Probably more related to this: https://sfba.social/@sysop408/110639435788921057
Probably more related to this: https://sfba.social/@sysop408/110639435788921057
Threads will support the same protocol as Lemmy (which is called ActivityHub), meaning Thread-content is accessible in Lemmy (and other services) and the other way around.
By blocking Threads no content from there will arrive here and the other way around.
Additionally this isn't the community where this needs to be addressed. Either contact the admins or open an issue on GitHub.
It's not exactly what you're looking for, but still: https://lemmymap.feddit.de/ (might be slow to load).
Greek and Roman god names all the way!
Based on this thread it's the deduplication that requires a lot of RAM.
See also: https://wiki.freebsd.org/ZFSTuningGuide
Edit: from my understand the pool shouldn't become inaccessible tho and only get slow. So there might be another issue.
Edit2: here's a guide to check whether your system is limited by zfs' memory consumption: https://github.com/openzfs/zfs/issues/10251
fyi, I'm getting an 502 error when trying to open the preview...
(Sadly I can't program, so i can't help with the actual coding...)
I'm in the same boat, but didn't jump so yet. I've been following paperless for a while now but every time I look at scanners I'm blown away by their prices...
Yep, works now! Looks lovely although I miss the up- and downvotes personally...
Quite sad indeed... But I guess most of them already got with the subreddit closure :(
I counter with friggin Lasers! https://youtu.be/fH_x3kpG8Z4
Then why didn't you contact the devs or opened a bug report on GitHub?
For syncing I use Syncthing. It's open-source as well and syncs two/multiple devices without the need for cloud-storage