All the current ActivityPub implementations expect posts to be published by stable Actors, so you might need one of the following:
- A system account that publishes all posts
- One account per followable feed
- One account per followable feed, which makes
Announces of posts that are putatively authored by an account per Discourse user
The first is likely easiest to implement; the third does the best job of meshing the data models.
There’s also the choice of if we want to publish full topic content, topic first-posts only, or something like the StackExchange twitter feeds where distinct posts are made promoting posts from the /top page. Or that could just be how the “top posts” feed works, and the other feeds publish everything…
On a technical level, the URL should not need to change: all servers will send Accept: application/activity+json or its alternates.
A reader application that mixes feeds from different sources at different times in ActivityPub - recreating the “algorithmic timeline” as an opt-in thing - is something I’ve been wanting for a while, and doesn’t seem to be existent today.
@hellekin: I think that cross-domain authoring has a high chance of fatally circumventing a lot of the anti-spam protections that Discourse has. Reading is more important to implement: after all, Reading is Fundamental!