eh

All of these are "root" mounts. I don't explicitly mount any subvolumes (they get "implicitly" mounted as folders though)

Storage space is one issue. Bandwidth (how many TB/mo goes out the server) is another. And for any "serious" use case transcoding would also be important (so you can keep the other two down for everyone except Apple users who are stubborn to adopt VP9/AV1, and to provide multiple quality options), which unlike the other two requires powerful hardware most instances do not have.

It uses WebTorrent for distribution between viewers watching at the same time which can temporarily help with the load on popular videos, but there still needs to be at least one source instance that's sharing the video "regularly" (for unpopular or old stuff), which ends up having the same bandwidth issues you'd get with any other video platform.

nobody (in terms of both apps or servers) uses the C2S API. the closest you can get to a "de facto" standard is unfortunately the Mastodon API.

alongside the others mentioned here, lemdro.id exists for Android-related stuff and lemmyrs.org exists for Rust stuff (but seems to be running an old version of Lemmy, so YMMV)

Well, the "how" is technically simple. You paste the URL to the search box and you hit subscribe. You can do that right now with:

• Lemmy communities
• Kbin communities
• PeerTube channels
• Mayyyyybe a.gup.pe / chirp.social groups???? idk how well those would work

Lemmy itself only let you subscribe to ActivityPub Group actors though, so it's quite restrictive in that regard. kbin adds user follows and microblogging into the mix, but you can't do those through Lemmy yet (or perhaps ever).

However, the real "problem" is presentation. While you can, say, follow a Lemmy group from Mastodon. Mastodon is not intended for groups so it kinda breaks and ends up spamming your home timeline with all the posts and comments. Other implementations such as Akkoma or Misskey or Calckey (pending rename) might end up interacting better (because Mastodon will try to convert everything it gets into Notes in a "lossy" fashion).

While the protocol does allow you the freedom to interact between services, you will not get the best experience if you're not on a "similar enough" service. Although that does not stop you from following a PixelFed account from Misskey, or a Mastodon user accidentally finding their way into the Lemmy comments section. (You can tell because they'll be the only comments that end up tagging people when replying)

You have to actually toggle to see it but IMO it massively improves how scrolling feels.

There are a few more scrolling-related options out there on the net if there's a particular "feel" you want to go for. https://github.com/yokoffing/Betterfox/blob/main/Smoothfox.js provides a couple you can try out, and most of these custom scrolling options use msdPhysics as a baseline.

Not obscure but general.smoothScroll.msdPhysics.enabled=true is a must have IMO.

Again - I have no idea how well it's hardware support is. I assume 3d accel and whatnot would be fine because it's widely used, but dunno if anyone tried running ROCm on it.

Just let some bees loose on your system for a while and they'll sort that out.
Also depending on how good your CPU is btrfs compression would also save a fair bit. AFAIK shared libraries are pretty well compressible.

I wonder how well it integrates with hardware. Arch with the pacman packages has been the only distro where I could get ROCm working reliably. I'd love to make a "ROCm container" and dump all that mess into it's own sandbox.

In fact, the thing I really want is more of a "Qubes but not for security tryhards" (aka I can actually use Wayland AND game on it) where everything gets it's own container mainly for organizational purposes, but something like this sounds like a fair compromise.

There are signing keys involved, so if someone puts up a new server but uses different keys then all sorts of federation trouble will await them.

That said it shouldn't affect the general network, just that individual server (both the communities and the users of it)

Edit: As for switching domains on an existing server, that would be equally troublesome as ActivityPub kinda relies on domains for all sorts of IDs.