• 0 Posts
  • 27 Comments
Joined 2 years ago
cake
Cake day: July 5th, 2023

help-circle


  • Waymo can absolutely drive at night, I’ve seen them do it. They rely heavily on LIDAR, so the time of day makes no difference to them.

    And apparently they only disengage and need human assistance every 17,000 miles, on average. Contrast that to something like Tesla’s “Full Self Driving” (ignoring the controversy over whether it counts or not), where the most generous numbers I could find for it are a disengagement every 71 city miles, on average, or every 245 city miles for a “critical disengagement.”

    You are correct in that Waymo is heavily geofenced, and that’s pretty annoying sometimes. I tried to ride one in Phoenix last year, but couldn’t get it to pick me up from the park I was visiting because I was just on the edge of their area. I suspect they would likely do fine if they went outside of their zones, but they really want to make sure they’re going to be successful so they’re deliberately slow-rolling where the service is available.


  • They’re still working on it. All the dev is by a single guy, who also runs Pixelfed. He says he’ll be open-sourcing the code soon so more people can contribute and help get things going, but he wants to finish getting the web interface working first. And apparently he’s been spending a lot of time keeping everything online during the surge of interest, which has slowed everything down.


  • I’m in the Discord for Loops, but not affiliated with it. The dev said they’re rate-limited by their email provider, so it does take a long time to go through the queue. The queue is also split between Pixelfed and Loops, since they have the same developer, so that slows things down even more.

    It took about three days to get my invite as well, but it may be a bit faster now since I think the initial surge of signups has tapered off a bit.





  • Unfortunately the amount of delta-V you’d need to boost it to a parking orbit of some kind, or to the moon, would be deeply impractical. And it doesn’t have the shielding required to support any sort of deep space habitation.

    I’d love to see some or all of it returned to be displayed in a museum, but it would probably be more expensive to do that than it was to build it in the first place. The vehicles to return it in whole or in pieces simply don’t exist right now, and on-orbit disassembly would be incredibly difficult and dangerous for astronauts to carry out.



  • Janet Yellen is not in charge of the United States money supply. You’re thinking of the Federal Open Market Committee, which is comprised of the seven members of the Federal Reserve Board, the president of the New York Federal Reserve Bank, and four of the eleven regional Federal Reserve Bank presidents on a yearly rotating basis.

    And I’m not sure why you’re bringing up a criticism of our collective net worth on a discussion around whether Bitcoin is used in scams, unless you’re trying to push the narrative that traditional fiat currency is somehow worth less than an unbacked security. Which is both irrelevant to the conversation, and a pretty good indication that you don’t really understand how currency works.


  • I’m one of the admins who manage CrowdStrike at my company.

    We have all automatic updates disabled, because when they were enabled (according to the CrowdStrike best practices guide they gave us), they pushed out a version with a bug that overwhelmed our domain servers. Now we test everything through multiple environments before things make it to production, with at least two weeks of testing before we move a version to the next environment.

    This was a channel file update, and per our TAM and account managers in our meeting after this happened, there’s no way to stop that file from being pushed, or to delay it. Supposedly they’ll be adding that functionality in now.


  • Yes, CrowdStrike says they don’t need to do conventional AV definitions updates, but the channel file updates sure seem similar to me.

    The file they pushed out consisted of all zeroes, which somehow corrupted their agent and caused the BSOD. I wasn’t on the meeting where they explained how this happened to my company; I was one of the people woken up to deal with the initial issue, and they explained this later to the rest of my team and our leadership while I was catching up on missed sleep.

    I would have expected their agent to ignore invalid updates, which would have prevented this whole thing, but this isn’t the first time I’ve seen examples of bad QA and/or their engineering making assumptions about how things will work. For the amount of money they charge, their product is frustratingly incomplete. And asking them to fix things results in them asking you to submit your request to their Ideas Portal, so the entire world can vote on whether it’s a good idea, and if enough people vote for it they will “consider” doing it. My company spends a fortune on their tool every year, and we haven’t been able to even get them to allow non-case-sensitive searching, or searching for a list of hosts instead of individuals.


  • Speaking as someone who manages CrowdStrike in my company, we do stagger updates and turn off all the automatic things we can.

    This channel file update wasn’t something we can turn off or control. It’s handled by CrowdStrike themselves, and we confirmed that in discussions with our TAM and account manager at CrowdStrike while we were working on remediation.



  • He didn’t ignore basic gun safety. Firearms on movie sets are not the same as firearms everywhere else. There is supposed to be a dedicated person who is directly responsible for ensuring live ammunition is never, ever brought close to a prop gun. I’ve posted this elsewhere at one point, but as somebody who has worked on productions with blank-firing guns, the cast and crew are not allowed to inspect, touch, or come near any firearm on set apart from the shortest time required for the scene. The firearms are secured before and after the scene, and there should never, ever be a chance for live ammunition to get inside a prop. The armorer guarantees the gun is safe, and are the ones responsible for it.

    The armorer for this production appears to not have followed those protocols, and that’s where Baldwin’s potential culpability is-- not as an actor who shot somebody, but as a producer who should have had better oversight of the armorer.





  • DesertCreosote@lemm.eetoMemes@lemmy.mlGoogle “search”
    link
    fedilink
    arrow-up
    8
    arrow-down
    1
    ·
    2 years ago

    Can’t speak for the person you’re replying to, but I’m a security engineer and stuff still makes its way to me that you would think would get filtered out by others (and isn’t my job to fix). It just takes the right person thinking “this is obviously a problem with $system, let’s just send it straight over to them so they can fix it quickly!” And then we get the fun job of proving it’s not us and has no relation to us.

    We got a ticket today for packet loss between two systems, neither of which have any of our tools on them…