unable to scroll past the first page when sorting by hot
unable to scroll past the first page when sorting by hot
When I open the app it's default to sort by hot. I can't scroll past the first page, it fails to load any more posts. If I sort by top 6 or 12 hour it works.
Anyone else experiencing this or know what I can do to fix it?
Similar behavior here, but it doesn't matter if it's Active, Hot, New, etc. Nothing loads past the first page; it spins and throw the error/retry at the bottom.
It DOES work if I switch to the "Subscribed" feed but not "Local" or "All."
It also works if I switch to anonymous. Might be server-specific?
Ok I just tried like you said and switched to subscribed and it works fine on hot but not the others.
I experienced this on my instance on just regular desktop browsing for a while, so I don't think it's necessarily an issue with your client; it did eventually just go away on its own (somewhere around the time the instance backend updated, I'm sure), but I also found that switching on "show hidden posts" fixed it as well, and since I don't really have any hidden posts it didn't make much difference. Downside was I had to do that manually every time, but it did at least get me to the second page.
Interesting. I tried other sorting methods and even scaled won't load more posts but top by "whatever" will load all day. I'm a rare exception here in that I know fuck all about computer stuff so I have no idea. I think I saw someone saying the same thing on the boost instance so it must be a wider thing. I'll try the hidden post thing but I'm not sure if that's a thing on jerboa? I've never intentionally hidden anything, just blocked shit I don't wanna see. Thanks for the reply.
Yeah unfortunately I'm not terribly familiar with this client, I just wandered in here from - and I hate to say it, given the circumstances - the second page of hot, so I'm not sure what all options you have available, but if the button's there that might fix it.
Now, it does look like your instance is running version 0.19.5 whereas mine's on 0.19.6, so it'll probably be fixed once an update goes through, whenever that may be.
Had the same problem but now it seems like it fixed itself.
which version are you using?
0.0.77