@gargron I think this is the thing about making very general ActivityPub backends... especially if you include the c2s api... eventually you hit the point where a lot of decisions are client-presentation. I've debated in MediaGoblin whether we should include "normal" social networking experience things. In the federation branch most of the backend functionality for that ended up growing... "Should we just not include this because it's not what our original mission was? Is that a good reason?"
@gargron We could end up at the point where people have very general AP backends and end up selecting their usecase-appropriate frontends. Would that be a good or a bad thing?