This is turning into a deal breaker for me. It doesn’t matter what instance I’m on, or what I have selected from the dropdown (or browser I’m using), but “new” posts are constantly flooding the feed list.
First, new posts shouldn’t even show if I specifically select a different view. Second, they flood things so fast I can’t even click on the things I’m interested in. If I look away from the page for 30 seconds it’s just junk.
I’ve had two other people tell me they are seeing the same thing. Tested on MacOS and Windows. Chrome/Brave/Firefox/Safari.
Anyone have a fix?
Yeah, I’m seeing this as well. If I had to guess, I think it’s because of new posts being cached on your home server. Like, someone goes out and subs to a new instance formerly unseen by your instance, and all the recent posts are suddenly cached and somehow pop up in your feed? I agree it shouldn’t be happening, and the age of the posts that are flooding my feed don’t seem to correspond with the view I use. I also notice that I get a lot of posts from the same community all at once.
Yes, I’m confused, then most of those posts that flooded the view disappear? I don’t get it.
I’m getting the same issue, as soon as I choose to see “all” it floods the page with new posts from everywhere (ironically that’s where I saw your post). Any fixes?
i have seen this as well. i’m pretty sure the devs are aware and i’m hoping it will be fixed in the next version where they are no longer use websockets.
I don’t know if this is a feature but could this be implemented temporarily?
- trusted high volume external instances like beehaw or lemmy.ml or lemmy.world updates at say 2 mins. (I estimated by my reading speed where it took about 2 mins to read through and tab out for one page worth of posts)
- all the other instances only accept update every 10~30mins depending if they have bot contents.
I think locally we are fine, but we do need to go to “All” to see something interesting so we can start tuning our subs.
i don’t believe there’s a way to do that, currently. will have another scan through the configs/docs and see if there’s anything that may help.
Welp, I think it’s pretty clear Lemmy is not ready for primetime. The number of new bugs filed vs. the number of people working on the project, doesn’t inspire much hope for things like this particular issue. And the fact that all instances combined still have fewer people online right now than some of the average size subreddits, means people don’t really give a shit about the API change. In the end, Lemmy might get a nice little bump, but Reddit isn’t going anywhere.
I’ll definitely keep an eye on Lemmy for the future, but it’s not going to replace anything for me.
It ought to improve with the move to version 0.18, which was just released today. They are replacing the WebSocket API connections with HTTP(S, I hope) connections in order to reduce the amount of traffic going back and forth. I don’t know for sure, but I think this will take out the real-time updating feature that causes these feeds to move around while you’re reading them.
Here’s the list of what they have done for 0.18, and it’s clear they have been working hard:
