Two posts, two different instances, two different sets of comments. Ok, there are pros and cons:
Segmenting the conversation means that different opinions and perspectives have a bigger opportunity to rise to the top in each discussion. That’s good.
There is also a risk of too few different viewpoints being present in one instance or another, making the possibility of an echo chamber forming higher. That’s bad.
I’m not suggesting that there’s a single perfect way to handle it, nothing is that black and white, but maybe there is a chance to do better. Perhaps crossposted content could contain a second link underneath between the body of the post and the comments section that could inform users that an identical post existed on another instance. Perhaps the comment sections could be merged but the user could choose to filter by instance if they wanted to.
I would love to have them linked more strongly. I do think that it makes sense to separate comments. If only because moderation rules are different for different communities. But it would be nice to group them in the feed.
Maybe if the cross post could be identified and the comments merged into tabs where you can jump between them for the same post. So instead of 5 copies of the same link showing up with 5 sets of comments all of them are merged to one and when you click on the comment section it allows you to cycle through all of the different instances discussing it. It would clean up the feed but still allow you to see what each group is saying and where they are saying it.
I’d love to have a link for a news article wheee I can jump between what all the various instances are saying so I don’t miss anything.
deleted by creator
That sounds like a job for a client and not necessarily Lemmy the service
Being able to merge them even if they aren’t both visible in the same page of your feed or even just efficiently looking up cross-posts would probably need server assistance. Ideally it could be done in a way that a client could choose to or not to merge them.
I’m not sure about that. For actual cross posts, where the server is aware of the posts that are connected, it’d just be a matter of fetching all the sets of comments rather than just the one.
For when no one has actually cross posted but just posted the same link to a different community, that gets slightly trickier.
Any sort of solution though would require some service, whether on the instances or a separate bot, to scan for identical URLs and make connections for the frontend or client to then use. In such a case, the backend would need some idea or structure for a post hoc cross post, which would identify separate posts as being related in a way separate but similar to the cross-posted information.
I also wonder if only the creator of the thread should be able to cross post it? Not sure if there is a reason why it does not behave like this at the moment - sure there is!
No, the creator might not know of all the communities where the post might be relevant. You’d end up either with everyone bugging the poster to xpost it everywhere; or everyone just copying the post, making things worse.
Seeing an xpost might lead you to finding nee communities you didn’t know, it’s one of the best discovery tools.
That makes sense, hadn’t even occurred to me!
I myself use cross-posting as a bookmark in my instance. Not a deal breaker, but would prefer to keep doing that.
Ah makes sense!
lemmy-ui actually groups them together. It all depends on the app / frontend implementation that you’re using.
Here is how the OPs example shows up with all the x-posted communities listed.
I have noticed, though, that two posts of the same URL within a single community are also listed as x-posted, and the “duplicates” don’t show up in the community’s feed at all. Which can be problematic if you’re linking to a page with a static URL that changes over time (such as sports league statistics). The trick so far has been to highlight text that has changed on the page and get a link to the highlighted text.
deleted by creator
My biggest issue with crossposts is when people don’t use it, but make new, unlinked posts :-P
I liked the idea from this comment:
Show comment sections from all other posts combined in each crosspost. View options:
- All combined in one
- Each post on it’s own
(So for a post with 2 crossposts, there exist 3 posts. The comment section has 3 tabs for each post, and a 4th tab for the combined view.)
It might make sense to (optionally) normalize comment scores for combined views. How well did this comment fare relative to it’s post and sibling comments?
Spending 2 minutes on GitHub, I haven’t found a related issue in either lemmy or lemmy-ui.
