My point being the extensiveness of a review process.
The more important a system, the more people it impacts, etc, the more extensive the review process.
Someone chose to ignore this risk. That’s intentional.
My point being the extensiveness of a review process.
The more important a system, the more people it impacts, etc, the more extensive the review process.
Someone chose to ignore this risk. That’s intentional.
Then incompetence at a level that’s incomprehensible.
A code review certainly exposed this, and some manager signed off on the risk.
Again, changes I make are trivial in comparison, and our code/risk reviews would’ve exposed this in no time.
Oh, yea, I get the safety angle, but that work has already been done.
If I’m replacing a battery in something like thsas long as I use the same tech, where’s the concern?
If the factory battery has built-in BMS, then I should use the same, that’s about the only concern I’d have. And if it’s NiMH, well, even less of a concern.
And for this use-case, I wouldn’t be cheap on my replacements, like I am for stuff that’s low risk (like a flashlight that lives in a metal cabinet outside - if that lithium does a runaway, there’s little risk).
Wow.
Again, the kind of fix I’ve done thousands of times on all sorts of devices.
Which is exactly what I said. You get the interface you choose.
Those are pretty bright patterns in my book. More of the usual BS.
More like jingoistic, which is rather tiresome anymore. “Nazi” today is a virtually meaningless pejorative, and my dead grandparents are rolling in their graves having escaped real Nazis.
Russians are now Nazis?
Someone needs to read more history, and out down the Book of Pejoratives
XMPP/Jabber has whatever interface you choose (determined by the client you use), and does voice pretty darn well.
I’m currently using Jmp.chat as a SIM/data provider, and they provide an XMPP account via Snikket. I can connect to that account with pretty much any XMPP/Jabber client.
To me, XMPP/Jabber is the most flexible, because it’s a protocol, and you choose which parts you want. And you can choose which clients you use. I have 2 clients on my phone and one on my laptop. They all work fine with the same account, with messages showing up at all simultaneously. One client (Snikket) has multiple accounts in it. The thing is XMPP/Jabber as a protocol is like SMTP - it’s a standard, so all clients can communicate with each other, if they support the same features (eg OMEMO encryption, which is popular now).
Alternatively check out:
Teleguard, it’s from the folks at SwissCows. They claim E2E, and from the way you connect devices, and that you can’t recover an account from them, I tend to believe it. Though I haven’t seen a third party evaluation (I belive they’re closed source, unfortunately). So do with that what you will.
Simplex Chat, self hostable, they claim it’s very secure. I’ve used it some, the phone app is a bit heavy on ram use.
There are numerous others out there.
Well, that’s me then.
Never know when I’m going to need it, and it’s usually doing some kind of work overnight (processing media files, syncing files around, etc).
I schedule that stuff for when I should be asleep - less heat in the house during the day, it’s off-peak power (doesn’t make a noticeable difference to my bill, but why not).
If i need it, I can pause those things.
But I also have a NAS that can do this stuff, but it can only do so much at once.
Oh, damn. And by the time they got pulled out, enough concrete had cured on the car to need:
Rims
Rotors/drums
Pads/shoes
Perhaps ball joints/suspension components.
Expensive lesson.
I already upvoted for the comment, I’m out of upvotes!
Lol, don’t forget to add /s, so people will understand your sarcasm!
Windows Pro does “just work”. Configure GP when you setup, and all this garbage isn’t an issue. Even without the more extreme changes I make (beyond GP), most people would be fine.
MS pushes this crap in Windows Home users, because they know those people have no idea what to do with it.
If you’re a technical person, or you run Windows Pro instead of Home, you probably won’t see as much crap. But there’s a ton of new telemetry/tracking in Win10 that’s even worse in 11.
As someone who’s been part of OS and software deployment since before WinNT, Win11 is hot garbage unless we do all sorts of preconfig to not make it so.
This isn’t really new, just that much worse in 11. With the previous versions of Windows, we didn’t have to configure as many Group Policies to restrict as much nonsense. And the home versions of 10/11 are so much worse, especially since they don’t support GP, you have to Registry Stamp any changes you want to make to disable all the telemetry garbage - stamps which an update can easily revert. At least GP is reapplied at boot/login.
I don’t let my family buy Home versions of Windows. Pro costs more, because it’s worth it from a support perspective.
Wish I could upvote you for your username! Haha
Wow, that’s an interesting metric.
And XP was 32 bit only, it was really an updated version of Win2k, which was really rock solid.
Which kind of supports your point.
Except ME was part of the DOS line, while XP extended Win2k which is NT.
But I take your point, just that Win2k was (largely) the end of MS producing DOS-based operating systems (with XP being the final nail in that coffin).
In business, once Win2k was out, we stopped deploying Win9x entirely. Before that, NT was problematic on some hardware and for some software/users. Win2k solved most of that.
I generally agree.
But any decent code review process would’ve exposed this, or at least a data surveillance system that checks this stuff. I’ve received a few notifications about my logs storing inappropriate data, as a result of a scanning system.
Some manager knew about this during a code review, and signed off on the risk because it was only in-house.