@doesnm@doesnm.p.psf.lt So the user should then set nick = _@domain.tld in the twtxt.txt?
It seems more intuitive and userfriendly to just use: nick = domain.tld and have then convention for clients to render the handle as @domain.tld instead of @domain.tld@domain.tld
For a feed with no nick defined (eg. https://akkartik.name/twtxt.txt) it will also be simpler and make more sense to just use the domain as the nick and render it as @domain.tld
No, i mean just _. If my nick = _ and my twtxt is located at https://doesnm.cc/twtxt.txt then just display me as @doesnm.cc. Why it’s not intuitive?
@doesnm@doesnm.p.psf.lt That can be done fairly easily I think/
What should the advantage be to nick = _compared to just not defining a nick and let the client use the domain as the handle?
What is not intuitive is that you put something in the nick field that is not to be taken literary. The special meaning of _ is only clean if you read the documentation, compared to having something in nick that makes sense in the current context of the twtxt.txt.
@sorenpeter@darch.dk No I agree. I think if the feed doesn’t hint at a nick, just default to displaying the bare domain. These sorts of things btw need to go into a Client recommendations / guidelines. If someone wants to start drafting up such I doc I will fully support this and help shape it 👌
I’ve implemented Use only nick as handle if nick and domain is the same · sorenpeter/timeline@8c12444
See it live at:
I’m not sure I like the leading @ thou…
hmm any ideas how to fix this case when there is no nick and it on a shared tilde hosting? http://darch.dk/timeline/profile?url=https://tilde.club/~deepend/twtxt.txt