Kata1yst

Over the years of using Vim both professionally and for my own uses, I’ve learned to just install LunarVim and only add a handful of packages/overrides. Otherwise I just waste too much time tinkering and not doing the things I need to.

I use FreshRSS. Can’t say I love the interface, but with the open and standardized API, there are dozens of beautiful front ends to choose on any device.

For real? Damn it that’s going to be painful.

Never ask a man his pay, a woman her weight, or a data horder the contents of their stash.

Jk. Mostly.

I have a similar-ish set up to @Davel23 , I have a couple of cool use cases.

• I seed the last 5 arch and opensuse (a few different flavors) ISOs at all times

• I run an ArchiveBot for archive.org

• I scan nontrivial mail (the paper kind) and store it in docspell for later OCR searches, tax purposes etc.

• I help keep Sci-Hub healthy

• I host several services for de-googling, including Nextcloud, Blocky, Immich, and Searxng

• I run Navidrome, that has mostly (and hopefully will soon completely) replace Spotify for my family.

• I run Plex (hoping to move to Jellyfin sometime, but there’s inertial resistance to that) that has completely replaced Disney streaming, Netflix streaming, etc for me and my extended family.

• I host backups for my family and close friends with an S3 and WebDAV backup target

I run 4x14TB, 2x8TB, 2x4TB, all from serverpartsdeals, in a ZFS RAID10 with two 1TB cache dives, so half of the spinning rust usable at ~35TB, and right now I’m at 62% utilization. I usually expand at about 85%

No, I’m not conflating “a” with “b”. I’m using stability exactly as it’s used in physics.
https://phys.libretexts.org/Bookshelves/College_Physics/College_Physics_1e_(OpenStax)/09%3A_Statics_and_Torque/9.03%3A_Stability

My point is, it’s a completely valid use of the word. And yes, so is reliable, though I think “reliable” fails to capture the essence of the system changing but maintaining it’s state, hence why we don’t study “reliable systems” in physics.

I recommend picking something else to be pedantic about.

Amazingly, for someone so eager to give a lesson in linguistics, you managed to ignore literal definitions of the words in question and entirely skip relevant information in my (quite short) reply.

Both are widely used in that context. Language is like that.

Further, the textbook definition of Stability-

the quality, state, or degree of being stable: such as

a: the strength to stand or endure : firmness

b: the property of a body that causes it when disturbed from a condition of equilibrium or steady motion to develop forces or moments that restore the original condition

c: resistance to chemical change or to physical disintegration

Pay particular attention to “b”.

The state of my system is “running”. Something changes. If the system doesn’t continue to be state “running”, the system is unstable BY TEXTBOOK DEFINITION.

Both are widely used in that context. Language is like that.

I think the confusion comes from the meaning of stable. In software there are two relevant meanings:

1. Unchanging, or changing the least possible amount.

2. Not crashing / requiring intervention to keep running.

Debian, for example, focuses on #1, with the assumption that #2 will follow. And it generally does, until you have to update and the changes are truly massive and the upgrade is brittle, or you have to run software with newer requirements and your hacks to get it working are brittle.

Arch, for example, instead focuses on the second definition, by attempting to ensure that every change, while frequent, is small, with a handful of notable exceptions.

Honestly, both strategies work well. I’ve had debian systems running for 15 years and Arch systems running for 12+ years (and that limitation is really only due to the system I run Arch on, rather than their update strategy.

It really depends on the user’s needs and maintenance frequency.

Xorg needs several of it’s extensions to function at the same level as Weston+Wayland. At minimum you’d need xorg server, proto, lib, and driver… Maybe a few other things I’m forgetting.

Weston is by file size, about equal to xserver. But really there is more utility in Weston than xserver.

Yeah honestly no idea regarding moderation. But the codebase is maintained by a team.

There is a team, not a sole dev.

I’m not saying everything is roses and rainbows, but this is FUD messaging being spread openly by the mbin dev team.

No argument here. I’m a PF2e player since beta and won’t touch HasWizards products with a 10 foot disintegrate.

The base ruleset (SRD) only. Everything else is OGL, which has proven to be as open as Wizards Hasbro wants to make it.

I’ve had great experiences with exactly one vendor of second hand disks.

https://serverpartdeals.com/

Currently running 8x14TB in a striped & mirrored zpool.

Really all I do is setup fail2ban on my very few external services, and then put all other access behind wireguard.

Logs are clean, I’m happy.

Yeah, you should be scrubbing weekly or monthly, depending on how often you are using the data. Scrub basically touches each file and checks the checksums and fixes any errors it finds proactively. Basically preventative maintenance.
https://manpages.ubuntu.com/manpages/jammy/man8/zpool-scrub.8.html

Set that up in a cron job and check zpool status periodically.

No dedup is good. LZ4 compression is good. RAM to disk ratio is generous.

Check your disk’s sector size and vdev ashift. On modern multi-TB HDDs you generally have a block size of 4k and want ashift=12. This being set improperly can lead to massive write amplification which will hurt throughput.
https://www.high-availability.com/docs/ZFS-Tuning-Guide/

How about snapshots? Do you have a bunch of old ones? I highly recommend setting up a snapshot manager to prune snapshots to just a working set (monthly keep 1-2, weekly keep 4, daily keep 6 etc) https://github.com/jimsalterjrs/sanoid

And to parrot another insightful comment, I also recommend checking the disk health with SMART tests. In ZFS as a drive begins to fail the pool will get much slower as it constantly repairs the errors.

ZFS is a very robust choice for a NAS. Many people, myself included, as well as hundreds of businesses across the globe, have used ZFS at scale for over a decade.

Attack the problem. Check your system logs, htop, zpool status.

When was the last time you ran a zpool scrub? Is there a scrub, or other zfs operation in progress? How many snapshots do you have? How much RAM vs disk space? Are you using ZFS deduplication? Compression?

Maybe Diaspora?

It can. Most people just use the filesystem watcher, but this looks nice. https://github.com/deathbybandaid/tdarr_inform