I switched from Plex to Jellyfin several years ago and haven't really looked back. Overall I just didn't like the direction plex kept going (pushing shit streaming services, central auth, paywalling features), and dropped it even though I grabbed a lifetime plex pass back in the day. The only thing I miss about plex was the ease of developing a custom plugin for it since you could pretty much just drop python scripts in there and have it work, though their documentation for plugin development was terrible (and I think removed from their site entirely).
Ext4 because it is rock solid and a reasonable foundation for Gluster. Moving off of ZFS to scale beyond what a single server can handle. I would still run ZFS for single-server many-drive situations, though MDADM is actually pretty decent honestly.
Yeah, as someone who used Mastodon back in the day this wasn't surprising, as they sorta highlighted your vs local vs public timeline, but I can totally see how it could be confusing expecting Lemmy to just be a "reddit clone". And TBF it is a reddit clone of sorts if you disable federation, "All" is everything your instance can possibly access, but then you lose out on what IMO is the killer feature.
There is probably a way you could spider instances and scrape content to get an "All" of sorts...
As someone who hosts a bunch of other stuff already including my own email (because I am a madman), does stuff like this as a job, has developer experience, etc. it was simple.
Figuring each of these things out (and how they all work together) for the first time was a hell of a journey.
Pictrs is a mix of both cache and long-lived images on anything you post, your profile image, etc. So you may want to back it up... Apparently there may also be some sort of internal database pictrs uses as well, but I haven't looked into that...
I would suggest taking postgres dumps and backing those up rather than trying to back up the data directory, as according to the pg docs when taking a disk-level backup "[t]he database server must be shut down in order to get a usable backup."
There are many ways to update dns automatically, I have used this container in the past. You could probably even write a bash script/cron job that checks your IP and updates it with curl depending on your DNS provider.
If you are already running tailscale you may be interested in using a funnel, which lets you accept and route internet traffic to your tailnet. I don't use tailscale so can't comment on how good/bad/useful this is.
You could also run some sort of service like frp from some remote box (like a VPS in DO/Linode/etc). This or the funnel lets you not expose/advertise your home IP address if that is a consideration.
I'm talking purely from an ActivityPub/Activity Streams/Activity Vocabulary/JSON-LD perspective. There are some other local identifiers for things in Lemmy, but those do not matter for the purposes of federation. Any Object that is federated is expected to have an ID that is a URL at which you can make a GET
request with the proper Accept
header and you will get the latest version of that Object. AFAIK there is no provision for IDs to change.
Migration of ActivityPub stuff is pretty rough... Everything has an ID, and that ID is the URL, so the ID of the post you replied to is literally https://lemmy.nrd.li/comment/227095
... AFAIK there are some (non-standard, at least not in core AP) ways you can mark things to be like "yeah, this moved to over here", but that isn't built in to the spec so whether those mechanisms actually work is a crapshoot.
AFAIK deletes do get federated. Also, it would be trivial to implement soft delete where the data is retained but bot shown.
In some cases soft deletes are good and useful because it allows things "deleted" for spam and rule breaking to be retained and used to build a case against a bad user/bot or train spam filters, etc.
Seems like most of the Tesla shills haven't really made it over to the fediverse yet, so that's nice.
Also their username on lemmy.ml of "Veritas" is particularly ironic given the current penchant of LLMs to lie/"hallucinate".
Laptops/desktopes: no real naming scheme, they use non-static DHCP leases anyway.
Physical servers: NATO phonetic alphabet. If I run out of letters something has gone terribly ~~wrong~~ right.
VMs: I don;t have many of these left, but they are named according to their function and then a digit in case I need more. e.g. docker1, k3s1. This does mean that I have some potential oddities like a k3s cluster with foxtrot, alpha, and k3s1 as members, but IMO that's fine and lets me easily tell if something is physical or virtual. I am considering including the physical machine name in the VM name for new things as I no longer have things set up such that machines can migrate... though I haven't made a new VM in some time.
Network equipment: Named according to location and function. e,g, rack-router, rack-10g, rack-back-1g, rack-ap, upstairs-10g, upstairs-ap. If something moves or is repurposed it is likely getting reconfigured so renaming at that point makes sense.