116
Feature suggestion: duplicate posts handling
(programming.dev)
Hello LJDawson, let me start with saying how happy I am to have Sync back :)
The one issue I have with Lemmy is duplicated posts between different communities (see screenshot). Posts usually have same title, author and link, yet differ in community/server they are posted to. It would be great to be able to make the appear as one item on the feed with some note below that links to both instances' posts, or something like that basically to make them not appear twice or thrice one under another.
Playing devil's advocate for a bit... So these are just cross-posts. Which existed even on Reddit. ...I assume they weren't handled in any way in Sync or Reddit?
But let's say this is fixed... What to do about the multiple comments threads? How would you reconcile them with each other? Especially since the user can choose different ways to sort the comments as well. Would all of this logic normally handled by the Lemmy back-end now need to run on your phone? Also how do you choose which post / instance to actually display and which ones to hide?
Btw, I'm not trying to dismiss the idea. Just want to call out some of the technical problems that might come up trying to implement such a feature. As well as ask questions to try and determine exactly how such a feature is expected to work.
Have the various comment threads on a carousel once you click in. Because of the fractured nature of Lemmy servers I feel like I see way more reposts than on Reddit. It would be nice for them to get merged in some way.
Yeah, I also think this is more of a Lemmy problem, rather than sync one.
Even if they are called the same at the end of the day they are different communities hosted on separate instances.
Just because it's a Lemmy problem, doesn't mean Sync can't do anything about it, for it's user's benefit.
It's fine to dismiss the idea, because on reddit you could see the same user post the exact same article on a dozen relevant subs. If you try to hide them, which one do you hide?
It's a stupid idea, akin to wanting to ban all reposts.
There are a few ways to handle it, but yes it would either need to be done client side or via a server proxy.
I am actually toying around with something (that I may or may not release publicly, depends on how far I get before I lose interest) to help app developers do stuff like this without heavy processing on the client.
Since this issue is most prevalent while browsing new, you could temporarily store (a hash of) the titles and contents of each post during a given browsing session, and if a post matches another post on the same page (e.g. one set of posts from Everything/new), hide it and allow the user to see comments from each instance of the post when they view the canonical (earliest, or most active, or returned first) post.
If another duplicate post is later loaded (through scrolling) the post could be hidden and replaced with a smaller indicator telling the user a duplicate post has been detected, and they can click it to view the comments.
I would imagine one post preview with a very compact list of instances on which the posts were posted so that you can enter either of those posts' view.
Or merge the posts into one view, show somehow it's a merged post, and merge comments as well (and let you choose the instance on which you want to comment if you create a new top-level comment).
Reddit had similar issue but it wasn't that bad since you hardly ever had 2-4 similar communities - something that appears to be very common with decentralised lemmy.