minnix

I read long ago you had to get malware on the air gapped machine first to begin with, and then it's only accessible within a few meters. Also it can't be accessed through walls. That was years ago though, maybe it's changed now.

Before you buy anything, put some of the same content that buffers on a USB stick or powered drive and play it directly from the pi4. Also connect via ethernet to your router from another PC and check your dl speed from the NFS share.

Check out [email protected]

Appreciate the offer but to be honest I don't even want to moderate my own communities.

Ollama without a GPU is pretty useless unless you're using with Apple silicon. I'd just get rid of it until you get a GPU.

Consequences will never be the same

There's an interesting book I read recently related to this called The Anxious Generation: how the Great Rewiring of Childhood is Causing an Epidemic of Mental Illness. I'd recommend it.

As a counterpoint, EFF put out this article today: The Surgeon General's Fear-Mongering, Unconstitutional Effort to Label Social Media

I am using Kinoite for quite a while now and not once did layering break anything.

That's great for you. Not everyone may use their distro in the same way as you.

https://discussion.fedoraproject.org/t/is-silverblue-rpm-ostree-intended-to-be-used-with-layered-packages/26162/2 https://discussion.fedoraproject.org/t/fedora-silverblue-36-will-not-succesfully-deploy-after-layering-packages/77502/3 https://gitlab.gnome.org/GNOME/gnome-software/-/issues/991 https://github.com/coreos/rpm-ostree/issues/4280

Not to mention the whole Firefox debacle of including an outdated borked version based with the system install instead of just moving to Flatpak install of most recent stable release. There's a very valid reason why package layering is discouraged by atomic maintainers and why toolbox is there by default as part of OS. And don't even get me started on DKMS and driver installation.

So, the points in favor of Kinoite is sticking closer to upstream, however it seems like I would need to layer quite a few packages. My understanding is that this is discouraged in an rpm-ostree setup, particularly due to update time and possible mismatches with RPMFusion

It's not only discouraged but often times it's system breaking. I used Kinoite for a year before I just became too frustrated and gave up. The first thing I learned though was to stay away from package layering because it tended to break things more often than not. Basically if you can't find or build a flatpak and you don't want to use toolbox all the time, just stick with workstation. Immutable is great when deploying to multiple servers or locked-down corporate workstations, but it makes no sense for your personal setup especially if you're already familiar with Linux.

Even more shocking is the revelation that somehow, even private DMs from Mastodon were mirrored on their public site and searchable. How this is even possible is beyond me, as DM’s are ostensibly only between two parties, and the message itself was sent from two hackers.town users.

I find this hard to believe but stranger things have happened.

Not every room or space will be hosted by someone self-hosting their server. I find it kind of appalling that this would be the solution. It’s certainly not what I’ve heard from people working on projects around moderation.

This is somewhat the goal, but without the hyperbole. Homeservers will be hosted by individuals or orgs, but will contain many rooms and spaces each. In 2020 there were over 20,000 homeservers. That number has without a doubt grown exponentially. The concept is the same with Mastodon. If you are worried about moderation on the matrix.org homeserver there are many lists of public homeservers across the web. Many people research homeservers to see if they are a good fit for them just as they do Mastodon instances.

This blog post gives a good idea of where matrix is heading. Notice their mission of decentralization.

Since agglomeration around a single instance is against the goals of Matrix and its Foundation, users need to have a way out and incentives to move.

We are committed both to making Matrix more accessible, and to doing the work to decenter the Matrix.org homeserver.

Matrix.org is meant to be an entry point, not a stopping point. As to your concern regarding built-in tools, matrix is just a spec, an open source federated communication protocol based on HTTP. The community builds tools. Matrix is not discord. In fact it is in opposition to the discord philosophy of centralization, data mining, advertising, and AI training.

It sounds like you are more concerned with the matrix.org homeserver than matrix itself. Matrix.org homeserver will eventually go away for personal use, this is the plan for the future. Matrix has always kept this homeserver open as proof of concept, but has not planned to keep it open forever as the goal is the widespread adoption of the protocol and for people and orgs to host their own servers and build tools using matrix.

The bullet points you listed are all currently able to be realized on any self-hosted homeserver.