I expect that should be fine, but there’s a URL signature scheme that is apparently involved, I’m worried that should I turn up a new instance, it won’t federate with e.g. mastodon.social
I expect that should be fine, but there’s a URL signature scheme that is apparently involved, I’m worried that should I turn up a new instance, it won’t federate with e.g. mastodon.social
At the simplest I feel a chrome extension or similar would be straightforward. A more native flow doing some sort of faux login/modal that could subscribe on the primary host would be better.
The backend especially is not too demanding (thanks to using a compiled binary via Rust). The database demands probably scale, but postgres scaling is relatively well understood. I think right now the least scalable parts look like the frontend node and websocket stuff, but that can be improved. I’m not sure how I feel about Activity Pub protocol wise, it feels pretty chatty, so transit scalability might be something else to consider.
Once you add things to the AllowList, only things in the AllowList federate. You probably want to use empty AllowList + populate BlockList as needed.