When scrolling through the main feed eventually I will hit a point where it’s roughly the same 20 or so posts on repeat. The posts might not be in the exact same order and new content will be mixed in.
In Apollo it would eventually hit “the bottom” of the feed and it wouldn’t go any further. This feels like the app is fetching the next posts but without a full page of results it’s returning the same posts again and again.
Anyone else seeing this?
yep, this is happening quite a lot for me
yep, this is happening quite a lot for me
yep, this is happening quite a lot for me
yep, this is happening quite a lot for me
Yep, this is happening quite a lot for me
yep, this is happening quite a lot for me
I’ve noticed this also
yep, this is happening quite a lot for me
Yes, and I waited until this came up a second time to write this lol
Why are you being downvoted lol
I have been noticing this more and more lately. Also as the gaps between posts gets larger the more posts I see repeated.
I have noticed this too. I was very excited to have the “mark read on scroll” option added with the update yesterday.
However, as I am scrolling and marking posts read I have noticed that a lot of the posts that were marked read keep reappearing as unread. Not other instances, but the same posts.
Hard to capture this in the wild, but I will try to get images of this happening.
I’m experiencing the same unread issue when marking comments as read to clear out my inbox. Everything just reappears as it was.
Tbf, lemmy is a smaller community
Yeah, I go back and forth between Lemmy and Mastodon for content consumption (and Pixelfed when I want to strictly look at pictures), using Fedilab you can follow hashtags to curate your home feed. Plus you can still read Lemmy posts and comment on them, but a lot of the time you’re shown comment replies to a post on your feed with no context until you select it, so it’s a little weird in that aspect.
Someone was explaining this to me last week. The algorithm goes by comments and upvotes. I was seeing 3 year old posts but had upvoted before I saw how old it was. That sent it back hot and then someone probably made the same mistake and so on, which made the post get hotter. I think they’re re-configuring the algorithm so it may change.
Also, this is conjecture, but I think when you’re in all, you’re seeing your instance’s version and everyone else’s version of the same post. So if someone from your instance upvotes, it makes it hotter. Please correct me if I’m wrong, I’m not positive this is the case.
I’m seeing the same thing as OP. This is definitely a bug. There will be a gap in posts, like a “missing” post and then I’ll see the same exact post(s) come up from the same community as before.
This is on the TestFlight version which the devs have acknowledged is a little broke right now.
I now realized I should have specified I’m using the TestFlight release.
I hadn’t made a connection to the blank posts, I’ll need to keep an eye on that to see if I notice the same behavior.
It’s interesting because the same post will have different upvote and comment counts. For example - the “Nilla ready to go for a walk” post in aww.
One post says Lemmy.world and another says Lemmy.ml — so is this the same aww, or two different subs with the same name and the exact same submitter and the exact same content?
these are different communities with the same post in them
Yep. It is a weird design decision to allow the exact same community name for two different communities. It’s encouraging cross posting, dilution of community, and repeated duplicate posts in the “All” feed.
It’s kind of the entire point of lemmy, it’s decentralized. Nobody can control other instances. There’s nobody “allowing” it including the lemmy devs
I don’t think there’s a problem with having a sub named “aww” and a sub named “awww” or “startrek” and “star_trek” — but I think allowing each instance to create distinctly different subs with the exact same name is problematic for the reasons I previously outlined. It’s not a control issue — it should be built into the system. Just like Usenet and dns servers don’t allow entries with the same name.
I don’t think what you’re describing is technically feasible. If it worked how you describe, then when someone makes a community that instance would have to somehow go and ask every single other instance in existence - hey do you have this community name already? We wouldn’t be able to like, keep a database of all the existing communities everywhere.
This sounds similar to something I fixed in a different Lemmy app. I think this issue existed in a few other apps too at one point. But basically, It’s possible that when you fetch the second page of posts from Lemmy, it can give you a post that was present in the first page fetch. It can also give you chunks of duplicates. Very annoying. But yeah I’m sure it’s something that will get addressed.
Same! I thought I was losing my mind.
Every instance has its own members and creates its own content. So, for example, a relevant new is posted in multiple instances, thus you see it multiple times. The most common occurrence of duplicate content.
yep, this is happening quite a lot for me
Yes I’ve been noticing this and unfortunately my brief research into has resulted in no fixes
I don’t think this is resolvable without some reworking by the devs.
Yeah, the posts are a bit wacky on all too since different instances subscribed to all communities have differing /all posts
Oh man glad to know I wasn’t going crazy or accidentally scrolling up somehow or that reposts aren’t that bad yet
Yep, seeing it too, and weird gaps in the feed too.
