- cross-posted to:
- piefed_meta@piefed.social
- cross-posted to:
- piefed_meta@piefed.social
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 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.
Oh shit is there an app?
Edit: doesn’t work too well with Lemmy instances yet
Double edit: apparently it does…?
Not “fully”, but testing is underway for Thunder (a FOSS Lemmy app) - https://piefed.social/post/484755.
Why do you say that it doesn’t work well with Lemmy instances yet? I’ve been using piefed.social for ~5 months now, and while I do often see connection issues (maybe once a month?), I likewise experienced first-hand many, Many, MANY other connection issues on several Lemmy instances (StarTrek.website got so bad that I left it for Discuss.Online, which I would say has such issues only exceedingly rarely) plus constantly hear about many issues on other instances (Lemmy.world delays with many other instances especially aussie.zone, programming.dev database corruption, images not showing on Lemmy.cafe, etc.).
The connection issues on PieFed.social in particular I believe may have little to do with PieFed as software in general and rather much to do with PieFed.social in particular being a bleeding edge testing ground for new features. Which I knew and consented to as I made my account (and advise people to keep a Lemmy backup alt, although that’s just good advice for any Lemmy instance too), but there are other instances running PieFed that someone can choose if they want greater stability - notably feddit.online as the largest one.
So that’s my take, but perhaps you have more details you can add? If you were referring to this old post, that was only referring to someone starting up their own instance using PieFed, and they said themselves that the issue resolved itself in half an hour after posting.
TLDR: you’re not exactly wrong per se, but it comes across as cherry picking to imply that Lemmy has no such issues working even with software on both sides being Lemmy. But perhaps I am missing something and I’d love to read more if you have any details you’d like to share:-).
Let me see if I can find the link that I found
Yes, please do!
Come to think of it, I am aware of one issue where PieFed won’t automatically pull in content when it receives a vote for it - but I discount that as being a problem bc that’s a major issue even among Lemmy instances, just in different ways. I could show you some examples where my votes on a post vary from like 200 to 0 or anywhere in-between (that particular issue was from the post being locked, which ofc I received no notification of that happening, it just screwed up the federation of it across the entire Fediverse).
Also, the issue I’m thinking of would only affect a brand-new PieFed instance, not an established one that receives the post content as it federated out. And too, the way that Lemmy would handle this would lead to improper vote counts: imagine hypothetically that a post got +1000 upvotes and only 10 downvotes, but then the moment your brand-new Lemmy instance goes online you start to receive exclusively new votes for this post, and let’s say that it receives +2 more upvotes and another 10 downvotes. In this (hypothetical) scenario, the vote counts are MAGNITUDES off from what they should be - instead of showing +983 it would show as -7, thus misrepresenting a “highly popular” post as a “fairly unpopular” one. Lemmy’s approach is to have the post but allow the vote counts to be incorrect, whereas PieFed’s approach is to not pull in the post in the first place (unless someone manually makes that determination to override - which anyone can do, though I’ve argued that this should be a feature that is slightly more hidden or at least not as readily shown to users who, like myself at the time, could unknowingly cause spread of misinformation by not knowing all of these technical details).
So it’s not that Lemmy’s way is “right” and PieFed’s is “wrong”, but rather both are kinda wrong, iirc, and yet only affecting old posts that brand-new instances are trying to work with, so very much an edge scenario.
But if there’s something I missed, yes please send me the link - I would like to be informed!:-)
I believe I saw this
https://piefed.social/post/484755
Did I read this wrong?
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!:-)
ah damn they arent even developing an ios version so this platform stays irrelevant to me
What do you mean?
First, there’s a version of Thunder available on the App Store.
And second, PieFed offers better service in its web browser interface than any Lemmy instance I’ve seen, and most apps too. Like, Voyager is pretty awesome and a strong contender for best Lemmy app (especially among FOSS options), but it doesn’t have categories of communities, hashtag support, user customizable and shareable Feeds (like multi-Reddits), cross posting that shows all comments merged into one view, etc. and a lot of features that it does have can be quite buried within the interface. e.g. to read the rules of a community you have to navigate to it, then click the hamburger menu and choose the side-bar option, whereas on PieFed the rules are displayed directly underneath every single post, so all you have to do is scroll.
Now, mind you, the standard Thunder app won’t work yet for PieFed - it’s still being tested in a forked version of the code, not committed yet to the main branch of the code. So if that’s a deal-breaker for you, then yeah you should stick with Lemmy - FOR NOW!:-D - but there is movement towards supporting that, which i think is fucking awesome 😎. Lemmy is so slow to add new features, while we get them here on PieFed basically weekly at this point.
The app or piefed as a whole?