With a climate change kicker thrown in

If you are willing, I would love to see a blog post, video, or repo of exactly how you conducted this audit. Great read, and would like to learn more of your specific process (beyond the readmes and man pages).

Eh, that post title is quite sensationalistic.

No it’s not? The issue is on Awesome Self-hosted, where they had Mattermost listed in FOSS instead of non-free.

Also, if you read the ticket, you can see why people feel the way they do. They’re skirting AGPL rules with the compiled requirement.

It’s because it’s a summit in a fjord, so more like a sharply cut hill than a mountain.

It’s a summit in a fjord, not a mountain, thus the small size. Probably didn’t take long to get up. I would love this.

Hello Chuck.

A lot of archery experts here for such little content in the archery community.

Great answers, thank you.

Question: Are failures due to issues on a specific platter? Meaning, could a ZRAID theoretically use specific platters as a way to replicate data and not require 140TB of resilvering on a failure?

While many in fedi will say the above, a simple federated search model could increase adoption. I.E. don’t bother going crazy with it, just add a discovery platform where you can search “your own” or “the network”.

Very cool. I run a piKVM attached to an 8 port KVM and 8 plugs controlled by relays, giving me full control over everything. I should add this to the mix.

Nice. Couple of things:

• The link in your post is broken 😉
• Consider doing with Jellyfin anything you’ve done with Plex. Plex is on it’s way out, especially with Fediverse users.