realreality
Joined 8 years ago
Joined 8 years ago
Back then, 10 years of technological advancement made a huge difference. Today, you can get by just fine with a 2016-era laptop.
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.
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.
in pf syntax:
table <yggdrasil> persist file "/etc/yggdrasil-allowed"
pass in quick on tun0 inet6 proto tcp from <yggdrasil> to port $servicesThere’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.
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.
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.
At some point, apple must've fixed this "bug", but the experience -- and apple's increasingly obtrusive software -- convinced me to switch to linux.
The question was why plumbers are expensive. I assert that it’s not because plumbing is especially difficult.
"Free" fuel for you just pushes the externalities elsewhere.