Tailscale simp here, been using this feature since it launched in beta, can't believe it didn't exist earlier.
This solved every last remaining problem of my CGNAT'd devices having to hop through STUN servers (with the QoS being noticable), now they just route through my own nodes.
I don't think it's possible to separate any open source contribution from the ones that came before it, as we're all standing on the shoulders of giants. Every developer learns from their predecessors and adapts patterns and code from existing projects.
El Al 1862 was another flight [1] that had an engine fall off, taking another engine out with it. The pilots managed to fly around for a few minutes and attempt a landing, but there was too much structural damage.
It doesn't seem aircraft are designed to survive these types of catastrophic failures.
This blog post isn't human speech, it's typical AI slop. (heh, sorry.)
Way too verbose to get the point across, excessive usage of un/ordered bullets, em dashes, "what i reported / what coinbase got wrong", it all reeks of slop.
Once you notice these micro-patterns, you can't unsee them.
Would you like me to create a cheat sheet for you with these tell tale signs so you have it for future reference?
Tailscale now has the awesome feature of peer relays and now there's no more excuses why you can't traverse that NAT and you can forget about all those DERP servers.
Interesting idea, but their PR piece mentions a "failure at a primary data center" which at face value does not sound like a cert issue, and CT logs for *.alaskaair.com show lots of certs issued every single day, but nothing that seems mission critical around October 23 or 24.
Then Tailscale came out and I stopped caring about DDNS or CGNAT ever since.