Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)LO
Posts
4
Comments
413
Joined
2 yr. ago

Permanently Deleted

Jump
  • The problem is that nobody, apparently not even manufacturers anymore know how to fucking aim headlights. Headlights literally have aimer knobs and you are supposed to aim them such that they cut off just before they would blind the majority of vehicles

    I have projector LEDs and with a projector lens you can get an extremely practically knife sharp cut off and I have it literally just at the very bottom edge of most small sedan windshield lines. It's great my headlights are bright as fuck they go all the way from the left shoulder to the right shoulder even on four lane roads but they don't blind anybody and I've had friends help me test that by just kind of passing each other on the street and them saying it was fine and wasn't bad like other people's cars.

    At some point people started associating the height of your light with the amount of safety, it's possible to get distance without adding height but everyone's forgotten how that works

  • They are amazing but at the end of the day they are still humans and they can make mistakes. In the YouTube video referenced one of the C devs is heavily against rust.

    Decided to go look for CVEs from code the guy manages (Ted Ts'o) I found these

    CVE-2024-42304 — crash from undocumented function parameter invariants

    CVE-2024-40955 — out of bounds read

    CVE-2024-0775 — use-after-free

    CVE-2023-2513 — use-after-free

    CVE-2023-1252 — use-after-free

    CVE-2022-1184 — use-after-free

    CVE-2020-14314 — out of bounds read

    CVE-2019-19447 — use-after-free

    CVE-2018-10879 — use-after-free

    CVE-2018-10878 — out of bounds write

    CVE-2018-10881 — out of bounds read

    CVE-2015-8324 — null pointer dereference

    CVE-2014-8086 — race condition

    CVE-2011-2493 — call function pointer in uninitialized struct

    CVE-2009-0748 — null pointer dereference

    Do you see a pattern in the type of error here? It's pretty much entirely memory related and right in the wheelhouse of something rust would just outright not allow short of just slapping everything into unsafe blocks.

    The Old Guard is not perfect, and they are acting as a barrier to new talent coming in. Sometimes change is good and I'm heavily in the camp that rust one of those times. Linus seems to agree as he allowed the code into the kernel which he would never do lightly or just because it's fomo

  • Some commuter Express routes operate on very limited stops so depending on when you got on you may very well have gotten on right before they hit the freeway and don't stop till the next town

  • It's true technical analysis does show the opposite, however it's a technical analysis. AKA Engineers making educated guesses. Which is the reason the FCC allowed a limited test area to run actual trials to verify. And the fact that the FCC has not immediately shut it down implies that they have not been able to confirm what that technical analysis predicted.

    Don't get me wrong I'm no big huge fan of starlink over here, but both AT&T and Verizon have a long standing history of competing through litigation rather than actual service so I'm inclined to give T-Mobile and starlink the benefit of the doubt here.

    When everyone was first getting new frequency opened up AT&T and Verizon fought over millimeter wave while T-Mobile mostly ignored it and went for the mid band 600-800mhz. This caused the T-Mobile to have an insane lead over actual 5G deployment you can now get good 5G speeds out in the middle of rural fuck nowhere because you'll be on the 700 band 12.

    Meanwhile millimeter wave is still useless because a piece of rice paper will block the signal entirely so it only works in extremely extremely limited areas of town with direct line of sight and no obstacles to the Tower. So Verizon and AT&T started complaining to the FCC that T-Mobile has too much spectrum and they can't possibly compete even though they made absolutely no attempt whatsoever during the initial bidding to get any mid-band.

    Now we see the same thing here, T-Mobile is getting ahead of everyone Verizon and AT&T are lagging behind they plan to roll out the exact same service, with the exact same frequencies, with the exact same technology, however they are still in the planning phase and starlink/t-mobile is just about ready to activate it so they are complaining

  • You could try actually reading? The article goes over why they want the exemption. Which is mainly that the fcc's maximum transmit power for this particular band is both outdated and wildly over cautious. They argue that you can easily transmit with more power without creating any interference and that's what the trial was demonstrating

  • She literally can't, even if she was actually 105% committed to it people seem to forget that overall the president actually has very little power. Without the cooperation of the house and Congress nothing in that vein will ever get done and no matter who gets elected our house in Congress have been split divided and useless for quite a while now

  • Starlink and T-Mobile, in a limited area that was approved by the FCC for testing. And at the end of that trial they are required to give the results to the FCC so AT&T and Verizon wouldn't even need to say anything if it was going to cause interference the FCC would just stop it at the end of the trials. The fact that that didn't happen and that they now feel the need to try and say it might interfere is proof that they are just stalling.

    And again they are literally getting ready to roll out the exact same thing, based on the exact same technology, using the exact same frequencies. They literally just want time to catch up because they got caught slacking lol

  • They are claiming that they think it would, despite the fact that both T-Mobile and starlink have demonstrated that it won't in trials. They are also simultaneously getting ready to roll out their own service based on the exact same technology which proves they are just talking out their ass because they want more time to catch up

  • I ask that same thing to people that are somehow still playing Minecraft despite having been playing it since it was an alpha. I definitely played a lot of it but I can't even touch it anymore I don't care what mods you put on it

  • They get upset about it because it's a trend in the industry that a lot of people hate. That particular series is a great example where the next game not only adds nothing but even generally takes stuff away from the previous title, but it keeps selling so it's kind of becoming a trend in the industry for most series to just keep releasing the same garbage over and over.

    So it's less about enjoying a sports game that they are upset about, and more upset about encouraging the behavior of extremely low effort recycled releases constantly

  • Given how big the US is I would imagine this kind of varies state to state. I'm in Washington state and I would say that about 85 to 90% of gas stations have diesel available. The major ones that don't off the top of my head are Costco and Fred Meyers Gas Stations. The majority of the rest of them even in downtown Seattle generally have diesel available