Some sort of user-controllable merging of community views would honestly alleviate most of this:
Adding something like user-specific topics, e.g. allowing the user to consolidate all posts from instanceA.communityA and instanceB.communityA and even instanceA.communityB into a custom community view shouldn’t be all that difficult to implement (he stated naively, having never looked at the codebase).
A great addition would also be to allow the merging of posts, e.g. show all comments of all threads under one post where the post URL matches and/or the title matches.
This isn’t exact, since multiple communities can discuss the same topic from completely opposite viewpoints, but at least allowing the user to consolidate stuff and control it would be huge.
You nailed my issue with the fundamental idea of lemmy. It’s like having a party at ten people’s houses with a tenth of the normal amount of guests.
Some sort of user-controllable merging of community views would honestly alleviate most of this:
Adding something like user-specific topics, e.g. allowing the user to consolidate all posts from instanceA.communityA and instanceB.communityA and even instanceA.communityB into a custom community view shouldn’t be all that difficult to implement (he stated naively, having never looked at the codebase).
A great addition would also be to allow the merging of posts, e.g. show all comments of all threads under one post where the post URL matches and/or the title matches.
This isn’t exact, since multiple communities can discuss the same topic from completely opposite viewpoints, but at least allowing the user to consolidate stuff and control it would be huge.