Kata1yst

Yes…? All are except Microsoft, which is why most companies I work with aren’t looking that way.

I know several large companies looking to Microsoft, Xen, and Proxmox. Though the smart ones are more interested in the open source solutions to avoid future rug-pulls.

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%

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.

You say “no one knows coffee better than he does”, while blatantly disagreeing with his entirely empirical points in his video on decaf, that it can be made by several processes, all of them are fairly good, and the result can be masterful?

I live in a hockey capitol. That makes me nothing like an expert. Same for you.

Okay, so you make brilliant decaf. That means your point in this thread is moot?

Funny thing on that “subjectivity” is when you disagree with other people in this thread, you’ve plainly said they’re just entirely wrong.

When someone disagrees with you, you hide behind “subjectivity”.

I encourage you to introspect.

You sincerely think you have a better grasp on coffee than James Hoffmann?

Much more likely you haven’t tried good decaf from a good roaster, tried a blind tasting, or your preparation is seriously flawed.

Yeah, well for many of us it’s decaf or no coffee due to health issues. You acting like it’s a foolish, childish thing is just tribalism/elitism.

And for what it’s worth, I’d put my decaf vs your coffee in a heartbeat. A good roaster with quality beans is great coffee, decaf or no. Just like Hoffman said.

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?

Love this product. Run my water cooling profiles on it.

What a weirdly unjustified, baseless attack on someone contributing a useful conversation. And when presented with evidence that you’re not just being a huge jerk, that you’re entirely wrong, you get defensive and continue to denegrate OP?

Shame on you. If you have had half the illustrious career you claim to have, you should have worked in enough places and with enough people to know when to eat crow.

Infighting and personal attacks like this from positions of false authority like yours are exactly why people have such low opinions of programmers as members of society.

Development is happening in the dev’s branches. Branches are generally kept local until submitted for a PR. You can easily see this in the origin branches and open PRs.

Honestly I’m not sure if you’re trolling, don’t understand git development, or if you really think that a project needs to iterate main multiple times per month to be your definition of “healthy open source”, but I’m tired of shooting down such lazy attacks and won’t be responding further.

Have a nice day.

What obscure location? Codeberg?

All the activity is open on Codeberg. You can see every member of that team actively merging and reviewing requests.

Why do you assume that? Why is your way of open source the right way?

All open source projects are run by a small team of people reviewing and accepting, rejecting, and prioritizing work. What part of this project’s methodology bothers you?

He did though. And honestly the website has come very far in a short period of time, I really don’t understand the concerns and whining in this thread…

From codeberg-

Core Team

• ernest
• szsz
• cooperaj
• rideranton
• AnonymousLlama

https://codeberg.org/org/Kbin/teams

Design Team

• cody