Post History

I'm not sure if this is actually an answer or not, but [as suggested in a comment thread](/comments/thread/7533), I'll put it out there and see what happens.

My understanding is that Fediverse / ActivityPub support doesn't necessarily *have* to be both ways. Bidirectional federation is *definitely* more useful, but there can be some value even in read-only feeds.

Therefore, how about **as a first step**, in much the same way as with the RSS/Atom feeds, *publishing ActivityPub feeds* but not implementing support for federation *input*?

I see this being primarily useful for categories and users; at least on Mastodon, this would map nicely to how people can follow either a hashtag or a user. Since ActivityPub supports threads and sub-threads, follow-up posts to a top-level post could map to replies referencing the original post likely to a largely arbitrary depth. (For example, a question could have its answers and comments, and answers to a question could have their comments, as replies.)

Starting out with read-only (export) federation should avoid many of the issues raised in [the previous answer](#answer-288361) while allowing Codidact/QPixel to at least dip its toes into the Fediverse by letting people follow Codidact communities from and easily share Codidact posts within the Fediverse.

Do note that there may be technical reasons which I am simply unaware of why read-only/export-only ActivityPub support is not feasible or meaningful. If there are, then that would invalidate this suggestion.