This would be more of a use case for blockchain, any site(/user) wishing to mirror the social media would participate in the chain. A post on one site would get pushed into the chain and show up on every mirror.

Media would likely have to be links outside of the blockchain since it isn’t usually very good at storing large datasets (it would make it difficult to mirror over time as it grew), so if you wanted a full mirror you would probably have your site fetching media as soon as it is posted and mirroring it yourself.

Or media might be a good spot to integrate with your bittorrent idea. Blockchain handles the distributed state of the site (communities/post text+metadata), and any submitted media is added to the post as bittorrent hashes. I don’t know how scalable bittorrent clients are though it might take considerable overhead to seed millions of pictures/videos.

https://www.linuxatemyram.com/

This is normal. Linux caches disk reads so that you don’t have to go to her/SSD to reread blocks. If your app isn’t using the ram Linux will use it instead.

Zero reason to be concerned, because if your app allocates more memory Linux will evict the cached pages to make sure your apps have plenty of space.

In this case your apps have memory that isn’t being touched (sometimes a sign of a memory leak), and Linux has decided that caching your disk access is more advantageous than keeping the unused application memory in ram.

If you have apps that you don’t use often and are really slow to access when you finally do, keep lowering that swappiness value or just remove swap all together if it annoys you.

Looking at your graph you have a lot of ram that you don’t really need… I would just disable swap entirely. Otherwise you are just wasting write cycles on your SSD.

Them’s fighting words! ;) yyyy-mm-dd is superior in every way. Sorts properly and much less potential for confusion across cultures.

If you click the link button it opens up the video instead of the preview jpg.

Btrfs raid5/6 support is unstable/experimental and cause some serious issues in the past, so it isn’t really recommended.

Since you only have 4 drives you could do a pair of mirrors with btrfs, but you aren’t guaranteed to be able to handle two drives failing (depends on which two drives fail). So zfs with raidz2 is the best protection you can get, and it matches the capacity you would get from mirrors.

Rebuild time isn’t great, but you would need a second drive to fail plus at least a read failure on another drive before you have issues.

A bigger question would be how soon would you have a replacement? If you already have a spare on hand I wouldn’t worry about rebuild time at all, but if you are expecting to wait potentially weeks for a warranty replacement your chances of the second failure go up.

Even if you had a second failure and additional read failure is unlikely (how often do you see read failures when you run a scrub). Combine that with your backups… You should have very little to worry about.

If two drives failed and you ran into a couple of sectors that can’t be read ZFS continues to operate just fine, except for the failed file. The file with the failed blocks shows up in zpool status so you know exactly where the corruption is, and you can just copy that single file from your backups and everything is back to normal.

If your files are mostly WORM files like media/documents then your backups cover you really well and copying a file or two from backups isn’t a concern. Vs if you are running virtual machines or DBs that are writing to their virtual disk constantly then you would start to worry about how much data you lose by rolling that file back to your past backup.

Well that would be the description of the community, but the actual rules section doesn’t say anything about privacy/control.

So at the end of the day Plex is self hosted (you run most of it) so it should qualify. It might not 100% match the spirit of self hosting it does still meet the definition.

You can argue most Jellyfin/emby installs have the same problem because most users are still are dependent on external services because of things like metadata plugins.

And on the privacy front those plugins aren’t any better than Plex. For instance The Movie DB which is the primary movie and TV metadata provider for Jellyfin has a privacy policy that clearly says they will use and share any interaction you have with the site including location and personal information. They almost certainly keep track of what is in your library. They don’t have a user account for you that they can use to track across IPs, but if your ISP keeps you on the same IP for long periods of time they have a good idea of what you are watching.

You can run Jellyfin without those plugins enabled but unless you want to build/collect manual nfo files to import that data you are going to have a subpar experience.

Same problem for the **arr stack since they need metadata as well. Some of which go to different providers so you are giving out that information to additional parties (i.e. Sonarr goes to TheTVDB which has a similar privacy policy).

You can configure the arrs to write out nfo metadata and have Jellyfin consume that so that at least you aren’t giving away your info to two external parties.