Of course there’s a financial reason, they’ve probably done a cost/benefit analysis and decided that it’s financially better to screw over those customers than to spend money fixing it. But that’s exactly the issue!
Of course there’s a financial reason, they’ve probably done a cost/benefit analysis and decided that it’s financially better to screw over those customers than to spend money fixing it. But that’s exactly the issue!
I think what most people disagree with, is that the active choice from AMD to not fix a very fixable issue, is a choice they know leaves customers is a seriously bad position. This is something they choose to do to their customers, because they could just as well choose to help them.
what I meant was that apparently only compromised systems are vulnerable to this defect.
That is not correct. Any system where this vulnerability is not patched out by AMD (which is all of gen 1, 2 and 3 CPUs) is left permanently vulnerable, regardless of whether or not they already are compromised. So if your PC is compromised in a few months for some reason, instead of being able to recover with a reinstall of your OS, your HW is now permanently compromised and would need to be thrown out…just because AMD didn’t want to patch this.
Ryzen 3000 series CPUs are still sold as new, I even bought one six months ago, they’re no where near being classified as “old”, they’re hardly 5 years old. And this is not only an issue for already infected systems because uninfected systems will intentionally be left vulnerable.
No they are just choosing not to roll out the fix to a known issue, which is screwing customers over on purpose (to increase profits). It’s not a matter of goodwill, they sold a product that then turned out to have a massive security flaw, and now they don’t want to fix even though they absolutely could.
They are 100% not patching old chips intentionally by not allocating resources to it. It’s a conscious choice made by the company, it is very much “on purpose”.
Must have been picked back up then, I recall it not having any commits for something like 6 months
Is it still being actively developed? I ditched it a while back because it seemed to have been abandoned It hadn’t received any activity for several months and was working really janky.
I would reall love to have an open source watch, but unfortunately both the pinetime and bangle.js 2 lack severely in the activity tracking, which is the primary reason for me to have a smart watch.
I’m not sure how the screen is on the pinetime, but on the bangle.js 2 it’s surprisingly bad. Not a deal breaker by itself, but combined with a sort of limping experience on other parts, it’s not a good product (yet).
I bought a couple of 12tb “used” drives from servershop24.de, thay all had less than 150h of runtime.
It’s not dependent of circuit, things just need to be on the same phase. Our house uses three phases total, so power line adapters only work for 1/3 of the house here.
Yeah it doesn’t really seem provide any useful functionality.
deleted by creator
I think 3.5" are usually priced better per tb than 2.5" drives and performance is usually better too. So unless you feel like burning money for an inferior solution, are have some space constraints that doesn’t allow 3.5" drives, I wouldn’t go with 2.5" drives. They’re more energy efficient though, but you’d need a fuckton of drives for that to make a worthwhile difference in your power bill.
He now runs a beet farm/B&B with his cousin.
Well that’s a big ol’ “whoosh” on me then 😅
That does sound more like a user issue than a software issue though
Should you really be concerned about a system that can be physically ruined by malware? I would say definitely yes…