| ▲ | 1dom 8 hours ago |
| No issues using headscale and selfhosted derp servers. Tailscale is great technology and protocol and facilitates decentralisation. Hypergrowth is a synonym for unsustainable growth. The headline here is business breaks tech, again. |
|
| ▲ | crazygringo 5 hours ago | parent | next [-] |
| > 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. |
|
| ▲ | cael450 5 hours ago | parent | prev | next [-] |
| > 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. |
| |
| ▲ | 1dom 28 minutes ago | parent [-] | | I'm not saying companies can't do fine in many respects after experiencing hypergrowth, but like you said, that's after hypergrowth - the hypergrowth isn't sustainable. And I disagree: outages are a fairly literal example of tech breaking. A few outages aren't catastrophic though, and I agree are fairly common. I know it's cliche, but "move fast and break things" might get growth, but it also gets broken things along the way. Hypergrowth is growth and churn at the expense of sustainability and stability. It can definitely be fun though! |
|
|
| ▲ | elashri 8 hours ago | parent | prev | next [-] |
| How do you selfhost your own derp servers? I am curious if it is an easy like headscale itself |
| |
| ▲ | bayindirh 8 hours ago | parent | next [-] | | The last time I looked (i.e. A couple of days ago), the documents sounded like Headscale now supports DERP [0]. [0]: https://headscale.net/stable/setup/requirements/#ports-in-us... | |
| ▲ | clayhacks 5 hours ago | parent | prev | next [-] | | It’s not super well fleshed out by Tailscale but they have a guide. https://tailscale.com/kb/1118/custom-derp-servers My last company ran our own DERP servers to have more consistent endpoints we controlled | |
| ▲ | 1dom 7 hours ago | parent | prev [-] | | I use the built in derp server. I have run a standalone derp server hackily deployed for a month, it worked fine but didn't provide much benefit over the built in one. It was basically just a go package. If you're familiar with running Go code, it's straight forward to run, it's very, very light/unproductionised. I have a todo task to integrate derp into my headscale deployment properly ("finish ansible role"), but when I picked it up last month, I noticed tailscale had release relay nodes, and they seem like they'd be better suited than dedicated derp nodes, but headscale hasn't implemented support for them yet. tldr: not to hard to host DERP, just needs publicly facing endpoint (incl. letsencrypt) but the built in one is fine. But relay nodes look like they'll be a better option for most and I'd guess will be implemented in headscale sometime this year. |
|
|
| ▲ | AndrewKemendo 7 hours ago | parent | prev [-] |
| Tech is simply the reproductive organs for capitalism So, things are working as designed for the few people that benefit |
