Comment on Tailscale addressing concerns over potential enshittification of the platform
TheHobbyist@lemmy.zip 1 month ago- Tailscale has an employee who is contributing to headscale. I think this is helpful and they could decide to stop this collaboration the moment they feel it is counter productive.
- they may decide to start adding undocumented/proprietary/“secure” elements which prevent headscale from working.
There is no guarantee headscale can keep working the way it does or that it is allowed to keep existing.
thelittleblackbird@lemmy.world 1 month ago
Honestly, this seems more than your assumptions and fears than anything else.
Clients are open source and foss, the moment something strange is in, Headscale could adapt.
If they finally goes to full close source, then the community will fork (emby - jellyfinn drama).
Your arguments don’t hold together, for the good of the community
TheHobbyist@lemmy.zip 1 month ago
I feel you are a bit out of touch when the topic is specifically enshittification and that it is based on the history of companies turning against their users, showing little good faith. It is also not something which is sparing open source projects (remember bitwarden’s attempt?). So sure, I’m not going to deny that I’m making assumptions and that I am concerned it may one day happen. But it is grounded in reality, not some tinfoil hat stuff.
thelittleblackbird@lemmy.world 1 month ago
Precisely bitwarden movement proves my point. Bitwarden tried to degrade the features/compatibility of the solution and they couldn’t because of the vaultwarden implementation.
Can they always add new features after a pay wall? Sure! But once foss Sw is here it is simple impossible to remove functionality, at most, to get some coins for services not fully selfhosted.
If tailscale tries to do something similar is goint to be a shoot into their own leg, because all the sw already disclosed makes it impossible. Could they make the relay a paid one? Sure but then they will face the competence of a vps with the Headscale implementation.
This and only this is because in your home lab only foss Sw should be allowed, even if you need to pay some money from time to time
teppa@piefed.ca 1 month ago
I switched my company over to Bitwarden because it was open source, any the code could be vetted. I'd definitely be dropping it if they ever started making things proprietary.