-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
add Bluesky support (#2302) #2303
base: master
Are you sure you want to change the base?
Conversation
NitroType throws status_code 302 which is QueryStatus.AVAILABLE as defined in here: https://github.com/sherlock-project/sherlock/blob/master/sherlock_project/sherlock.py#L458-L459
Lichess throws 404 if a username is available
Kick's changed their error message from "Not Found" to "Oops, something went wrong"
Houzz throws 404 if a username is available
"errorMsg": "<title>@{} — Bluesky</title>", | ||
"errorType": "message", | ||
"url": "https://bsky.app/profile/{}.bsky.social", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure this is going to work super well. If the user doesn't have a display name, I think the title of the page will match this even if the user exists. It might be better to use the status_code
errorType and then specify the actual API call that looks up the user. That should respond with a 400 if the user doesn't exist. The API call would be https://public.api.bsky.app/xrpc/com.atproto.identity.resolveHandle?handle={}.bsky.social
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @ibnaleem before I run through things do you have any thoughts here?
Added Bluesky (bsky.app) to data.json.