I know that it’s a core design feature of Lemmy and the underlying federation, but it’s pretty annoying that multiple communities with the same name can exist on different instances while not necessarily following the same ruleset or even purpose.
The small user base gets even more fractured that way, a lot of posts get reposted to multiple instances as well.
So you either:
subscribe to one or two communities and miss a lot of potentially interesting conversations
subscribe to more communities and get flooded with reposts and potentially stuff you don’t want to see due to a different ruleset
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.
On a user level I agree it’s a very good feature (if configurable, not just an automatic grouping of similarly named communities). For merging post, not sure I want that, perhaps a bit too smart… Now if many users want this why not (as long as there is a setting to turn it off ;)).
I know that it’s a core design feature of Lemmy and the underlying federation, but it’s pretty annoying that multiple communities with the same name can exist on different instances while not necessarily following the same ruleset or even purpose.
The small user base gets even more fractured that way, a lot of posts get reposted to multiple instances as well.
So you either:
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.
On a user level I agree it’s a very good feature (if configurable, not just an automatic grouping of similarly named communities). For merging post, not sure I want that, perhaps a bit too smart… Now if many users want this why not (as long as there is a setting to turn it off ;)).
Do you think that the ability to hide duplicate posts could solve this?