←back to thread

Tailscale raises $100M

(tailscale.com)
854 points gmemstr | 5 comments | | HN request time: 0.651s | source
Show context
pilif ◴[] No.31260250[source]
With such a huge investment comes the obligation to eventually pay it back. Is this another one of my favourite tools going the way of Dropbox, 1Password and all other companies that were formed around what should be a platform feature, which took on way too large investment sums and were eventually forced to become the everything, losing sight of their core values?

I sincerely hope not, but there's so much bad precedent.

replies(6): >>31260318 #>>31260351 #>>31260537 #>>31260737 #>>31261295 #>>31264059 #
oicU00 ◴[] No.31260737[source]
It’s a basic web UX over a built in Linux kernel feature

There are Docker containerized apps that manage Wireguard too

Maybe contribute to one and fret less about behavior of VC funded business and wondering if they’re actually respecting your privacy to accomplish finance goals

replies(2): >>31261433 #>>31265555 #
shepherdjerred ◴[] No.31261433[source]
It handles a lot more than that, right? It does all of the key distribution and rotation which is a pain.
replies(1): >>31261583 #
oicU00 ◴[] No.31261583[source]
If they can do it it’s not impossible (they’re just people after all).

With an open source implementation out there, anyone can do it merely pulling a Docker container, and without paying Tailscale.

Regardless I manage a dozen users with no issue using Embarks container; once they’re setup I touch nothing.

Paying people is not working with people; it’s working with a specific group. Open source is working with people.

replies(3): >>31262932 #>>31264792 #>>31264813 #
1. samhw ◴[] No.31264813[source]
If the open source implementation is equally good, I'm sure people will use that instead of Tailscale. That Tailscale exists makes me suspect that the open source implementation - as is usually the case with these "just use curlftpfs!" comments – is not equally good.

The reality is that making software, like any other human endeavour, takes time and energy. Paying one another money is a rather well-established mechanism of rewarding and incentivising that time and energy (since not everyone wants to work free of charge to make and maintain software for you, out of the goodness of their hearts, no matter how much you insist that you're owed their unpaid labour).

There are small and local means of getting free food, or free woodworking, etc, but the general reality is that a high-quality high-dependency maintained product, over the long term, is more feasible when it's paid.

replies(2): >>31265858 #>>31278017 #
2. shepherdjerred ◴[] No.31265858[source]
It's the same argument as the famous Dropbox comment[0]. I'm generally going to prefer a polished service over a technical solution.

[0]: https://news.ycombinator.com/item?id=9224

replies(1): >>31267992 #
3. samhw ◴[] No.31267992[source]
Haha, yup, that's what I was quoting in my comment ("just use curlftpfs!").
replies(1): >>31279320 #
4. oicU00 ◴[] No.31278017[source]
If agency to make a thing must be purchased the long term viability of the thing is suspect. The work becomes about payments not the thing.

If it’s a real human problem, humans will solve it. If it’s instigated due to someone with coins in their pocket to mesmerize lizard brains, it’s a synthetic solution that will vanish with the synthetic driver of the work; payments.

Just because paying for things is common throughout history does not mean it’s necessary or the best choice long term; see Netflix propping up payment flows churning out crap. It means meat based tape recorders simply LARP the past.

5. oicU00 ◴[] No.31279320{3}[source]
Apples and oranges

A fully functional web app in a Docker image is what wg-ui is.

Web companies could probably just provide API keys for customers at this point and abandon UX teams.