@darch@neotxt Looking great! :-)

@lyse@lyse.isobeef.org you mention here looks wierd

@darch@neotxt.dk What makes you say that? 🤔

@prologic@twtxt.net it shows as @darch@neotxt. That’s wrong.

@bender@twtxt.net Oh I missed that! 😱

@lyse@lyse.isobeef.org any idea how to fix this accoss pods and self hosted twtxt files?

@darch@neotxt.dk I doubt it 😆 To be proper decentralized means there are no central points of control or decision making 🤣

@prologic@twtxt.net no but we could make some recommendations for how clients are to deal with issues like this

@darch@neotxt.dk I just totally missed the fact that the mentioned URI was just entirely 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@lyse.isobeef.org 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@userlookup spec and validation for @-mentions (_whichyarndimplements, but is undocumented and I never spec'd it..._) this _might_ be solvable...

I believe it was @anth@a.9srv.net also that recently mentioned in #7xnsrsa his own frustrations with this and suggested maybe we could look at using WebFinger – Which honestly is probably not really all that hard, it uses (AFIK) a WKD lookup/discovery, not too dissimilar from the one used by Salty Chat 👌

I’ve built a client and server library and command-line tool (combination of a bunch of code I found and fixed up): https://git.mills.io/prologic/webfinger

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.

Some questions…

• 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)? 🤔

Well that now works 🥳 (at least on my pod):

@prologic@twtxt.net cool, so can this be used to improve the data quality of various nicks on each pod? I don’t see a "nick": field in the JSON

@darch@neotxt.dk Oh? You want a nick hmmm I wonder if that’s even a valid / commonly accepted rel … 🤔

Doesn’t appear to be.

This is now correctly working rather nicely 👌

– 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)