This has been a long standing issue, not just in the last update. Force stop then clear cache and it’ll be better… For a while…

Yep, I had the same problem - see my previous post on lagginess in this /c. Force closing and clearing app cache resolved it for me.

Everyone keeps confusing this with a server load issue, which it isn’t.

Doesn’t seem to be a server-side related issue as far as I can tell, but the app itself - after clearing app cache it’s running much better now.

Thanks, after clearing cache it’s much better now - force closing wasn’t quite enough.

Overall it’s going well, and experience from both browser and Jerboa is great, especially considering the lack of maturity and large influx. It’s been amazing to see how quickly communities have shown up. A couple of weeks ago when I first heard about Lemmy and plans for Reddit subs going dark, I looked at Lemmy and walked away with a meh because of lack of content, and what was here was not my thing. However, throughout the day today I watched the number of communities grow like crazy, with new topical communities popping up every time I checked.

I do think lack of a centralized /c/ namespace makes things confusing for a lot of people, and will result in a lot of topical duplication between servers - even with federated access and searching. I get why lack of a centralized namespace is also a design feature, but it comes at a price, in my opinion, and it’ll be interesting to see how it works itself out over time. Just an observation/opinion on my part.

Still a bit early to call it, but it’s looking good!

You can search communities, but not posts or comments yet - https://github.com/dessalines/jerboa/issues/27

I’ve been wondering about this too - sometimes it subscribes immediately, sometimes it gets stuck pending. Hopefully the pending ones work themselves out per the other comments…