I've been saying that for years, but everyone said I was nuts. You can't solve anything in capitalism. If money and consumerism are your only goals, that can't solve anything. Best you can do is patch... and that's about it. There is no money in long term solutions.
Wait for the instance to start caching content from the comm. It might even take a few days, but eventually, it will start caching. Sometimes it might lag though, like cache for a day or two, than stop for a day or two, than catch up... these are all home servers or VPSes, they're not as powerfull as the servers corps have at their disposal ๐คท.
Because some of these disks were proclaimed worn out and not to be used. I still use all of them in 3 custom NAS builds. I sold 2 of them, the owners still haven't reported a disk failiure, that was 2 years ago. I use one of the NASes as my personal storage, mdadm in RAID5, I still haven't had a single disk fail on me. They were all full of "bad sectors" (logical, because of the bad contact between the head/preamp and the control board, bad data was being written to them, passed them with DRevitalize, all of the bad sectors were "reparied"), and yet, somehow, they still work.
Not to mention the numerous primary (OS) drives I've done this operation through the years and most of them still work fine, even though they have fulfilled their purpose (with the advent of SSD and all that). I've also compared the life cycle of identical drives that didn't get this treatment and ones that did. Most of the ones that didn't get this treatment are dead now (head crash in most cases).
Do this surgery to all of your drives as soon as you buy them (or at least after they're out of warranty), disable AAM/APM (wdidle3 in case of WD) (you can do this even if in warranty, it's a software/firmware tweak) and the disk will practically last forever.
There is no formal warning, like from the software, but the admins did explain this and most just removed beehaw comms from their subscriptions (or at least I presume), but I kept them, for experimental purposes, to see if this is actually true. I don't actually see anyone commenting in those posts. They appear empty. I know they aren't cuz I can view beehaw from other accounts, but to sh.itjust.works, they appear empty.
The thing is I don't think an instance can check if it's being defederated by some other instance in the fediverse. If there is an easy way to check this, than yes, I do believe a formal warning on a post on an instance thay has defederated from you is in order. Things are kinda chaotic now regarding other bugs and features that are more important, but when things kinda settle down, yeah, I believe they should look into this as well.
Yeah, that's why I usually try and explain things, not just offer solutions. I believe it's important for the users to understand how things work under the hood. Not in detail, but the general gist of it, yes.
It's like a secret code. You can define a new one whenever you want (the admins I mean), but that will invalidate any active session (users logged in), so you have to clear cache and log back in.
Superior quality, but didn't make it on the market, the cassettes and mechanisms were too expensive, the heads as well. Sony thought that wouldn't matter, so they pushed it... turns out price does matter.
You might wanna log out and readd your accounts, most instances changed the login cookie secret after the attack yesterday, so now the old cookies don't work any more.
0x4E4F @ 0x4E4F @lemmy.fmhy.ml Posts 12Comments 476Joined 2 yr. ago
Still, I'd tap dat ass ๐.