Yeah this. I use teams all the time and I'm not happy about it but it mostly works and it has a lot of features. Meanwhile zoom is highly likely to not work. Last time I tried to use it, both video and audio tested good, then NEITHER worked and I could only chat during the "call".
People who lived in a big county could have to pay fees to call people in the same county! They were called "local toll" calls. Telcos have always been parasites.
This is not even remotely true.
Tesla shuts off before crashes
https://electrek.co/2025/03/17...
Tesla can't detect things even the most primitive AEB systems will stop for
https://www.theswansonlawgroup...
Idiots who Elon wouldn't piss on if they were on fire suck billionaire dick
https://slashdot.org/comments....
Why do you react so angrily to disagreement?
Oh look, you're morally bankrupt and stupid. Already knew that, though.
I promise you that letting Jesus into your life will make it better.
Oh, THAT is the specific kind of creeper dipshit you are. I wondered. I do not want or need Jesus to save me from what Jesus is going to do to me (send me to hell) if I don't love him. Your god is the most pathetic abusive substitute for an abusive spouse ever imagined by sad little men.
The problem is low level bugs have a tendency to have their tendrils in far more places than it appears.
Fixing a bug in 14 days? That may be reasonable if it's an application like Microsoft Word, but even then it likely isn't enough to be realistic. Even Google's 30 days was unrealistic.
The problem comes down to how central the component is - there are things where you need to do full regression testing because it's such a critical component that any change could break something.
If you demand a fix in 14 days, the easiest and quickest fix is likely the one that harms security for all - disable BitLocker. The option already exists and can be deployed with minimal testing in days.
But if it's deep down within BitLocker, then 14 days likely isn't enough - if it's a simple fix, it might take a day to go through the basic builds and sanity tests, but then you need to run through a ton of other tests because it impacts user data and you need to make sure the change doesn't introduce an edge case where users might lose their data.
Even small chances become big with big numbers - a 0.01% chance is still 100 incidences per million users.
Even in Linux the issue happened - Dirty Frag is easily mitigated, unless you happen to be using those modules where it can be exploited. And even then the fix isn't validated, there have been more similar issues found. While Copy.Fail was reasonably self-contained - it was just reverting a patch, and Dirty Frag was a simple check, who knows what the real fix is? It might result in a fix that blows up in people's faces because the patch had to come out and there was not enough time to test it.
At the same time, it isn't unheard of for patches to not fix the issue so a patch came out, then two weeks later a new one comes out as it wasn't properly patched in the first place Rushing never solves any problems, only makes new ones.
Not pulling people over to issue frivolous tickets saves lives.
Not pulling people over for safety violations costs lives.
It's his sister's fault she didn't preserve the key.
It's Mickeysoft's fault they locked the computer for no reason. Locking a normal user's desktop computer (i.e. not one with additional security-related group policy) just because they weren't using it is both user-hostile and pathetic. It gives off strong "Notice me senpai" energy.
There are no heroes in this story, but that goes triple for Microsoft's user-hostile defaults.
That's because for the most part, insurance will cover the loss
Insurance doesn't cover not getting to work. It might help pay for a rental car, but my insurance rental car amount won't completely cover even an econobox, even though I have an employee discount for car rental (my employer has a deal with one of the rental companies.) And even then I still have to wait for a rental car to show up.
It really doesn't matter what you think, what was stolen was worth a fuckton of money,
Anyone transporting a bunch of important data should a) have another copy and b) encrypt it. Does that excuse stealing it? No, but someone not actually trying to steal your data should only be responsible for stealing your HDDs, as intent matters. The value of the data should be irrelevant unless someone intentionally broke in and deleted your only copy. If not having your data leaked is important, you should be encrypting that data.
Yeah, people should all drive perfectly at all times.
This isn't necessary at all. All people have to do is pay attention even slightly. Flashing lights ahead? Slow down or get over. It is after all already the law.
Bill's not really an ex-anything.
There are cycles involved.
Why don't you get the fuck on yours and pedal the fuck out of here, bootlicker?
N150 is plenty for browsing. I have the AMD competition (Ryzen 7 5825U) and it is absolutely fine. The AMD chip has a lot more GPU, but it's still not enough for gaming really. Like, I could turn down the settings enough in Civ VI to make it playable, but not to have it look good at the same time. And that's a strategy game! Action games are hopeless unless they are quite old.
But this PC isn't being sold for gaming, its whole purpose is... well, to make money with bullshit marketing really, but it's meant to lurk in the background. You're not supposed to be using the console. Therefore the abject lack of GPU performance is irrelevant. The CPU power isn't going to set any records, but it's fine for any normal tasks.
The actually important part of what it's not powerful enough for is running local models. It doesn't have enough RAM and it doesn't have enough CPU. What you want for that is probably a Ryzen AI chip and at least 32GB. Some models run pretty well on a reasonably fast CPU without any LLM-specific features. I have a 5900X desktop with 64GB and a 4060Ti 16GB, and models run around 0.7x speed on the CPU compared to the GPU.
An AMD Ryzen AI HX 470 MiniPC with 32GB and 1TB is over $1000. Even with Ryzen AI 5 340 it's $750. So you're not getting the ability to run local models for this kind of money.
At one point even Musk realised it.
Then he found out Tesla could dodge a whole bunch of liability by driving into things and turning off autopilot less than a second before impact, then claiming that autopilot was not on at the time of the collision. If it was on until less than a human reaction time before the collision, it was on at the time of collision.
I literally won't get into a Tesla with alleged FSD. Other people can be that close to that experiment. It's bad enough I have to be on the roads with them.
I am not a native English speaker - English is not even the first foreign language I use - but I think "because he was very worried that someone else, if they got it, would do the wrong thing with it" unintentionally states that Musk wanted to be the first to do the wrong thing with an AI.
Now, fast forward a few years and Musk's AI claims to be a mecha Hitler.
IBM Advanced Systems Group -- a bunch of mindless jerks, who'll be first against the wall when the revolution comes... -- with regrets to D. Adams
