@joeld@jesse It's possible to have Webfinger identities for the main domain, which use home pages and ActivityPub streams on a different hostname. So you could have your Web pages at <something>.<name>.<tld> but all the Webfinger addresses could be <user>@<name>.<tld>
@joeld@jesse The problem is that some programmers just do text manipulation on the Webfinger addresses instead of doing the work of discovering the important info. This is a bugfeature of Webfinger.
@joeld@jesse@evan You can have your instance wherever, and have @<user>@<name>.<tld> point there. For wherever, I'd go with something like fedi or social. Definitely not Mastodon (because if you ever change server software, you can't use Mastodon as the hostname due to its trademark), and not any other software name, either.
I think there was a plan at one point to use SRV records in DNS as a way to find the right server to query for Webfinger, but it was too complex and didn't end up in the final spec.
@evan@algernon@jesse OK I see, except it’s really not like MX at all. It’s not handled via DNS but by making sure your web server is set up to redirect certain HTTP requests. (Good luck if your domain points at something like Wix or Squarespace?) It would have been a lot simpler if they had used a DNS-based approach instead.
@evan@joeld@algernon@jesse Maybe I'm not understanding something about this, but if I do a webfinger redirect from my domain (say, @me@stevebate.net) to @steve isn't the latter still going to be my "real" federation identity? My posts will still be published using the mastodon.tech instance address, right?
@admin@algernon@evan@jesse@joeld I've read the WebFinger spec and it seems like it could *theoretically* do what we're discussing, but unless an instance has code to implement a proxy for the external account alias, I don't see how it would work in practice.