I haven't noticed any bad actor traffic. Perhaps yggdrasil is still too obscure to bother attacking.
The stationary nodes are connected to several public yggdrasil peers that are geographically close by. The routing "just works", though connecting to a peer can take a few seconds, at first.
I share that sentiment. I've thought about combining yggdrasil with garage to create a sort of plug-and-play distributed storage pool shared with a trusted circle.
Though I wonder if the network routing would break down beyond a certain scale, or if it can be resilient against attacks. I don't know enough about the inner workings to be determine the weak points.
There are tipping points, when warming accelerates and becomes irreversible.
There’s some debate in “the science” about how quickly we’ll reach that point. Limiting warming to +2°C was not a scientific position; it was political, based on what people thought was achievable. Before the Paris Agreement, 2° was not considered “safe”.
Anyway, it turns out we’re going to zoom past 2° in the next couple of decades.
Objects in Garage are broken up into 1MB (default) blocks, and compressed with zstandard. So, it would be difficult to reconstruct the files. I don't know if that was a recent change since you looked at it.
Configuration is still through the CLI, though it's fairly simple. If your usecase is similar to the way that the Deuxfleurs organization uses it -- several heterogeneous, geographically distributed nodes that are more or less set-it-and-forget-it -- then it's probably a good fit.
Garage works well for its limited feature set, but it doesn't have very active development. Apparently they're working on a management UI.
Seaweedfs is more mature and has many interfaces (S3, webdav, SFTP, REST, fuse mount). It's most appropriate for storing lots of small files.
I prefer the command line interface and data/synchronization model of Garage, though. It's easier to manage, probably because the developers aren't biting off more than they can chew.
I use a slow cellular connection and noticed some apple service (I could never figure out which one, even after installing an outgoing firewall) was aggressively uploading some large blob every time the mac woke from sleep, which made the whole connection useless for up to half an hour.
At some point, apple must've fixed this "bug", but the experience -- and apple's increasingly obtrusive software -- convinced me to switch to linux.
Designing sewage infrastructure isn’t rocket science, either. If citizens in your town needed to do it, they could figure it out, regardless of their credentials.
Sometimes regulations come about to protect the public. Often, they’re enacted to protect the profits of insurance companies, banks, and other influential industries. Don’t be naive about “the systems at work and their interplay”.
Plumbers make excellent money because regulations require licensed plumbers to do the work, and plumbing unions have a financial interest in limiting the number of plumbers.
But anybody can do plumbing. It’s not rocket science.
In 10 years, resource, energy limits, and wealth inequality will become increasingly clear to everyone, while the climate continues to warm at an accelerated rate. Social instability might preclude the existence of software engineering, aside from a tiny minority supporting the lavish lifestyles of the ultra-wealthy.
The system was already authoritarian, if less blatant to most people. Any meaningful resistance to the power structure gets crushed, and everyone tacitly accepts that arrangement.
Yes, it would be wonderful to be able to tune out the wretched poor people. Maybe a future headset will include a forcefield to actively repel potential muggers or oncoming vehicles.
Back then, 10 years of technological advancement made a huge difference. Today, you can get by just fine with a 2016-era laptop.