Memmy - An iOS client for Lemmy

2536 readers

1 users here now

View on GitHub

Join the Discord

Code of Conduct

founded 1 year ago

MODERATORS

[email protected]

teflocarbon

[email protected]

241

Is anyone else noticing repeating posts when continuously scrolling? (lemm.ee)

submitted 1 year ago by [email protected] to c/[email protected]

39 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] TheBeanDream 1 points 1 year ago (1 children)

these are different communities with the same post in them

[–] reddig33 1 points 1 year ago (1 children)

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.

[–] TheBeanDream 2 points 1 year ago* (last edited 1 year ago) (1 children)

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

[–] reddig33 1 points 1 year ago (1 children)

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.

[–] TheBeanDream 2 points 1 year ago

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.