what do y'all think of this idea for managing identical posts in identically named communities?
Being subscribed to similar communities on multiple instances and seeing duplicates - Lemmy
Would be very nice to have after the initial hurdles of app development are wrapped up
So I'm actually against this idea. For some communities, the subject is the important thing. But for others, they're competing and they have different standards. Take memes for example. There's a memes community on every instance. Why would Star Trek memes be grouped with Solar Punk memes?
What I would say, is that some people are still stuck on the idea of karma and so they're desperately trying to spam their posts in every relevant community like clout matters. What they'll eventually realise is that they're just spreading their engagement and failing to support any of the moderators.
I think the point isnt all cross posts are collapsed into one, but that all identically named communities with identical posts are collapsed into one, and if you reply to a user then your comment goes to the relevant community that hosted that particular post (amongst all the other cross posts)
Top level comments don't work in this model. Which post do they go to?
Okay, so if I build a community and someone decides to build the same community on another instance, if they post stuff to both communities, there's a chance my stuff will be treated as the copycat and I lose traffic despite having built a massive community? It just seems like you're punishing me rather than the spammer.
what idea? i must be missing something, i only see the description of the problem, but not an idea of a solution?
The thread between sabreW4K3@lemmy.tf and I in this post might be more enlightening
what if users were able to group together communities client side kind of like it worked on reddit?
I might be wrong but I think this issue is due to the fundamental way Lemmy works (separate instances) and I'm not sure it's possible for Sync or any Lemmy app to do what the user Lvxferre suggested, although it's a wonderfully elegant suggestion.
I don't see this as a permanent fix. If this is easily implemented, I wouldn't be against it, but like all things sync, I would hope the feature would be OPTIONAL!
I would love it, been waiting for clients to do it.
I don't know, recently there were articles on Google's Web Environment Integrity published on different communities and each of them had slightly different takes in the comments, I feel de-duplicating posts would make me miss some part of the conversation or at least some of the point of views expressed in the different communities.
What if the conversations were merged into one page? You could have thread 1 from community A, thread 2 from community B etc all in one page, so you don't miss out on any comments.
In some ways a check box to block all bot accounts might be nice.
Do it like Ground News where it shows you stories, then when you click on it, it shows you the sources. Default click goes to your local source, but maybe add a button to view the cross posts.
It would help to merge them in some way while viewing a profile that constantly reposts their "content" to several communities at once.
The link I sent is about the comment of the post I sent, it just shows the other communities that have the same post, it's not one mod in control of all the other communities
I'd like to see the ability to regroup communities (at the user level, not visible to everyone) where the posts with an identical URL are regrouped as a single post. Would be useful to scan the news at least, without having a ton of duplicates.
there's a bug filed so @ljdawson@lemmy.world or @ljdawson@lemmy.ml can work on the crossposting feature
How it's that handled when each thread has differing comments, though?
I feel like for me, I just pick one of those duplicates and unsubscribe from the others
Not sure what would be the best way to handle it.