Is there a way to hide posts that have identical titles on identical sibling communities? My feed gets cluttered really fast when I’m subbed to a big community on two different instances because people often crosspost. I’m tempted to leave one, but I don’t want to miss anything.
Seems like an inelegant solution to a broader issue.
Do you have any suggestions for a better one? I’m all ears, but the solution definitely isn’t “hey guys stop crossposting”. Any other solution would require structural refactoring of Lemmy, and changes like that are not easy. I saw a post talking about combining sibling communities, but that would get very messy very fast. This solution is pretty elegant imo. Just a checkbox that says “I prefer posts from my main instance, hide any crossposts” would be perfect. No one has to subscribe to sibling communities either; if you’re fine sticking to one, then the issue doesn’t apply.
No, not with out a rethink of Lemmy writ large or without some changes to the activity hub protocol, you are correct to suggest that a ‘glued on’ cross posting solution might be the best answer. It also might be worth considering that Lemmy may well be the v1.0 and this issue could be addressed in a future protocol.
I’ll keep thinking on it, because its really the downfall of the whole thing. Lemmy can’t be a reddit killer because of this very issue. It forces a splintering of the network. Some how, users and posts need the ability to ‘move around’ the fediverse.
I’m hoping that, someday, we have support for what I described in another post:
It would be very beneficial to have clients that support aggregating equivalent communities from multiple instances. When viewing a post from the aggregated community there could be a section at the top saying “Viewing comments from:” and then a dropdown to choose between “all instances”, “lemmy.world”, “lemmy.ml”, etc. When viewing all comments, they would be in one combined feed, without the user needing to care about which underlying post holds the specific thread they’re looking at.
Similarly, when users post something to an aggregate community, they could select whether it’s posted to all the included communities, only one, or some specific subset.
But then you’re going to miss the conversation on the other community.
I’m okay with that, hence why I want it as an option I can opt-in to. If it’s the same person posting the same post and title to two different communities, I’d rather just see the one for my main instance and miss the conversation on the other, rather than seeing my feed cluttered with duplicates. I’m not unsubscribing to the other one, I won’t miss content unique to it.
I thought Lemmy already supported smart crossposting? You make one post, and then use the crosspost button (which isn’t in Sync yet I don’t think) and then you just have one post in your feed with a little link on it to the crossposts.
Or did I imagine that?
I guess it doesn’t do anything for people just posting the same thing twice to different communities.
I don’t think any app supports built in lemmy crossposts. I wouldn’t be surprised if people who joined after the lemmy app explosion don’t even realize it exists.
!remindme 3 days
