# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 32
# self = https://watcher.sour.is/conv/ezygx4a
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?
@abucci Did you miss #33jt3fa and the subsequent twts in that yarn? 🤔
@abucci Did you miss #33jt3fa and the subsequent twts in that yarn? 🤔
@abucci Did you miss #33jt3fa and the subsequent twts in that yarn? 🤔
@abucci Did you miss #33jt3fa and the subsequent twts in that yarn? 🤔
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
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
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
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
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.
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.
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.
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.
@prologic I understand, but it seems to me that you can do more or less the same stuff with IndieWeb's h-card (https://indieweb.org/h-card) and related standards.
@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 👌
@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 👌
@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 👌
@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 👌
Use Preview to check this out on any frontpage of a pod or profile page 👌
Use Preview to check this out on any frontpage of a pod or profile page 👌
Use Preview to check this out on any frontpage of a pod or profile page 👌
Use Preview to check this out on any frontpage of a pod or profile page 👌
@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.
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.
@abucci This is a little different though 😆
@abucci This is a little different though 😆
@abucci This is a little different though 😆
@abucci This is a little different though 😆
@abucci Yeah and I guess the nice thing is acct: could mean anything I guess
@abucci Yeah and I guess the nice thing is acct: could mean anything I guess
@abucci Yeah and I guess the nice thing is acct: could mean anything I guess
@abucci Yeah and I guess the nice thing is acct: could mean anything I guess