• Has a simple backup and migration workflow. I recently had to backup and migrate a MediaWiki database. It was pretty smooth but not as simple as it could be. If your data model is spread across RDBMS and file, you need to provide a CLI tool that does the export/import.

• Easy to run as a systemd service. This is the main criteria for whether it will be easy to create a NixOS module.

• Has health endpoints for monitoring.

• Has an admin web UI that surfaces important configuration info.

• If there are external service dependencies like postgres or redis, then there needs to be a wealth of documentation on how those integrations work. Provide infrastructure as code examples! IME systemd and NixOS modules are very capable of deploying these kinds of distributed systems.

Silverbullet is nice

How long did you try it? It took me a good two months to get back to full speed.

I like AdGuard Home myself.

Wireguard is p2p.

EDIT: I guess the point is it’s doing peer discovery without static public IPs or DNS. Pretty cool!

Sounds a lot like the AT Protocol.

I’m not in the market, but I’ve actually had similar thoughts of building a project on top of NixOS that’s focused on self-hosting for homes and small businesses. I recently deployed my own router/server on a BeeLink mini PC and instead of using something like OpenWRT, I used NixOS, systemd-networkd, nftables, etc.

DM me if you want to discuss more. I think the idea has potential and I might be interested in helping if you can get the business model right (even if it just ends up being some FOSS thing).

Sorry if this sounds like a conspiracy theory, but how do we know that BlueSky isn’t padding their stats with internal bots? I could see this being a viable strategy to attract users and overcome the social network bootstrapping problem.

Book a night at Trump Tower.