This is really neat! With the power of WebFinger, you can make your Mastodon account discoverable using your own domain name!
See it in action by searching for me with these custom addresses:
@me@breakdecks.com
@owner@prods.page
It's a bit kludgy if you make it static, so @<anything>@your.domain will end up working.
Thanks @maartenballiauw@mastodon.online for the writeup!
https://blog.maartenballiauw.be/post/2022/11/05/mastodon-own-donain-without-hosting-server.html
Oh, and it breaks every @ after the redirect in the same post! Look at that!
Thanks again @maartenballiauw. Looks your clever trick exposes a bug in Mastodon.
@Alex @maartenballiauw Thank you for over-sharing this spiffy trick! Looking forward to trying it out.
An aside, is there an established #MastodonBug or similar hashtag for bringing attention to possible bugs?
@dripsandcastle I should probably:
1. See if this condition exists in 4.0.2 (which means updating my instance 🙄)
2. If so, I should submit a bug report here: https://github.com/mastodon/mastodon/issues
(You could probably do this faster since you are on an instance running 4.0.2)
@Alex In the next few days I'll get my GitHub, personal site, and related verification links setup. I'm bookmarking your thread to revisit.
Also, If I find out elsewhere to tag bugs I'll add it here. I'm a fan of TODO and FIXME in code. See: https://marketplace.visualstudio.com/items?itemName=Gruntfuggly.todo-tree Having something like #MastodonBug would be equally satisfying.
Take care!
@Alex Haven't seen this yet on a v4 server. Does look like the resolving only works when logged in (e.g. user search on a random server where you are not authenticated seems to not be supported)
Okay, sorry for spamming this post repeatedly.
It turns out if you publishing a post with a custom address in it like this, you'll get an error message and it will look like it didn't send.
I just kept mashing that button while I investigated, and it really was publishing the post every time 😬