I actually don't have firewalls set up on my devices that run Yggdrasil yet (please don't crack me). I haven't noticed any brute-force attacks on my SSH servers yet. Though I really should set up firewalls.
As for routing, I run my own node on a VPS, so all my edge devices are peered with that machine so routing is fine. Though when my machines are on the same network they automatically peer with each other directly.
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 considered using Tailscale, but at the end of the day Yggdrasil is more inspiring to me. I like the idea of a network with no central authority delegating addresses. I hope that it takes off beyond just an overlay network. I'd be curious to try running it directly over some physical link without IP. Imagine if the world ran on something like Yggdrasil: anyone could plug in and get a publicly routable address. I think it would be great for decentralization and the open internet.
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.
This is clearly the follow up to the dril tweet - you do not, in fact, have to hand it to them for figuring out how to monetize the enemy combatant guidelines
I regularly can't remember who that one person is in that one movie either. I think part of being bad with names is that you don't actually care. That may offend some people, but hopefully less so if they consider that I think my name is just as unimportant as the next guy's.
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.
I guess this change was inevitable. But I like the possibility to reconstruct a broken distributed file storage system. GlusterFS also allowed this.
My use case is relatively common : I want small S3 compatible object stores that can be deployed in Kubernetes without manual intervention. The CLI part was a bit in the way last time, this could have been automated but it wasn't straightforward.
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.
My Macbook used to grind CPU for 10-20 minutes after every power on. That happened with literally fresh install and it does it every time. I don't know why does it do that. May be some indexing? This lack of transparency was one of the reasons for me switching to Linux too. I don't want my OS to do anything at all in background, that I didn't explicitly configured to. I want to be in full control of my software. Linux is far from perfect, but much better.
Lack of transparency is almost a feature for these systems, and definitely something that serves the vendor, not the user. My daily driver is a Linux for the same reason - there is just so much less bullshit going on, and if I want to find something out, I can.
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.
You can hire a non-union plumber. There isn’t usually much of a price difference. Where I live, you can easily find a non-licenced plumber (called “moonlighting”, usually done by apprentices of licenced plumbers). A lot of people prefer not to since you’re on your own if something goes wrong.
Plumbing requires skill, particularly for difficult jobs, and also requires advanced equipment to do such a job in a reasonable amount of time, such as special cameras to inspect a septic tank or drain line without having to actually cut into it.
> regulations require licensed plumbers to do the work
Regulations come about because of repeated failures that end up harming the public. Regulations aren’t a dirty word, and aren’t obstacles to be “disrupted” in most cases.
> plumbing unions have a financial interest in limiting the number of plumbers
Golly gee, it’s almost as if - because we live in a society where everyone must work in order to survive - that skilled professionals have a vested interest in ensuring only qualified candidates may join their ranks, to make it harder to depress wages below subsistence levels (the default behavior of unregulated capital).
> But anybody can do plumbing. It’s not rocket science.
Oh wow, I had no idea I was qualified to design sewage infrastructure for my township just because I plumbed my Amazon bidet into the cold water line! Sure glad there’s no regulations stopping me from becoming a licensed plumber since apparently that’s all it takes to succeed!
Sarcasm aside, your argument holds about as much substance as artificial sweetener: it sounds informed and wise, but anyone with substantial experience in reality and collaborating with other people knows that all you’re spewing is ignorance of the larger systems at work and their interplay.
You’re not wrong (examples include the US FCC, ZA’s Telekom, ye olde Standard Oil, vertical integrations…the list goes on, and even includes modern cloud services and AI tools, since the regulations they champion are often intended to block competitors with onerous compliance requirements), but in the context of the person I was replying to, they used “regulation” very much in the same context Uber/AirBnB and the SV Libertarian ilk decry “regulations”.
Regulations aren’t a binary (exclusively good or exclusively bad), yet so many of the HN cohort have drank the “exclusively bad and everyone can be trusted to make good decisions forever” koolaid that seeks to dismantle regulations wholesale.
Smartest thing you’ve said all day. Thanks for reminding me that trying to convince someone of something when they cannot be bothered to do research beyond first order impacts is a waste of my time.
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”.
Back then, 10 years of technological advancement made a huge difference. Today, you can get by just fine with a 2016-era laptop.
reply