Claim your Discord Username on BlueSky!

Discord has recently released a BlueSky account connection into their Canary Desktop client, this allows you to show off your BlueSky account in your profile!

In celebration of this, we've developed a custom domain that allows you to claim your Discord name as a BlueSky handle, using the Discord OAuth2 system to prove ownership of your Discord account on BlueSky!

Introducing: Dis.Blue!

To claim your Dis.Blue handle, all you need to do is type the handle of your BlueSky account in the box below, and hit claim! This will take you to a Discord OAuth2 screen that will ask to see your basic information, and your connections. We need your basic information to assign your username, and your connections to attempt to verify your BlueSky account connection. You don't need a BlueSky account connection in Discord to use this, but it's highly recommended.

Dis.Blue is not affiliated with Discord or BlueSky, it's third party software developed by PNLY.

If there's any issues with claiming your handle, you'll see an error message or warning above. You can find debugging information further down this article.

Now your handle is claimed, you can go to your account settings in BlueSky and update your handle. First, select "I have my own domain" as below.

Next, you'll want to input your handle. This will be your Discord username followed by .dis.blue. For example, for the username Panley, you would input panley.discord.blue as below.

Next, you must click the "No DNS Panel" button as our domain does not use DNS records, but rather a text file to verify your handle.

Finally, hit "Verify Text File" and you should be good to go! you can now update your handle and claim your Discord-connected username on BlueSky!

Debugging

There's a few errors you may run into while using this service. Here's a rundown of everything you could encounter and how to fix it:

• security could not be confirmed
  • This means the State parameter was missing from your Discord OAuth2 flow. Make sure you ONLY start the flow from the "Claim Handle" button.
  • You must authorize the Discord application within 10 minutes of hitting the "Claim Handle" button. If you take longer, just try again.
• discord auth code missing
  • Discord has responded to your authorization without an auth code. This means the authorization URL was malformed or missing data. Make sure you ONLY start the flow from the "Claim Handle" button.
• handle could not be found
  • We couldn't find the handle you entered on BlueSky's servers. We only search for your handle if you don't have it connected to Discord already, so connect it if you can.
  • If you can't use the Discord BlueSky connection, make sure your handle was typed correctly and try again.
• we could not verify BlueSky account ownership
  • This isn't an error, just a warning. If you see this, it means you don't have a Discord BlueSky connection that matches the handle you provided. Connect it if possible, but you don't have to. If you see this, your handle WAS successfully claimed!

• Wrong DID returned from server
  • This means you're trying to claim the handle on the wrong BlueSky account. Make sure you're using the BlueSky account with the handle you provided.

• Failed to verify handle
  • This means you've either not successfully claimed your handle, or your handle is incorrect. Make sure you type in your Discord username followed by .dis.blue and not your Discord display name.
  • If this issue persists, try claiming your handle again.

In some cases, your handle may become invalidated as below, there's several potential causes for this.

• You changed your Discord username
  • if this happens, the next time BlueSky checks to make sure you still own the handle, we'll tell them you don't. To fix this, change your username back and claim your handle again, or simply update your handle to your new username. Our backend will automatically switch your claimed handle over when you change your Discord username.
• You de-authorized the dis.blue app
  • We rely on maintaining a constant connection to Discord via OAuth2 to keep your handle active. If you de-authorize our application in your authorized apps settings on Discord, we lose this ability and you lose your handle. To fix this, simply claim your handle on this page again and make sure not to de-authorize the app.

If your Discord username has periods in it (.) - they will be removed. This DOES mean there's potential for clashing, but until I can work out a better way to handle them, that's the rub.

What do you do with my data?

The short answer: As litte as we possibly can.

The long answer: We store the following data for the service to function:

• Discord Username
  • We use this to associate your Discord username with your handle, if your username changes we will update this data the next time BlueSky checks to make sure your handle is still valid.
• Discord ID
  • We store this to associate your OAuth2 credentials with your BlueSky ID, so your BlueSky account is able to claim the username associated with your Discord ID.
• BlueSky ID
  • We store this to allow BlueSky to check you own your handle, and thus Discord username. This is also publicly associated with your Discord username via the AtProto well-known text file verification system. This is required for our service to work.
• Discord OAuth2 credentials
  • We store these so when BlueSky attempts to verify you own your handle, we can fetch your Discord account data freshly and make sure nothing's changed. If it has, we update it accordingly.

And here's what we don't store:

• Your Discord account connections
  • We only fetch these to verify you own your BlueSky account when you initially claim your handle.
• All other data from your Discord account
  • We don't store your display name, icon, banner, badges, or any other information.
• All other data from your BlueSky account
  • We don't store your current handle, or any other account metadata from BlueSky.

All data is encrypted at rest and stored in accordance with the Discord Developer TOS.

If you wish to delete your data, simply de-authorize the application in your Discord authorized apps settings, and when BlueSky next attempts to verify your handle ownership, everything will be wiped. Your Discord OAuth2 credentials are immediately invalidated when you de-authorize the app.

What's a BlueSky connection and why should I care?

BlueSky is a decentralized (no, not in the cryptobro way, no NFTs here) social media platform based around something called the AtProto. The idea of BlueSky is to have a completely transparent social media service, where you can choose to take additional control over your personal data and identity. It, alongside other federated social media such as Mastodon, are alternatives to the centralized social medias you may know like Twitter (nobody's calling it X), Reddit or Facebook.

Discord has recently added the ability to connect your BlueSky account to your Discord account via the account connections page! This means you can show off your BlueSky handle and following, like below: