@darch@neotxt. Thatβs wrong.
$ bat https://twtxt.net/twt/xzi7m6q | jq -r '.text'
(#kwyhrda) @<darch@neotxt https://neotxt.dk/user/darch/twtxt.txt> Looking great! :-)
I guess @lyse can't blame
yarnd1 for this one π€£ Hehe π
-- But seriously, this is the problem with essentially what are free-form mentions that have no validation. If we seriously reconsidered what I _was_ trying to propose some months ago about formalizing a @user lookup spec and validation for @-mentions (_which yarnd implements, but is undocumented and I never spec'd it..._) this _might_ be solvable...
$ bat https://twtxt.net/twt/xzi7m6q | jq -r '.text'
(#kwyhrda) @<darch@neotxt https://neotxt.dk/user/darch/twtxt.txt> Looking great! :-)
I guess @lyse can't blame
yarnd1 for this one π€£ Hehe π
-- But seriously, this is the problem with essentially what are free-form mentions that have no validation. If we seriously reconsidered what I _was_ trying to propose some months ago about formalizing a @user lookup spec and validation for @-mentions (_which yarnd implements, but is undocumented and I never spec'd it..._) this _might_ be solvable...
$ bat https://twtxt.net/twt/xzi7m6q | jq -r '.text'
(#kwyhrda) @<darch@neotxt https://neotxt.dk/user/darch/twtxt.txt> Looking great! :-)
I guess @lyse can't blame
yarnd1 for this one π€£ Hehe π
-- But seriously, this is the problem with essentially what are free-form mentions that have no validation. If we seriously reconsidered what I _was_ trying to propose some months ago about formalizing a @user lookup spec and validation for @-mentions (_which yarnd implements, but is undocumented and I never spec'd it..._) this _might_ be solvable...
$ bat https://twtxt.net/twt/xzi7m6q | jq -r '.text'
(#kwyhrda) @<darch@neotxt https://neotxt.dk/user/darch/twtxt.txt> Looking great! :-)
I guess @lyse can't blame
yarnd1 for this one π€£ Hehe π
-- But seriously, this is the problem with essentially what are free-form mentions that have no validation. If we seriously reconsidered what I _was_ trying to propose some months ago about formalizing a @user lookup spec and validation for @-mentions (_which yarnd implements, but is undocumented and I never spec'd it..._) this _might_ be solvable...
I've also implemented an experimental feature called WebFinger (
webfinger) in d940da9f05 which I'm _hoping_ will "just work"β’ π€ (at least to provide webfinger lookups) -- client-side lookups and discover can come later.
I've also implemented an experimental feature called WebFinger (
webfinger) in d940da9f05 which I'm _hoping_ will "just work"β’ π€ (at least to provide webfinger lookups) -- client-side lookups and discover can come later.
I've also implemented an experimental feature called WebFinger (
webfinger) in d940da9f05 which I'm _hoping_ will "just work"β’ π€ (at least to provide webfinger lookups) -- client-side lookups and discover can come later.
I've also implemented an experimental feature called WebFinger (
webfinger) in d940da9f05 which I'm _hoping_ will "just work"β’ π€ (at least to provide webfinger lookups) -- client-side lookups and discover can come later.
- What should the mime-type for the Twtxt feed be? Should we define one (even if its accepted by the W3C at this point)? π€
- What other data/properties should we return (fi any)? π€
- What should the mime-type for the Twtxt feed be? Should we define one (even if its accepted by the W3C at this point)? π€
- What other data/properties should we return (fi any)? π€
- What should the mime-type for the Twtxt feed be? Should we define one (even if its accepted by the W3C at this point)? π€
- What other data/properties should we return (fi any)? π€
- What should the mime-type for the Twtxt feed be? Should we define one (even if its accepted by the W3C at this point)? π€
- What other data/properties should we return (fi any)? π€
"nick": field in the JSON
nick hmmm I wonder if that's even a valid / commonly accepted rel ... π€
nick hmmm I wonder if that's even a valid / commonly accepted rel ... π€
nick hmmm I wonder if that's even a valid / commonly accepted rel ... π€
nick hmmm I wonder if that's even a valid / commonly accepted rel ... π€
-- 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)