But then you're relying on Tailscale's relays and infrastructure then. All you're doing is shifting the liability and dependency from one company to another... which kinda defeats the point of the whole self-hosting thing doesn't it?
Unless by "Tailscale" you actually meant your own self-hosted Headscale server + your own DERP server + config in a way that there's zero reliance on Tailscale's infrastructure...
You are correct, this article is part of my self-hosted Tailscale series using Headscale, which is why I'm receiving the full benefits of moving Syncthing to it. Otherwise Tailscale would keep the same metadata that Syncthing discovery and relay servers were. I talk about that in Part 1 of the series, it's a main motivator for self-hosting Headscale.
I posted the link to the Spanish article by mistake, please notice that there is an English version available:
https://blog.fidelramos.net/software/tailscale-3-syncthing
> No reliance on Syncthing's relay network.
But then you're relying on Tailscale's relays and infrastructure then. All you're doing is shifting the liability and dependency from one company to another... which kinda defeats the point of the whole self-hosting thing doesn't it?
Unless by "Tailscale" you actually meant your own self-hosted Headscale server + your own DERP server + config in a way that there's zero reliance on Tailscale's infrastructure...
You are correct, this article is part of my self-hosted Tailscale series using Headscale, which is why I'm receiving the full benefits of moving Syncthing to it. Otherwise Tailscale would keep the same metadata that Syncthing discovery and relay servers were. I talk about that in Part 1 of the series, it's a main motivator for self-hosting Headscale.