(#ezygx4a) @abucci Did you miss #33jt3fa and the subsequent twts in that yarn? 🤔

(#ezygx4a) I guess in general though, it's a pretty good lookup mechanism. I also wrote a command-line tool `webfinger` you can intall with `go install go.mills.io/webfinger/cmd/webfinger@latest` and use like this: ``` webfinger prologic@twtxt.net ```

(#ezygx4a) I guess its usage in Twtxt clients could be something like this: ``` $ webfinger prologic@twtxt.net | jq -r '.links[] | select(.rel=="Self").href' 2023/01/06 02:32:40 Looking up WebFinger data for acct:prologic@twtxt.net 2023/01/06 02:32:40 GET https://twtxt.net/.well-known/webfinger?resource=acct%3Aprologic%40twtxt.net https://twtxt.net/user/prologic/twtxt.txt ``` Where a lookup of user@domain would yield the Twtxt feed for that user+domain pair.

(#ezygx4a) @prologic I understand, but it seems to me that you can do more or less the same stuff with IndieWeb's `h-card` () and related standards.

(#ezygx4a) @abucci You can, however that is not a lookup mechanism, more of a publishing standard. And yes all profile pages in `yarnd` implement this, as well as all feeds and the main frontpage discover feed too 👌

(#ezygx4a) Use Preview to check this out on any frontpage of a pod or profile page 👌

(#ezygx4a) @prologic since in IndieAuth your URL is your username, it *is* a lookup mechanism. You download the page pointed to by the URL, parse out the `h-card` and other records, and now you have additional data. `webfinger` seems to be stuck in the "account-first" mindset. I guess that's how it's different.

(#ezygx4a) I always thought that was pretty elegant because you don't need to host yet another discovery service and deal with all the maintenance and security headaches that entails. You just need a stable domain name and a web site you control.

(#ezygx4a) @abucci This is a little different though 😆

(#ezygx4a) @abucci Yeah and I guess the nice thing is `acct:` could mean anything I guess