Gregory's Server@trwnh No, urls are the easiest to share, as you can click on them. And they resolve to have links in, which code can look for as well as people.
trwnh.com doesn't have an lrrd link in it's host meta and webfinger 404s
https://trwnh.com/ gives me useful links, and with one more rel=me added would give you a green tick, like you did with https://abdullahtarawneh.com/ (which has no webfinger either, but has a nice h-card) https://indiewebify.me/validate-h-card/?url=https%3A%2F%2Fabdullahtarawneh.com%2F
|
Top-level
4 comments
 @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) @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....) |
@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