degenerate_neutron_matter

Torrent containing the videos from the Reddit thread linked in the article:

magnet:?xt=urn:btih:GSP4QPJ2YFYNFXDJ7BFS2TLKOI2XW4UC&dn=Depositions%20for%20MLA-ACLS-AHA%20Lawsuit%20About%20the%20NEH&xl=6810123378&tr=http%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce&tr=udp%3A%2F%2Fopen.demonii.com%3A1337%2Fannounce&tr=udp%3A%2F%2Fexodus.desync.com%3A6969%2Fannounce&tr=udp%3A%2F%2Fopen.stealth.si%3A80%2Fannounce&tr=https%3A%2F%2Ftorrent.tracker.durukanbal.com%3A443%2Fannounce&tr=udp%3A%2F%2Fwepzone.net%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.wepzone.net%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.torrent.eu.org%3A451%2Fannounce&tr=udp%3A%2F%2Ftracker.theoks.net%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.srv00.com%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.filemail.com%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.dler.org%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.alaskantf.com%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker-udp.gbitt.info%3A80%2Fannounce&tr=udp%3A%2F%2Ft.overflow.biz%3A6969%2Fannounce&tr=udp%3A%2F%2Fopen.dstud.io%3A6969%2Fannounce&tr=udp%3A%2F%2Fexplodie.org%3A6969%2Fannounce&tr=udp%3A%2F%2Fbittorrent-tracker.e-n-c-r-y-p-t.net%3A1337%2Fannounce&tr=https%3A%2F%2Ftracker.zhuqiy.com%3A443%2Fannounce

That’s odd, maybe it has to do with symlinks? Adding --dereference to the du command will count the file size of the files referenced by symlinks. If that doesn’t show anything abnormal, I’d compare the directory sizes between your home directory and the rsync backup and try to find where they differ significantly. If it does show a much larger size, narrow down the location of the relevant symlinks (may be a hidden directory) and either delete them or exclude them from the rsync.

You can rerun the du command with --count-links to count hardlinks multiple times. If that shows >780GiB you have a lot of hardlinks somewhere, which you can narrow down by rerunning the command on each of the subdirectories in your home directory.

Your options would be to delete the hardlinks to decrease your total file size, exclude them from the rsync with --exclude, or repartition your SSD to a filesystem that supports hardlinks.

BTRFS supports compression and deduplication, so the actual disk space used might be less than the total size of your home directory. I’d run du -sh --apparent-size /home/sbird to check how large your home dir actually is. If it’s larger than 780 GiB, there’s your problem. Otherwise there might be hardlinks which rsync is copying multiple times; add the -H flag to copy hardlinks as hardlinks.

Sort your data into stuff you absolutely need to keep (personal files and such) and stuff you’d be okay with losing (less important files, device backups, downloads you can redownload, etc). Then only back up the former. As for backup medium, ServerPartDeals often has some pretty good deals on storage; they were selling refurbished 12TB drives for $80 a pop a while back.

Didn’t see this earlier but another thread gave a good summary: https://piefed.social/comment/9505729

Cool, but this article looks like AI slop.

Looks like I’ve been spreading misinformation, whoops. Edited my comment to clarify.

I don’t think it’s a good idea either, but it’s less egregious than filtering specific communities.

This filter is not part of any specific instance, it’s hardcoded into PieFed’s code. That means it applies to every PieFed instance unless the instance admin explicitly patches the code to remove it.

Got any other specific examples?

Each instance should be free to set their own rules. Individual instances blocking those communities is fine, but the PieFed devs hardcoding a blocklist that applies to all instances (especially one as opinionated and arbitrary as this) is absolutely not.

List of blocked words in community names:

shit
piss
fuck
cunt
cocksucker
motherfucker
tits
memes
piracy
196
greentext
usauthoritarianism
enoughmuskspam
political_weirdos
4chan

Seems like one of the PieFed devs has some opinions about the kind of content they dislike, and are unilaterally forcing that on every PieFed instance. I can somewhat understand filtering out curse words, but specific communities should not blocked by default, and definitely not hidden in a hardcoded list in the source code.

Edit: Important context here: https://lemmy.world/comment/21323475 Seems this blocklist is more limited in scope; it’s not blocking federation entirely, just blocking (from what I can tell) their appearance in search and automatically federating with them when adding an instance. Still problematic to exclude specific communities in a non-configurable way with little justification IMO.