I wrote up some thoughts about how Bluesky can/should support OAuth, both for applications to access users' accounts, as well as allowing users to log in to their bsky.social account using their own website!
Bluesky, a new social media platform and AT Protocol, is unsurprisingly running up against the same challenges and limitations that Flickr, Twitter and many other social media platforms faced in the 2000s: passwords!
I recently got access to the BlueSky beta, and decided to poke around to see what it's all about. I will save the details of what it is and how I feel about it for a different post. However, one of the first things you do when you sign up is choose a username that exists under the bsky.app domain. I have zero interest in another name rush where everyone tries to claim the shortest username possible, so I went with aaronpk.bsky.app rather than trying to get a or apk.
I'm glad to see that BlueSky supports custom domains! I have zero interest in sitting on a username in the bluesky namespace. Setting it up was roughly the same as pointing your own domain to a hosting provider, and a lot easier than Mastodon/ActivityPub!