This is fantastic. Is there any way kbin.cafe could be included in the list of includes? It's a top-8 server and it'd be super nice if it "just worked".
50 TB on a network attached storage appliance across 8 drives, probably 200-400 GB across two laptop internal drives, and 500 GB or so of games on a Framework expansion card.
I may have a problem. Something something r/datahoarder something something.
Are there any plans to create a more friendly website that highlights instances based on certain traits (i.e. country-specific instances; general-purpose instances; hobby/interest-specific instances)? Right now discoverability seems limited to the Fediverse Observer and FediDB, which shows /kbin instances by user activity.
Little known trick--or perhaps everyone knows it and is quietly laughing behind my back--with Chromium browsers and Firefox (and maybe Safari, I'm not sure), you can add a slash to the end of an address and it will bypass the search.
So, for example, my router on the LAN goes by the hostname "pfsense". I can then type pfsense.lan/ into my address bar and it will bring me to the web UI, no HTTP/s needed.
I didn't care about any of this (my off the shelf Router used .local) and then I started selfhosting more and using pFsense as a router OS. It defaulted to using home.arpa, which was so objectionable that I spent time looking into RFC 6762 and promptly reverted to .lan forever.
The official choices were: .intranet, .internal, .home, .lan, .corp, and .private. LAN was the shortest and most applicable. Choice made.
Shameless plug: I made a magazine, @rss, for RSS. It has approximately zero content right now but I'd love for people to start using it to exchange ideas, comments, and questions about feeds.
It would be lovely if posts had a unique ID (UUID of some sort) that was shared between instances. That way, rather than using the thread ID, a unique ID is used that points at that particular thread, comment, or microblog. But alas, this doesn't exist, and we're here.
I use Vaultwarden in Docker, which is a light-weight Rust implementation of the Bitwarden server. You can just point any of the apps or browser extensions to your server at login and it works seamlessly. The oficial Bitwarden Server is also available, but when last I used it, it was much more resource intensive and had a number of docker containers as dependencies instead of the single container for Vaultwarden.
For UniFi, I use a docker image--currently, I'm using this one.