Skip Navigation

One of the things that the recent addition of the Feeds feature highlighted was how many cross-posts / duplicate posts there are. When you display posts from linux@lemmy.world, linux@programming.dev, linux@lemmy.ml, etc all the cross-posts make it get repetitive, really fast. The same thing happens on the home feed too although it's a bit less obvious because there's a wider range of subjects involved.

Except now, it doesn't, because PieFed de-duplicates your feed! And your home page, and your topics. Attached to this post is a screenshot showing how it works out - an article posted to 7 different places is only shown once despite me having joined most of those communities.

We're still figuring out whether it's a good idea to merge all the comments from all the cross-posts into one page and how to do that in a way that respects the different culture/rules in the communities that the posts were made in. It's a tricky UX and social question.

I've held off on adding a cross-post function to PieFed until now but it'll be added soon.

Fediverse @lemmy.world
XNX @slrpnk.net

PieFed supports auto merging threads so you see all the comments in one post
Meta @jlai.lu
inlandempire @jlai.lu

Piefed peut désormais rassembler les postes doublons
23 comments

  • @rimu@piefed.social Omg! You're a life saver! That was what was really bothering me lately! So many duplicates!

    • Yup and it's only going to get worse as Lemmy usage increases.

      • Hehehe, not anymore... :-)

        (Well, I guess still those that don't involve a link, but this is still a great step forward, worth celebrating! 🎉🎊🥇🥳🍾🍺🎆🎇🎈)

  • A welcome side-effect of this work is that going to another page of posts will maintain your place in the stream so you won't occasionally see one or two posts from the previous page at the top of your new page.

    • Oh wow, that is a welcome side-effect: almost as news-worthy as the main feature!

    • Oh is that what the result_id in the URL is for?

      I think I might've spotted an unintended side-effect, actually not sure if that was there already but it grabbed my attention now:

      On the first page of my feed, when I select the menu of a post to go block the community that this post is in, the page changes into that community with the mention above that it's hidden now, and when I page-back I return to my feed with that post not visible anymore.

      Now on the second and later pages, if I do the same, and then do a page-back, the post is not hidden anymore. Refreshing doesn't hide it either, I have to redo my scrolling from page 1 onwards if I wanted those communities that I just blocked to be hidden.

  • Bah, it relies on people actually cross-posting, and not re-uploading the image every time, of course. I've just seen the posts from this user and they're all different URLs. Maybe a function can be added for admins to fix-up posts like that to de-dupe them (it'll last until the OP edits the post, at least).

    • We do have a function to de-dupe those - click the 3 dots and then look for 'Delete' ;-)

      What if.... when an image is uploaded we generate a unique hash of the image data and save the file to the server using that hash as the file name. That way if the same image is uploaded multiple times it'll get the same name each time. Each post will have the same url and the usual cross-posting detection mechanism will take care of it.

      Anyone see any problems with this?

      • That sounds like a better idea (when you're looking for them, you realise how many people don't actually cross-post stuff "properly").

  • I really never noticed this as an issue as much as everyone likes to say. But cool

23 comments