|
Top-level
 @kevinmarks oh hmm, both trwnh.com and abdullahtarawneh.com are green ticks for me over here as far as webfinger resolving, i was giving a hypothetical example that is currently not valid but might be valid in the future when i get around to actually implementing my new (dynamic) website :roundboi: currently i just have *.trwnh.com dns resolving to trwnh.com and any unrecognized resource maps to 404 via nginx 3 comments
@trwnh but it isn't human friendly. @kevinmarks well again, that's dealing purely within the realm of mastodon, which i think we can agree does not strictly *need* webfinger, but i still think it is useful for interop note that the mastodon web domain and webfinger domain do not have to be the same, either -- i could host mastodon.trwnh.com and have a profile at mastodon.trwnh.com/@a, but still use the webfinger address a@trwnh.com for consistency with my email and xmpp (although with that said, i do not wish to run mastodon....) |
Gregory's Server
@kevinmarks fwiw what i was trying to say is that the human-friendly identifier (webfinger) should resolve to the machine-friendly identifier (activitypub id, which can be reasonably resolved via https and parsed by code)