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...
ScottE
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.
I use Manjaro, but I run it like vanilla Arch (for example pacman/yay and not pamac). I find this to be a sweet spot for me - rolling releases are so incredibly nice, and Manjaro being slightly slower than Arch is good from a stability standpoint in my experience.
I use ZFS all over the place, including the root storage pool on my home server, which has overall been a great experience with systemd-boot.
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
None - I don't run any DE, just a WM - i3. All I need is a terminal, browser, sublime-text for larger projects, and that's about it.