A little reward for anyone who was affected by the outage?

TailScale is a VPN, and the article highlights a recent increase in user base. This is likely due to VPNs being required to access pornographic materials for residents of many US states.

Took me a moment, but now I can't not see it.

It is not a cartoon, it is an interpretation of the position in Bauhaus style.

I mean... shows where your head is at? Lol.

Why isn't every cover image a cartoon 69 position?

420 is very controversial so what choice do you really have this days

Cannot unsee :)

How do you selfhost your own derp servers? I am curious if it is an easy like headscale itself

Tech is simply the reproductive organs for capitalism

So, things are working as designed for the few people that benefit

> Hypergrowth is a synonym for unsustainable growth. The headline here is business breaks tech, again.

That just isn't true. Plenty of services do just fine after experiencing hypergrowth, and a few outages are not an example of tech breaking. That's a fairly common occurrence.

> Hypergrowth is a synonym for unsustainable growth.

No it's not. It's often a recognition that just one or two, maybe three companies will end up dominating a particular market simply due to economies of scale and network effects... and so the choice is between hypergrowth to try to attain/keep the #1 or #2 position, or else go out of business and lose all the time, money, and effort you already put into it.

Nothing whatsoever makes it unsustainable. You might be offering cheaper prices during hypergrowth -- those are unsustainable -- but then you raise prices back to sustainable levels afterwards. And consumers got to benefit from the subsidized prices, yay! The business is entirely sustainable, however.

Uber is the poster child of hypergrowth. They became profitable in 2023. And their stock price has ~doubled since. Totally sustainable.

Would you mind explaining this comment? (I worked on deviantart for many years when it started so I'm curious, tho the servers did literally melt at one point)

> just be sustainable, that's okay too

Not if most of your company was built on investor money.

They want their pay day!

Hypergrowth can be natural. Random example but what if you designed a microblogging service and all of the sudden the biggest platform gets bought by a facist and users come flocking? You could start turning users away or you could work as fast as you can to accommodate them and make small mistakes along the way. Both of these are reasonable decisions and neither one is really wrong.

A network partition between the client and server is a network partition between two nodes in a distributed system, which is the P.

This is a common misunderstanding about the poorly named ‘Availability’ in CAP. Availability under CAP means that if your request reaches a non-failing node, that node still responds despite being unable to communicate with other nodes. This is distinct from SLA-style availability, which describes the uptime of the overall system. I’m pretty sure the partition tolerance they’re referring to is the fact that the tailnet remains intact and continues to operate even when nodes can’t reach the coordination service.

Isn't Availablility the ability to connect to something? If I'm calling from region A to region A servers, and the region A servers' networks go down. Well, my client is clever and can failover to region B servers. Except, all my state and context was on region A servers, and maybe that state wasn't replicated over to region B - that replication might only happen on a nightly basis.

When I reconnect, my dating profile is missing all the pictures I uploaded of me in my new convertible with me lowering my sunglasses and winking at the camera.

The LovinHuggin.com server architecture is Available, but not Partition Tolerant. And after I upload different pictures of me in tuxedos and talking like a boss on the cellphone to region B, I've potentially created a weird "split brain" situation. Region A and region B servers have different views of me. Both views are super hot, but the client might get confused if my session returns to region A when their network heals, and the nightly region replication might be messy with reconciling the split brain. Eventual consistency is a helpful (or fraught) feature to have in the database when things like split brain happen.

The reason for that is that all nodes talk p2p to each other. There is no central communication server like with many other vpn solutions. So even if Tailscale would go down for days you won't have any downtime between your nodes.

The server that acts as the control plane needs to have full access to the outside internet. You can’t do NAT hole-punching through STUN if you are yourself behind a NAT.

(There is Headscale though)