This isn’t plausible at the moment because:
- the binary is expected to be all-inclusive but currently you need several. To run a service, we currently need orb, orb-ns, IPFS kubo.
- There are no other providers (e.g. no other mastodon servers) to join if you’re grumpy, so you’ll need to know how to administer a server.
- we don’t peer w/ any external networks on either IPFS or orb-ns
1 & 2 are currently surmountable by a motivated user.
To solve 3, we need to connect our kubo to the broader IPFS network and make orb-ns peerable. These are both concerning because clients may be well-intending, but not good peers. This may cause QoS concerns for callers.
To connect kubo more broadly, we need monitoring and perform experimentation around possible failure conditions, possibly including chaos testing, with an eye towards how those affect happy-case latency. To reduce underlying FUD, we should read the kubo source code. We could defer the kubo FUD by offloading concerns to web3.storage or maybe iroh.
To make orb-ns peerable, we need a mechanism to monitor “reputation” so that as reputation diminishes, they aren’t allowed to peer. We may be able to use the BitTorrent DHT directly to use their karma system via something like https://github.com/nuhvi/pkarr.