Everyone’s talking about using a domain as a Bluesky handle these days so we put together a guide to getting your own domain, using it for a Glitch website, and verifying yourself with it on both Bluesky and Mastodon.
Tell us about all your cool domains… 
project link in the post is missing the ~
good stuff, it was nice to learn how bluesky and mastodon do domain validation
Gah thanks for that, I had originally linked to the Glitch in Bio page which has no tilde but changed at the last minute 
We now also have a guide to autoposting to both Bluesky and Mastodon through API:
And companion starter app!
Someone able to help with an issue I have? My domain (ghostyboi.glitch.me) is not working on Bluesky, when I followed all the right steps, going to the .well-known page in question shows text that reads “Forbidden”. Could that be the issue?
Hi there, when I open your project I can’t see a file at .well-known/atproto-did so can you verify it’s there in the editor? I do see it listed in your .gitignore which may also be causing a problem.
I’ll try removing it from the .gitignore
I know the problem. Glitch keeps auto-deleting it, therefore making it impossible for me to verify my domain. I’ll try mastodon next
What is it you think Glitch is auto-deleting?
It’s deleting the .well-known/atproto-did. I have no idea why it’s doing this
Glitch shouldn’t be doing that so I think something else must be going on here. Can you try downloading the project from the editor to check if the file is in there? If a file is in your gitignore it won’t display in the editor by default.
Note that depending on the server package your project is using, just creating a .well-known directory in the root of your project will not expose anything as URL. If this is a static site, the .well-known dir will work (Glitch doesn’t delete any files automatically), but if it’s not, you need to configure your build or server so that it exposes that directory, or make sure that directory exists inside your static asset location (or both, possibly).
It looks like you made a dir called well-known, so it’s missing the . at the front. It has to be named exactly .well-known for things to work.
That’s odd, I cannot see that.
When in doubt, open the terminal (button at the bottom) and inspect your files that way. ls -hals shows a directory called well-known (and now a directory called .well-known, too).
I’ve just downloaded and extracted the site, I see what you’re talking about now.
And it is there in the terminal too. Is there a way I can unhide it?
If there’s content in the dir that’s not showing in the editor, you can also run the refresh command in the terminal, which reloads the editor with an explicitly updated list of files.
One thing that may be happening, and I’ll have to look into that if it turns out things still don’t work, is that dot files and dot dirs are not being uploaded as part of your site for security reasons (as the dot-name convention usually means “these are special, protected, private-to-this-content, files and/or directories” so they may be getting skipped)
I see what’s happening now. When I run the refresh command, the directories that are hidden don’t show up, and .well-known became a part of that list too
That would make sense, the only dotfile that has special exposing is the .env file, so you may need to do your .well-known edits through the terminal instead.