I feel like there’s an easy win to keep up with the fragmentation of discussions without waiting for some implementation of this feature request.
All a frontend needs to do is group all posts with the same URL together and display all their comments in the as one unified comment section. If you reply to the OP, you can either choose which community the comment goes to, and maybe set a default as well.
This functionality should be an extra switch for the frontend, so that the user can disable it and see individual posts.
This also nicely avoids not knowing how to deal with moderation, as each community moderator still maintains control.
Comments from blocked communities would not appear ofc.
This would both prevent seeing the same post multiple times on your feed, but also drive view to smaller communities where comment in their sections are ignored.
My question is why is this a backend universal question? This should be a per user/instance frontend solution; meaning I would curate my communities into a group on
@lemmy.worldand it’s unique to me.Now I should be able to export or share my groupings if I want, and it should be read-only in the sense that if I post, I post to a single community and not the group as a whole. The only thing a backend should do is allow the frontend to retrieve posts from multiple communities in one call.
In other words, keep it simple.
This is what this post is suggesting, yes