All posts on my front page are from 2-4 days ago and no new posts are showing up there. I’m sorting by hot. Sorting by new does show activity in my subscribed communities.
Sorting by hot has been broken for me the entire time I’ve been here. I usually sort by top day or new
This instance hasn’t been updated to version 0.18 yet, don’t know if its related or not. Can’t use jerboa with this instance either because of that.
Jerboa does have limited use here. You just can’t post anything. I used it to comment here and to up vote.
I’m always nervous about installing an apk package into to my phone. Will Thunder ever be in the Play Store do you think?
The rumbling on the Fediverse is that Sync should be available for Lemmy in the Play store fairly soon. But maybe I’ll take the plunge with Thunder before that.
Get it from F-Droid, they compile it from the source code themselves
First I’m hearing of it, but so far this is a much better experience
The Sync dev is switching over to lemmy.
Oddly, Jerboa was working for me to post and everything, but I literally just got notified of an update via F-Droid, and now I can’t view all or sort properly. I was hoping for some fixes, but it seems even more broken now than before.
Sorting by ‘Active’ shows me the same posts that were at the top when I joined a week or two ago. I cycled between New, Hot, and New Comments depending on how stale things get. Another issue with these sorting options is that really active communities like Memes dominate my feed while the smaller communities fall by the wayside.
Yeah I have the same problem. Sorting by hot used to update all the time and now its been the same for days
quick fix for this is just restarting the server. Seems lemmy.one hasn’t been restarted since 5 days ago
5 days isn’t a long time in terms of server uptime 😕 something must be seriously wonky with the “hot” algorithm for it to break after the app has been running for a day or so.
Yes there’s an issue that already fixed in new version 0.18, but lemmy.one doesn’t seem to want to update for now. So I suggested the easiest workaround
You guys still getting this issue even with the update to 0.18?
Not that I’ve seen
