Pretty sure that's only true about Lemmy. There are other threadiverse apps. The mistake is people calling the threadiverse lemmy.
r00ty
joined 1 year ago
These days with UEFI it's much less likely to break things. Worse case though you just boot from a LIVE USB boot, chroot in and rerun grub/your bootloader installer. Often even if windows puts its own bootloader first, you can choose your bootloader from the bios boot menu and just rerun the bootloader installer.
It used to be a lot worse.
20 years into the trump dynasty dictatorship, they will still be saying "thanks Biden" to every financial inconvenience.
The GDPR penalties are pretty serious for any reasonably large entity operating within Europe. I think when they're actually pushed with a proper GDPR request, they will mostly comply.
And it's risky to try to use that data. If someone, sometime in the future can prove their data was used after a confirmed GDPR request, it could be bad for them. And frankly, the number of actual GDPR requests is small enough that it's not worth their while for such a small part of the sheer cascade of data they have.
Yes, for everyone else I don't doubt they don't actually delete anything.
This is actually a very big difference with the USA and the UK (and possibly most of Europe, not sure though). We generally store eggs outside of the fridge. On a shelf or in a pantry/cupboard for example.
Slimey's back!
I wouldn't even bother replying to comments from hexbear mk II. I just automatically assume troll.
I said elsewhere, I hope this is just some way to track changes over time per user.
But they need to take an anonymous hash of some non changing data or create an install id that is used for this and nothing else (e.g it identifies a unique user but not the person or hardware behind the user).
Too much identifying info is just pushed around like we shouldn't care, it's become a real problem.
The way I read it, the developer wanted opt-out but it's likely it will be opt-in. I'm find with opt-in and vehemently against opt-out for telemetry.
I would prefer the information was statistical only. Rather than hostname (making the assumption they only want hostname to be able to somehow separate the data to follow changes over time), a much better idea would be some kind of hash based on information unlikely to change, but enough information that it would be unlikely possible to brute-force the original data out of the hash. So all they know is, this data came from the same machine, but cannot ID the machine. Maybe some kind of unique but otherwise untrackable unique ID is created at install time and ONLY used for this purpose and no other.
Yeah, my only concern here was if it was opt-out. That'd be bad.
Now I completely understand the developer on this. This is useful info to have to help decide future changes/features and general direction, but balancing the right to privacy means this kind of data provision should ALWAYS be opt-in. Microsoft, you hearing me here?
Yeah, it's not really new. In the movie Falling Down from 1993 (weird, I thought it was late 80s) has the whole scene where he's complaining about the difference between the advert and what you're served in a fast food place (well also that they wouldn't serve breakfast because it was like a couple of minutes late and almost certainly had some still hot breakfast around, but that's another story).
It's been this way for a long time, all over the world. I'd be amazed if this turned into a world changing case after all this time.
I'm on a pretty old version of mbin (I have some modifications I made for federation issues back when it was kbin). I need to spend a weekend to pilot an upgrade and make sure I can run it safely live.
But even then it's better in some ways already and I never feel like I'm missing something from lemmy. But I think just calling the whole thing lemmy puts off people that are seeing things through a political lens.