This project is not associated with Tailscale Inc.
However, one of the active maintainers for Headscale is employed by Tailscale and he is allowed to spend work hours contributing to the project. Contributions from this maintainer are reviewed by other maintainers.
Limited by material. They store electric charge by using thin layers of insulating material and pooling negative charge on one side and positive on the other. You can puncture the material and release energy as a typical conductor, it's not stored chemically.
Push based, sure. Allowing SMS, I still hold, undermines all of this.
They "secure" this behind password which you entered to trigger the SMS push in the first place.
Offering an "out" to a more secure flow means your secure flow may as well not exist.
Additionally, phishing a pushed OTP is not really much harder since you can trigger the push and then just have the user finish off the flow for you, provided they don't read the IP or whatever you display them (they won't, they think they're signing in), effectively the same as a TOTP.
Anecdotally, I don't know anyone who picks up random tools, unrelated to AI, because AI is advertised.
Usually when I see people see a pop-off for Try our AI assistant I hear "Fuck off" or "leave me alone" while they close it. It's like everything has a modern Clippy.
Personally I do see it as a VC signal, as if they gave up on making a good tool and started working on slopifying it.
60% is lower than I imagined, tbh. Most people aren't doing agentic workflows and AI is likely not a selling point.
I use a basic OTP password instead of Microsoft's ironically less secure (see SMS as 2FA) with my work MS account. Perhaps your org disabled it but it is definitely something a Microsoft account can do.
And yet, I incessantly get spoofed numbers calling me from the same "central office code". Also resulting in people with the same code "returning my calls" and then getting angry that I say I didn't call them.
Preventing number spoofing would help significantly with spam calling. At least the ones from local numbers.
I see everyone coming up with an arbitrary date of when Google lost their moral compass that aligns with their own moral compass. In that vein, I feel like when Brin and Page released a paper stating how PageRank could never be beneficial to a consumer with ads and then launched an ad company powered by page rank is when Google became evil.
If they wanted the release build to be an error I wouldn't care. Having the current solution be "have the editor automatically change code to include or remove the underscore" is so wrong to me. Just invented a problem that needs tooling to modify source code to fix.
This project is not associated with Tailscale Inc.
However, one of the active maintainers for Headscale is employed by Tailscale and he is allowed to spend work hours contributing to the project. Contributions from this maintainer are reviewed by other maintainers.