Forum federation thread on the.socialmusic.network

There is no ActivityPub category on Meta; there is a tag for that. And it's the tag that follows the category on your forum. So topics here are created uncategorized but with the #activitypub tag.Angus explained that before in April:https://meta.discourse.org/t/topics-made-with-activitypub-dont-have-a-category/360221/6

A community member moved the post to the support category. I guess I would have chosen the same category because, to me

strypey:

trying to get their heads around how to use the AP federation features

sounds like they need help (in contrast to, e.g., reporting a #bug or requesting a #feature).

Though the #general category, where it is now, of course, also works, as general works for everything.



Discuss this on our forum.

Ah, OK. Thanks for the clarification. I didn’t know both categories and tags on Discourse can be federated, that’s a cool feature. So just to be clear, our Discourse category on SH receives a federated copy of anything posted in any category on Meta with thr ActivityPub tag?

Coming back to the original topic, there is another thread on the.socialmusic.network about the interop between @discourse,
@nodebb and MBin, which raises a couple of UX issue to be ironed out in forum federation.

One is a variant of the same one we stumbled on in this thread. How to accurately communicate where a topic started, and where subsequent replies come from. Then there’s that old bugbear of fediverse threads, missing steps in the staircase of the conversation;

ā€œI can see this post from completely different software (Mbin), so that’s cool, but I don’t see replies from ā€˜social music network’, and for some reason it thinks that fedimusic community is on forum.wedistributeā€