So, @prologic@twtxt.net, having a slash on the nick breaks mentions. Is there a consensus on which characters are allowed on nicks, or just about anything goes? Evidently I am not going to be exchanging that many twts (if anything at all) with someone with a slash on their nick, but it would be nice to either set some “standard”, or fix mentions (again?!) to accommodate.

@fastidious@arrakis.netbros.com yeah the thing is the original twtxt (legacy) spec never really specified any standards around what constitutes a valid source.nick. So this is a bit of a source of contention right now, especially with folks like @ew0k/BW – I’m currently not sure what to do about it as this affects not only yarnd but others clients too. Parsers have to be updated and changed and that’s actually a lot more work than just simply one person just adjusting their “advertised” nick to something more reasonable. (Sorry @ew0k/BW)

My $0.02 worth (cc @lyse@lyse.isobeef.org and @movq@www.uninformativ.de on standards) is we should stick to the already accepted and conventional standard of ^[a-zA-Z0-9][a-zA-Z0-9_-]*$ or equivalent.

@movq@www.uninformativ.de Good! I’m glad it’s quite easy to reach consensus on this 👌 Where do we document and formalize this? How many folks do we need to get “buy-in” from? 🤔

@lyse@lyse.isobeef.org Hmmm you do raise a good point. So if anything:

except a space and closing angle bracket

So I guess we should update the lextwt parser ?🤔

@thecanine@twtxt.net I think you replied in the wrong thread/yarn 😅

@thecanine@twtxt.net No worrries 🤗

Gets kind of difficult to support spaces when a space is the token separates 😂

@lyse@lyse.isobeef.org Of we added support for “Display Name” it would just be abolition free-form Metadata field used for display purposes only.

@lyse@lyse.isobeef.org No you’re right, it’s a stupid idea and we shouldn’t do it for all the reasons @thecanine@twtxt.net spelled out 😂