Testing mentions, immediately followed by commas. Let’s see: @prologic@twtxt.net, this one is local, it might not break. Now, this one @ isn’t local. Nor this @ one. Will they break. Let’s find out!

That’s kind of weird actually. Hmmm @ @ and @bender@twtxt.net are all cool 😎

Whereas @movq@www.uninformativ.de @lyse@lyse.isobeef.org and @bender@twtxt.net are all cool 😎

I’ll see if I can fix this and write a test case for what’s going on here. I think this is made difficult now because folks like @eapl.me@eapl.me decide that it’s okay to have a . (period) in their # nick 🤣 tbh I think nick(s) should have rules of what they can and cannot be comprised of. i.e: no punctuation 🤦‍♂️

There are 5 of such “Twters” on this pod that have periods in their nick 😢

sqlite> select count(distinct(nick)) from twters where nick like '%.%';
count(distinct(nick)) = 5
sqlite> select distinct(nick) from twters where nick like '%.%';
 nick = @marado@ciberlandia.pt

 nick = eapl.me

 nick = eapl.mx

 nick = grumpygordie.great-site.net

 nick = @chyrp.doesnm.cc

@prologic@twtxt.net how about @ and @ Will that work?

@bender@twtxt.net I can fix and make that work in the parser too. But I’m no longer sure how to cater for the general case. It’s too much to support all punctuation whilst at the same time as other contradicting rules. For example you cannot both support . in nicknames and then expect to be able to to end a mention with a . 🤦‍♂️

@prologic@twtxt.net it’s a pickle. Then sanitise the outliers. No other way.

@bender@twtxt.net I believe that’s the only way. We’ll deal with it as it comes up I think.

This is fixed now 🥳 Thanks @xuu@txt.sour.is!

@bmallred@staystrong.run Nice! 👌

hehe, just catching up on this thread! I’ve replied in another that using periods/dots sounds good to me as it’s usual in domains, but perhaps some agreement would be needed. For now I think any character is valid as long as it is not a space.
For example we are using this for PHP twtxt.php#L153