> Sign up with your identity provider...
This frightened me enough not to use Tailscale, I don't want Google / Microsoft sharing any more of my data. Is this still the case?
> Sign up with your identity provider...
This frightened me enough not to use Tailscale, I don't want Google / Microsoft sharing any more of my data. Is this still the case?
Btw, there is no IdP support in Headscale. You need to have access to the machine where you are running it, and use the CLI to register your machines (or use a authkey, ofc).
Why would it be? It's a commercial service.
>Such that I can set this up myself for my own purposes 1:1?
I'm guessing both peers ping a central server in order to discover each other, which is why it's integrated with tailscale at all. If you're in the tiny segment of the population who is already paying for a server with a public IP, and have the technical ability to deploy services to it, I feel like it would be marginally less effort to just sftp the file to that server rather than try to clone the feature set of taildrop.
Tailscale could theoretically publish a docker container that contains the guts of this service, but it'd be rather a lot of work, for no money.
>>Sign up with your identity provider...
I have not seen a lot of evidence that regular users care about identity provider privacy, seeing as how Facebook had 2.8 billion monthly active users last quarter. That customer segment (half of the world population) might be more interested in signing up for the free tier of tailscale and getting magic file sharing than they would be in administering their own linux server.
Open source is a good way to get community buy in, because it improves transparency and reduces lock-in. There are lots of open source commercial services, including the Tailscale client service.
https://github.com/zerotier/ZeroTierOne/blob/master/LICENSE....
I'm personally really tired of fake open source projects like this.
If I use an OAuth integration I'm involving a third party
Some people use a third party email provider, but chances are they aren't supported (even if your mail provider offers oauth integration) -- the only support is with Google and Microsoft
Now that aside, I support the idea of tailscale not creating its own identify provider. BYOI is far better than yet another supplier to leak information and yet another password to manage.
If I were interested in integration with my company's SSO, I'm sure they'd be able to support our OAuth endpoint.
For personal use, chances are you have an identity with one of the providers, and the information leaking to that provider (that you use tailscale) is minimal and seems like a good solution.