Live data from Hacker News

Hypergrowth isn’t always easy

tailscale.com

21–30 of 53 posts

Re: Hypergrowth isn’t always easy

#21
post #20

Not my deviantart ass thinking hypergrowth meant something else

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)

That sounds like quite the story.

Re: Hypergrowth isn’t always easy

#22
post #20

Earlier quoted context omitted.

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)

That sounds like quite the story.

pack considerably more spinning disks bought off the shelf at radioshack than you ever reasonably should in a box in a colo, turns out they generate a lot of heat, I don't recall the year I'd guess around 2004/5-ish - was a big problem, site was down for quite some time. Same year someone found out who one of our mods was and showed up to their house with a gun. Ask me about hypergrowth, I'm not sure if the DeviantART stories or the DigitalOcean stories are more wild. heh. :)

Re: Hypergrowth isn’t always easy

#23
post #13

Earlier quoted context omitted.

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.

Notably, it's a VPN for connecting your own devices together, so unless you're deploying a server elsewhere for access to porn it's probably not for that.

you can pay for the mullvad add-on to use their exit nodes

Re: Hypergrowth isn’t always easy

#26
post #2

Why is the cover image for the post a cartoon 69 position?

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.

It could also be that Tailscale users have many kids, who then also use Tailscale. Although if the header is meant to represent that, it's showing the wrong position.

Re: Hypergrowth isn’t always easy

#27
Kind of annoying to read. No, the P in CAP theorem isn’t when the client can’t connect to your unavailable service. That would be the A. Maybe it was down because of a P on your side, but don’t start blaming your downtime on network partitions between the client and your service.

Edit: your service going down and not being able to take requests from clients does not a network partition make

Post reply on HN