yarnd has a similar thing where we maintain a similar mapping per user and have lookup for that), then we can avoid this whole "bad data" mess in the first place. I'd also be interested to know what folks like @anth was thinking too when he mentioned the use of WebFinger. Anyway we'll see how this pans out, yarnd (at least my pod) now has an experimental webfinger endpoint where you can do for example $ webfinger prologic@twtxt.net
yarnd has a similar thing where we maintain a similar mapping per user and have lookup for that), then we can avoid this whole "bad data" mess in the first place. I'd also be interested to know what folks like @anth was thinking too when he mentioned the use of WebFinger. Anyway we'll see how this pans out, yarnd (at least my pod) now has an experimental webfinger endpoint where you can do for example $ webfinger prologic@twtxt.net
yarnd has a similar thing where we maintain a similar mapping per user and have lookup for that), then we can avoid this whole "bad data" mess in the first place. I'd also be interested to know what folks like @anth was thinking too when he mentioned the use of WebFinger. Anyway we'll see how this pans out, yarnd (at least my pod) now has an experimental webfinger endpoint where you can do for example $ webfinger prologic@twtxt.net
yarnd has a similar thing where we maintain a similar mapping per user and have lookup for that), then we can avoid this whole "bad data" mess in the first place. I'd also be interested to know what folks like @anth was thinking too when he mentioned the use of WebFinger. Anyway we'll see how this pans out, yarnd (at least my pod) now has an experimental webfinger endpoint where you can do for example $ webfinger prologic@twtxt.net
acct: could mean anything I guess
acct: could mean anything I guess
acct: could mean anything I guess
acct: could mean anything I guess
yarnd already does this today really, based on what's in your "Followings" list on your account, which basically is a mapping of nick -> url of the feeds you follow. Really it could just be a simple list and we could drop the nick there too at some point (as again, we can just look them up and cache)
yarnd already does this today really, based on what's in your "Followings" list on your account, which basically is a mapping of nick -> url of the feeds you follow. Really it could just be a simple list and we could drop the nick there too at some point (as again, we can just look them up and cache)
yarnd already does this today really, based on what's in your "Followings" list on your account, which basically is a mapping of nick -> url of the feeds you follow. Really it could just be a simple list and we could drop the nick there too at some point (as again, we can just look them up and cache)
yarnd already does this today really, based on what's in your "Followings" list on your account, which basically is a mapping of nick -> url of the feeds you follow. Really it could just be a simple list and we could drop the nick there too at some point (as again, we can just look them up and cache)
yarnd implement this, as well as all feeds and the main frontpage discover feed too π
yarnd implement this, as well as all feeds and the main frontpage discover feed too π
yarnd implement this, as well as all feeds and the main frontpage discover feed too π
yarnd implement this, as well as all feeds and the main frontpage discover feed too π
@<darch https://neotxt.dk/user/darch/twtxt.txt> like this @darch π
@<darch https://neotxt.dk/user/darch/twtxt.txt> like this @darch π
@<darch https://neotxt.dk/user/darch/twtxt.txt> like this @darch π
@<darch https://neotxt.dk/user/darch/twtxt.txt> like this @darch π
$ 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.
$ 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.
$ 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.
$ 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.
webfinger you can intall with go install go.mills.io/webfinger/cmd/webfinger@latest and use like this:
webfinger prologic@twtxt.net
webfinger you can intall with go install go.mills.io/webfinger/cmd/webfinger@latest and use like this:
webfinger prologic@twtxt.net
webfinger you can intall with go install go.mills.io/webfinger/cmd/webfinger@latest and use like this:
webfinger prologic@twtxt.net
webfinger you can intall with go install go.mills.io/webfinger/cmd/webfinger@latest and use like this:
webfinger prologic@twtxt.net
nick somehow to the JRD (JSOn resource Data?) would really help here anyway. What this _would_ help with however if we got this spec'ed up and into clients is a way to validate -mentions and feed URI lookups.
nick somehow to the JRD (JSOn resource Data?) would really help here anyway. What this _would_ help with however if we got this spec'ed up and into clients is a way to validate -mentions and feed URI lookups.
nick somehow to the JRD (JSOn resource Data?) would really help here anyway. What this _would_ help with however if we got this spec'ed up and into clients is a way to validate -mentions and feed URI lookups.
nick somehow to the JRD (JSOn resource Data?) would really help here anyway. What this _would_ help with however if we got this spec'ed up and into clients is a way to validate -mentions and feed URI lookups.
-- If anyone wants to give this a try, just docker pull prologic/yarnd:latest (if you're running using Docker) or git pull and rebuild, then either --enable-feature webfinger or add it to Settings -> Poderator Settings and restart (or edit /path/to/data/settings.yaml)
-- If anyone wants to give this a try, just docker pull prologic/yarnd:latest (if you're running using Docker) or git pull and rebuild, then either --enable-feature webfinger or add it to Settings -> Poderator Settings and restart (or edit /path/to/data/settings.yaml)
-- If anyone wants to give this a try, just docker pull prologic/yarnd:latest (if you're running using Docker) or git pull and rebuild, then either --enable-feature webfinger or add it to Settings -> Poderator Settings and restart (or edit /path/to/data/settings.yaml)
-- If anyone wants to give this a try, just docker pull prologic/yarnd:latest (if you're running using Docker) or git pull and rebuild, then either --enable-feature webfinger or add it to Settings -> Poderator Settings and restart (or edit /path/to/data/settings.yaml)
> How can we make doing this sort of awful shit harder (or impossible) on Yarn pods?
I don't give a shitβ’ what anyone does on their own Twtxt feed personally, I just don't follow that god awful shit, not that I've ever found any π
> How can we make doing this sort of awful shit harder (or impossible) on Yarn pods?
I don't give a shitβ’ what anyone does on their own Twtxt feed personally, I just don't follow that god awful shit, not that I've ever found any π
> How can we make doing this sort of awful shit harder (or impossible) on Yarn pods?
I don't give a shitβ’ what anyone does on their own Twtxt feed personally, I just don't follow that god awful shit, not that I've ever found any π
> How can we make doing this sort of awful shit harder (or impossible) on Yarn pods?
I don't give a shitβ’ what anyone does on their own Twtxt feed personally, I just don't follow that god awful shit, not that I've ever found any π