What is the software setup when you’re actually configuring the minipc/box? Beyond the hardware architecture of the local network, what is the actual stack I should be pursuing and how is it implemented?

For example: I read lots of great things about OPNsense, Wireguard, DietPi… but I don’t know what the exact stew should be and how to set it up ELI5 style.

I was lazy in my langauge. I meant DOCSIS modem -> router/firewall with everything -> access points or hardlined ethernet recipients. Current setup is Arris dedicated (non-wifi) 3.1 to Linksys mesh.

99% of demands are local network performance. No mega streaming needs or huge external traffic. Upload on wireguard (Jellyfin or otherwise) will be pretty limited to a single user at once. But this is not critical. Local network is my usecase.

I am 500/50, will probably up to fiber as soon as it’s available. But again not a lot of external traffic, hyper limited.

So get a switch between the router/minipc/whatever and the rest of the local network instead of many on-board ethernet?

What do I need to run Kimi? Does it have apple silicon compatible releases? It seems promising.

For media, I use Jellyfin on an M1 MacMini.

How do you get around RAM requirements on SBC home servers with little devices like this? I am often streaming 4K files and the encoding/decoding can sometimes be mildly intensive depending on the file.

Considering both Plex and Tailscale are going toward VC exits, Headscale and Jellyfin is the only FOSS way atm.

Buy an LG Smart TV and use the WebOS version of Jellyfin. That’s the best I’ve achieved.

Is there a more detailed guide to this practice and the pros/cons?

Discovery should not be a function of the Fediverse itself. It should be a tool, app, or otherwise layer on top of a baseline. Discovery is an opinionated service offering—if it’s baked in, it’s not a good thing IMO.

Joined the TestFlight!

Jellyfin and self host!

Jellyfin is so much better man, once setup. It’s basically the dream.

This looks so sick.

We need an encyclopedia of posts/content like this that is the masterbook of Fediverse ops and scaling “how-to.”

You should redo your org from scratch and let all the default plugins do the work. Mine looks great and I never changed anything, just followed the recommended file org pattern for Movies and TV Shows.

This is elite self-hosting, lol. I want more of this content.

Like I said, I think they should wield their expertise towards making alt implementations of Mastodon and Lemmy that support multiple ways of video—paywall or otherwise—because the primary problem with video is always distribution and engagement. Miming YouTube more directly will always fail. It has for two decades now.

I am of the belief we do not need PeerTube at all.

We need a custom Lemmy instance that has video upload baked in, as well as a method of monetizing it for the server/“creator” (who is in a structural sense the moderator of the community to which it was uploaded).

Lemmy is simply better at distributing the information. PeerTube is a red herring and P2P video sucks. We need to make it easy for a server operator to have a mechanism for paying for the bandwidth (take payments and contain distribution to paying users, and account for bandwidth when distributing operating income after costs).

Bitcoin Cash my dude. If you’re doing Stripe, integrate BitPay.

I’ll check this out 🙏

Is there a master guide for Jellyfin setup from hardware to software? I am having trouble finding something as a server novice who wants to set it all up for my home.