ZFS also directly addresses this issue in that a scrub can be setup in cron, which will detect any data issues and send email. One could do that with smartctl too, but that can be too late, where a ZFS scrub is more likely to let you know of issues before data loss.
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…
A rototiller was my first thought as well. Picking up the rocks will just require manual labor, but a tiller should do a good job of breaking up the clumps, though the soil might need to be amended with some other dirt/soil tilled in.
I use the spray cans, and it just takes some practice. If the result isn’t good you can wipe it off and try again. It’s not an easy skill to master at all.
Not this this helps you, but it’s been running solid here since upgrading. I’d take a look at the logs and see what’s going on, myself.
Definitely. As much as a centralized /c namespace is against all the principles of a decentralized system, lack of a centralized namespace results in topical duplication and hinders discovery. I don’t know how, but seems to me some sort of happy medium has to fall out.
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 (or at least doesn’t seem to be directly).
I never had much luck with the layout editors, so I just hand edit the JSON. Here’s part of my main dashboard (it scrolls on for a ways, but this much was already a big screenshot).
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 system-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!
i3 is what I’ve been using the past few years. I’ve tried others, but I always end back up with i3 as I’ve found nothing else to be as simple and efficient for my workflow, with 12 workspaces across 2 monitors.
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…
Thanks for your work in keeping this server up and available - should be an interesting ride for the next few days. :-)
We’ll usually have one meal of the chicken with mashed potatoes, then make a big batch of chicken enchiladas with whatever is leftover.