If you wanted to make high-impact fediverse software, I would recommend making a simple daemon that does the following:

- Consumes RSS/Atom feeds
- Posts them as subscribable feeds over activitypub
- So dead easy you can host it yourself as a simple daemon on your server
- Optionally: collects replies as a comment section with a way to render them inline, a-la disqus, with some simple moderation tools. Simplest way to reduce spam would be to make it approve-only to show up on the feed.

You could extend this to allow posting on other servers etc. But, in other words, let more people use the static site generator they already have

@cwebber Bluesky's "you can block someone from your replies by blocking them" is a good start, I think it's worth exploring to just do replies as "Ask the OP server/account what the replies are. Sure, let the poster's server decide which replies are accepted. Want to post something the thread starter doesn't like? make your own thread!". This approach would allow some meaningful technical simplification in the distributed case I think
@mcc @cwebber hmm, isn't that basically how mastodons fetching of post context works?
@4censord @cwebber if so, control over it is not exposed to the user (except i guess in single-user server contexts?)
@mcc @cwebber i'm not actually certain if the post context endpoints respect the posters blocks
if it does, at least for anything that didn't federate directly to my instance, if you had blocked them i'd never see their reply under your post