cross-posted from: https://piefed.social/post/538685
No more duplicate posts
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 [email protected], [email protected], [email protected], 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.
I believe I understand it. To clarify:
The normal Thunder app works perfectly with Lemmy instances. I’ve got it and while I haven’t registered my account with it yet, it works very well even as a guest to read content - it’s a great app!:-)
There is also a fork for the app, designed specifically for testing purposes, which only works atm (iirc) for a single PieFed instance. This fork no longer works with any Lemmy instances, nor any instances of PieFed either that aren’t running the API code. So it’s testing the backend and frontend connections, requiring specializations on both ends to work at all.
When all of that is done, the fork can be requested to be merged into the main branch, and become a standard feature of Thunder, to work either with Lemmy or with PieFed instances.
But notably, getting to what I thought you meant: PieFed itself still connects perfectly to Lemmy, due to its implementation of the ActivityPub protocol (and Mastodon, Friendica, Pixelfed, Loops, and whatever else may also use that same ActivityPub protocol to share content).
I hope this explanation helps at least a little!:-)