3 ms·
I'm generally interested in Bluesky (and I'm already using it), but I think DNS was probably the wrong choice for them here: it's not authenticated (and can't e
by woodruffw 4y ago
I'm generally interested in Bluesky (and I'm already using it), but I think DNS was probably the wrong choice for them here: it's not authenticated (and can't easily be authenticated in reasonable ways), and has relatively weak guarantees around propagation, invalidation, etc.
The "well-known" URI scheme[1] was intended to overcome many of these deficiencies, and has worked admirably in other contexts (for example, Let's Encrypt's HTTP-01 challenge scheme[2]). I believe Bluesky also supports a "well-known" flow for domain verification, but it seems like it still isn't the default.
[1]: https://en.wikipedia.org/wiki/Well-known_URI https://en.wikipedia.org/wiki/Well-known_URI
[2]: https://letsencrypt.org/docs/challenge-types/ https://letsencrypt.org/docs/challenge-types/
- rnk 4y agoHow does one get a blue sky account? I requested one. All I see is people offering to sell you one. That seems terrible.
- zadler 4y agoSorry, Jacks launch plan for blue sky is cool kids only for now. (I also do not have an account, but as time goes on my interest wanes).
- Hamuko 4y agoExisting users get an invite every two weeks. Some prominent accounts get a bunch of invites at random. And at times they invite a bunch of people from the waitlist.
- squarefoot 4y agoI'm not interested in Bluesky atm, but having self-seekers among the first batch of users doesn't constitute a nice PR for the platform.
- reaperducer 4y agoIt worked for Gmail.
- pessimizer 4y agoNot really. Invitation-only was good marketing, but accounts were absurdly easy to get from the beginning.
- jeroenhd 4y agoWith competent DNS providers, DNS can be authenticated very easily through DNSSEC. Whether other people bother to validate that authentication is a whole other problem, but enabling it really doesn't have to be all that hard.