-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bluesky: unable to authenticate with domain handle #1667
Comments
Hmm, sorry for the trouble! Looks like you're @tedt.org on Bluesky. I'll look into it. |
No troubles. I might have been "Holding it wrong" But once I got the DID, as I saw it was looking that up in the Error Messages, everything worked. I also didn't quite know what format you wanted the handle in. Was it @tedt.org or [email protected] or @[email protected] or or or or... Perhaps this defect is a UI/UX 'error' |
Bluesky handles are just domains, not email addresses or fediverse-style webfinger addresses, so your Bluesky handle is tedt.org, or stylized, @tedt.org. Bridgy has a couple bugs to fix here. First, it needs to validate handles better, including stripping any leading We'll fix both of those. Thanks again for reporting! |
Yep, looks like I'm in this boat too. Seeing your comment and changing TechLifeWeb.bsky.social to lower case enabled me to authenticate. |
Fixed! Thanks again for reporting! |
Sorry for the spartan bug report. I am on mobile.
I use @[email protected] as my handle at BlueSky. I am unable to authenticate from this page.
I was able to get this working by using my DID, which is a TXT record off my tedt.org that BlueSky uses to validate I own the domain name. Brid.gy then gets my name right and works ok.
I suspect you don't have a case in the code to do the DNS lookup.
https://brid.gy/bluesky/start
The text was updated successfully, but these errors were encountered: