🤔 Prosoal: Disallowed the @<url> form of mentions. Strictly require that all mentions include a nickname/name; i.e: @<name url>.
@head_honcho_supremus@twtxt.net sounds good but, when using Yarn—at least—users shouldn’t need to worry about this minutiae. They simply hit “Reply”, or “Fork”.
Note, I manually added a nick to this reply.
@bender@twtxt.net I agree. I’m just saying spec-wise, this makes implementations have to worry about less edge cases like this 🤣
Otherwise if we insist on allowing things like @<url> then I have to do quick a bit of dancing to figure out how to render such mentions sanely 😅😅
What say you @movq@www.uninformativ.de @lyse@lyse.isobeef.org @eapl.mx@eapl.mx / @darch@neotxt.dk @andros@twtxt.andros.dev (new client author)? 🤔 Shall I PR this up?
For the record; we consider the new authority on the Twtxt spec(s) going forward (has been for some years actually) to be implementers / primary maintainers of widely used clients. To date that is:
yarnd@prologic@twtxt.net (me and others)
jenny@movq@www.uninformativ.de
tt@lyse@lyse.isobeef.org
Timeline@darch@neotxt.dk / @eapl.me@eapl.me and others
twtxt-el? – @andros@twtxt.andros.dev
Full list of supported and widely used clients can be found at https://twtxt.dev/clients.html – which I note a few above are actually missing from this page haha 🤣
@prologic@twtxt.net Fine by me. I don’t see/remember a valid reason for just doing @. Was there ever a reason to do that? 🤔
@prologic@twtxt.net @movq@www.uninformativ.de Well, the original Twtxt Specification explicitly allows for the short form with just a URL and no nick: https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html#format-specification
Mentions are embedded within the text in either
@<source.nick source.url>or@<source.url>format […]
I’d just continue supporting it, even though I don’t see it all that often in the wild. I guess more common is the case where just a nick is given, which is illegal. But yarnd users seem to produce it every now and then.
What’s the motivation for deprecation?
tt currently supports all three forms: @<nick url>, @<url> and even the illegal @<nick>. The difference between the last two is whether the token in angle brackets looks like a URL or not. Whenever a nick is available, the nick is rendered. In case there is just a URL, it tries to resolve the nick from the subscriptions. If that also does not work, it displays the URL.
What’s the motivation for deprecation?
Namely that without the mention having a label (as such) it becomes very hard to render it in any sane/nice way. I think we should just stick to @<label url> personally. It makes implementations have to worry about far less edge cases.
Was there ever a reason to do that? 🤔
I’m not sure to be honest. I have no idea why you’d ever want to do a “nameless” @-mention@twtxt.net.
As an aside, if we could all agree, I’d personally just say we scrap this whole fragile broken shit and bring out WebMentions and be done with it. And then mentions are always @nick@domain and looked up, cached and can never be screwed up haha 🤣
@prologic@twtxt.net If you’ve got the feed URL in yarnd’s cache, you can easily look up a missing nick. If you can’t find it, just show the URL (or maybe just the domain name to be halfway consistent with this @nick@domain thing that yarnd invented) and be done. It’s really that simple.
When yarnds peer with each other, the odds of actually having come across that feed URL in the past are higher than with traditional clients that only have their local set of subscribed feeds. One additional improvment would be to also look at all the mentions and see if somebody used a nick for that URL and go with that.
Yeah, yarnd currently renders some really weird shit when the mention contains just a URL, but I’d call that a bug for sure.
Personally, I do not like the @nick@domain syntax at all. It looks silly to my eyes. What might have also contributed is the fact of this mentions syntax gotten screwed up so many times by yarnd in the past. But that’s a totally different topic.
@lyse@lyse.isobeef.org Hmm you ate right 😆 Also did you volunteer to fix this 🤔🤣
@eapl.me@eapl.me yeah, it is a typo, meant to be proposal. OP is the “Lord of the Typos”. :-P
@bender@twtxt.net Hahahahah 🤣🤣