this post was submitted on 30 Dec 2023
155 points (94.8% liked)
Asklemmy
43821 readers
1152 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Many people have given great suggestions for the most destroying commands, but most result in an immediately borked system. While inconvenient, that doesn't have a lasting impact on users who have backups.
I propose writing a bash script set up to run daily in cron, which picks a random file in the user's home directory tree and randomizes just a few bytes of data in the file. The script doesn't immediately damage the basic OS functionality, and the data degradation is so slow that by the time the user realizes something fishy is going on a lot of their documents, media, and hopefully a few months worth of backups will have been corrupted.
It'll just write a new Shakespeare play
I think we may need to implement a 128 bit unix timestamp before that will work.