I stumbled on a plugin to add `webfinger` info to my web site, so I installed it and....what now? It seems to work fine, but what the heck is `webfinger` good for?
(#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
```
matched #7mkcd7a score:11.81
Search by:
Search by 1 tags:
(#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.
matched #axnl2ea score:11.81
Search by:
Search by 1 tags:
(#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 ๐
matched #qgt7cjq score:11.81
Search by:
Search by 1 mentions:
(#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.
matched #y5f7h5a score:11.81
Search by:
Search by 1 mentions:
(#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.
matched #cpewzga score:11.81
Search by:
Search by 1 tags: