@lazarus @prologic (#bai3sla) This wellknown mechanism seems like a nice thing. But I only know it from OIDC and Let's Encrypt. I personally don't care so much about these "handles". Twtxt just says, you need a public file and a nick, that's all. As @movq pointed out, some clients understand `# nick = foobar` comments in the feed. So, not sure, what the wellknown here would actually bring new to the plate. Rewriting URLs definitely breaks twtxt mentions, that's for sure.

@lyse @lazarus (#bai3sla) Hmmm I’ll have a think about it for yarnd

@adi (#bai3sla) Looks great!

@lazarus (#bai3sla) In plain twtxt, none of this is really specified. 😢 That part of the protocol is not so great. In plain twtxt, *my followers* must configure that the URL belongs to the username “movq”. So it has to be done manually. 😢 That being said, you can put a `# nick = foobar` at the top of your feed and *some* clients will pick it up and show this as your nick. All the `@username@yarn.domain.tld` stuff that you see in Yarn.social is actually just a Yarn convention – maybe @prologic can tell you more about how exactly that works. 🙂

@lazarus (#bai3sla) It takes a smart person to realize he's a dummy! 😁 You don't need help, you have a full support crew @eldersnake @jlj @lyse @movq @prologic, @xjix @xuu @adi and others. 😎

@lyse @lazarus (#bai3sla) I think the .well-known stuff is just convention right? 🤔

(#bai3sla) @prologic @movq How can you specify your handle? Do other sites recognise it depending where the twtxt.txt is located? e.g. Can I host a pod publicly at yarn.domain.tld but have the yarn handle just as ` @username@domain.tld instead of @username@yarn.domain.tld ` I mean, from the perspective of everyone else. I realise the profile will still be viewable at yarn.domain.tld/user/username

@lazarus (#bai3sla) Hmmm no only the former is supported

(#bai3sla) @prologic So it works for @lyse and @movq because they are just hosting a twtxt file and not a pod? They can still have landing page for their website and have their handle at the domain.tld level this way. It's not a big issue for me, was just wondering if it were possible to make use of a .well-known in nginx.

@lyse @prologic (#bai3sla) For example I have currently running a Matrix server here with the following `server { server_name ix.social; ... location /.well-known/matrix/server { return 200 '{ "m.server": "syn.ix.social:443"}'; ... } location /.well-known/matrix/client { return 200 '{"m.homeserver": {"base_url": "https://syn.ix.social:443"}}'; ...` This allows the user handle to be username@ix.social instead of username@syn.ix.social where Synapse is running.