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

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.

This seems extremely elitist, even if just for the fact that you do not know what other knowledge (and experiences and viewpoints and…) those people who’d be interested in those communities would bring.

If you want a site comprised entirely of - what it seems to me - techbros who talk about how large their homelab Kubernetes clusters are, you should do that by curating your experience with the general platform, not by excluding anyone else, which is what you’re doing here even if you don’t realize it.

I personally want people from all walks of life to set up shop in the fediverse (as long as they’re not jerks). Even if I’ll never see or interact with 99% of what they create, maybe that last 1% will solve an obscure problem I encounter, or recommend me something (whether it be a product or recipe or location or…) that will change my life for the better.

I do not agree with the people wanting to control other servers by trying to force defederating from threads. Independent admins running their own server is what the Fediverse is built upon.

As long as authorized fetch is implemented (and correctly), intermediaries can’t “leak” messages out anyways. If Threads wanted to read the contents of a boost, they would have to ask your server for that, and your server can tell them to screw off.

Does kbin or Lemmy implement authorized fetch? If they don’t they should start working on it. And consider enabling it by default. I know versions of Lemmy >= 0.18 can talk to GTS (which enforces AF) so there is partial support for it. And nobody runs 0.17 because of how inefficient it is, so that won’t be too big of a backwards incompatibility issue. No idea how it works on kbin land here, but it should be implemented ASAP if only so that any future enforcement won’t break backwards compatibility.

that would be censorship, something the fediverse aims to avoid. We all shit on meta/twitter/other large corps for censoring content, but when instance owner’s do it, its fine? De-federating for ideological reasons like this goes against the principles of federation.

The thing about the Fediverse is that you have the choice to pick an instance. We shit on “big tech” when they do something, because there isn’t anything else to do. I personally want to be on an instance that will defed the fuck out of threads (and anyone else who will bring over people who will delight themselves on harassing me and my friends) should they federate, and if you don’t want that you’re welcome to go to an instance that won’t, and we can still talk to each other.

ps: As far as I’m aware, Fediverse never “aimed to avoid censorship” nor had any “principles on federation”. In fact, there are large parts of Mastodon (well, mostly Pleroma/Akkoma/Soapbox) filled to the brim with the worst kinda people you can imagine, yet they’re all defederated into their own little sandbox. Nobody can decide who can use and build upon ActivityPub but we sure as shit can decide to not federate with a company so shit at moderation that everyone opposing federation with them seems to be a minority in one way or another.

The solution to this is Authorized Fetch. It trades a little bit of efficiency (individual AP messages being re-shareable by intermediaries) for proper authorization (every server must fetch the messages directly from the source, with the correct authorization). Mastodon implements it behind an env variable, and implementations like GoToSocial force it. No idea how kbin or Lemmy work but they should look into it.