News for hackers. Stuff that matters.
Re:Improving Tailscale via Apple’s open source by jzelinskie on Thursday April 13, 2023 @02:20PM (#35559807)
I don't think that their choice to keep their server software proprietary is baffling. They're going to architect it so that it's easiest/best for their team to run which is not the same what's easiest/best for EVERYONE to run as is the typical goal of open source software.
Re:Improving Tailscale via Apple’s open source by ceejayoz on Thursday April 13, 2023 @02:25PM (#35559875)
There's two concerns: "can I run it myself", and "what does this security-critical third-party code do?"

Open sourcing helps with the latter, even if the code's not very well optimized for general purpose use for the former case.

Re:Improving Tailscale via Apple’s open source by judge2020 on Thursday April 13, 2023 @02:37PM (#35560047)
The concern is that people will assume the OSS is for both scenarios, so even if you close issues and have a PR bot rejecting PRs, you'll still get both support tickets and (good|bad) PR from people trying to run the mainline system themselves.

Supporting development on a made-for-self-hosting OSS project is the most user friendly option and allows them to avoid needing to handle the woes of public code.

Re:Improving Tailscale via Apple’s open source by daveidol on Thursday April 13, 2023 @02:49PM (#35560237)
What about open sourcing the code with a README stating it is only for transparency, comes with no support, etc. and disabling GitHub issues?
Re:Improving Tailscale via Apple’s open source by Operyl on Thursday April 13, 2023 @02:57PM (#35560365)
Users will still just spam the ticketing system. (Their support email).