I know it’s currently under a lot of stress as a whole due to the recent events, but Lemmy needs to fix it’s scrolling in specific boards. Nothing worse than scrolling halfway through the feed, clicking a post, leaving the post, and ending up at the beginning of the feed.
For android I recommend Jerboa. Doesn’t have this issue and it’s getting more features by the day!
I’m actually running on jerboa lol
My jerboa was doing this to me yesterday, but today seems fine… no idea why its working now tho 😅
Or Mlem for IOS. Beta stages but it’s been really useful IMO and being updated
My Jerboa just did this as I saw this comment and again posting my own comment.
Is there a way to interact with Kbin magazines on Jerboa or is it for Lemmy only?
It works just the same as the web site! You can search or browse/scroll through local communities, subbed ones, or “all” (from all federated instances that are subbed to by anyone on your instance if I understand correctly).
Ooh, that’s nice to hear. Thank you, I’m going to try Jerboa now.
Correct! I have a lemmy.world account and use Jerboa for Lemmy for Android. I was able to briefly browse Beehaw before they defederated and can now browse kbin. I did absolutely nothing on my end except browse “All, top daily” and subscribed to whatever community/magazine made interesting posts.
Or Mlem for IOS. Beta stages but it’s been really useful IMO and being updated
I tried to access Mlem and got a “beta is full” message
Or Mlem for IOS. Beta stages but it’s been really useful IMO and being updated
Don’t quote me on it but I believe that is a known issue that is being worked on. Infact I thought I saw something about the recent 0.18 version of Lemmy having a fix for that.
I’ll quote you on that. I’ve seen the same discussion. It’s a known issue that really was a non-issue until the “dozens of us” turned into tens of thousands.
So true! I also have this issue that the feed seems to reload on its own or whatever that is and kicks me a few places up or down from where I was, kind of annoying.
This is a known issue with webscokets and will be changed in next version.
