Testing something… @@example.com
For people using clients other than yarnd, does that appear as a valid mention? It’s valid according to the spec but I’ve never seen it in use anywhere.
Mentions are embedded within the text in either
@<source.nick source.url>or@<source.url>format and should be expanded by the client, when rendering the tweets.
@mckinley@twtxt.net Without a nick, we’d (yarnd) would have to go fetch the feed, parse it, cache it and then render it properly. This kind of “form” I think should be illegal IMO.
@tkanos@twtxt.net, do you have a dump of all the twtxt feeds from doing we-are-twtxt? If so, could you please upload a tarball somewhere or send me a magnet link? I want to grep it for this crazy mention syntax.
@mckinley@twtxt.net Too bad I can’t think of a way to do this via the search engine 🤔
@movq@www.uninformativ.de is right, it’s still valid but it is hard to render as anything beyond a URL? 🤔
@mckinley@twtxt.net @lyse@lyse.isobeef.org I clean m’y code today and release it tomorrow or tonight.
@mckinley@twtxt.net here is the dump https://github.com/tkanos/we-are-twtxt (on the tarball all-twtxt.tar.xz)
Outside of this thread, this comment syntax has been used exactly twice when searching every known, currently accessible twtxt feed on the Web.
$ grep -r '@<[^ ]*>'
buckket.org.txt:2016-02-12T18:37:00+01:00 Hey @<http://vigintitres.eu/twtxt.txt>, @<teddy https://data.trafficking.agency/twtxt.txt> und @Jim@example.org was geht? Ich bin’s @GEHEIM@buckket.org!
[...]
hecanjog.com.txt:2020-09-03T17:36:00-05:00 @https://tilde.town/~lucidiot/twtxt.tx@ twtxt via DNS TXT would be insane and fun.
@mckinley@twtxt.net Cool! 👌 So… Let’s nuke it? 🤔 Are you thinking of writing a new spec?