Skip to main content


Initial temperature check for #Socialcoop members:

What would you think of enabling members to have [user].social.coop as their handles for Bluesky?

This would require no data storage or throughput from us, just a DNS record: https://bsky.social/about/blog/4-28-2023-domain-handle-tutorial

  • Love it, I would use it (16%, 2 votes)
  • Fine, I guess (58%, 7 votes)
  • I have reservations (reply below) (8%, 1 vote)
  • Definitely not (16%, 2 votes)
12 voters. Poll end: 2 months ago

This entry was edited (2 months ago)
in reply to Nathan Schneider

I guess I'm a bit concened about the logistics of managing this for potentially 100s of @SocialCoop users, and knowing when they could be retired. Assuming that could be smoothed over I would be fine, I guess.
This entry was edited (2 months ago)
in reply to Ed Summers

@edsu @flancian @todrobbins @SocialCoop fair concerns. From the Bluesky documentation, it seems like there may be a fairly automated way of managing these, but it's not totally clear.
in reply to Nathan Schneider

My own perspective is that I think this could be a low-hanging way for Social.coop to become cross-platform and to explore what it means to have a cooperative presence on ATProto/Bluesky. It would also advertise our collective existence there.

Personally, not sure I'd use it, as I already use my personal domain (@ntnsndr.in) on Bluesky.

Lo, thar be cookies on this site to keep track of your login. By clicking 'okay', you are CONSENTING to this.