-
Notifications
You must be signed in to change notification settings - Fork 71
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
Create an official Jupyter account on Bluesky #168
Comments
Ping @Ruv7 and @blink1073 from the EC who are working on all things social media. |
I requested a Bluesky account using the Jupyter gmail account. Note: "Bluesky will launch soon. Join the waitlist to try the beta before it's publicly available." |
@blink1073 I have an invite code if needed |
Hi @ibdafna, yes, please, we still have not gotten a reply. |
Sent over LinkedIn message! |
Thanks @ibdafna, done! |
@blink1073 FYI it's possible to "validate" the account's identity by adding a TXT record to jupyter.org. Once validated, the handle will be @jupyter.org |
Thanks for the heads up, I don't have direct access so I'll bring it up to the EC. Note to self, instructions are here: https://blueskyweb.xyz/blog/4-28-2023-domain-handle-tutorial |
🧹 cleaning up here and closing this issue. Looks like this was done. https://bsky.app/profile/projectjupyter.bsky.social Follow up to "validate" the account must have petered out, so if someone has renewed interest in that, please open a new issue. Happy hacking! |
Similar to #146.
Bluesky is getting a lot of traction recently, so it can make sense to have a presence there: https://bsky.app/
It's possible to use a domain name as the handle, so the sign up will hopefully be simpler than Mastodon since there is no instance to choose from. So the Jupyter account could simply use the
@jupyter.org
handle.For reference the Bluesky official account is
@bsky.app
:There is no rush to grab a username since it's possible to use a custom domain name. Just opening this issue for awareness.
The text was updated successfully, but these errors were encountered: