🤔 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.
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 🤣🤣
@prologic@twtxt.net I say we should find a way to support mentions with only url, no nick, as per the original spec.
- For
@<nick url>we already got support
- For
@<nick>the posting client should expand it to@<nick url>, if not then the reading client should just render it as@nickwith no link.
- For
@<url>the sending client should try to expand it to@<nick url>, if not then the reading client should try to find or construct a nick base on:
- Look in twtxt.txt for a
nick =
- Use (sub)domain from URL
- Use folder or file name from URL
- Look in twtxt.txt for a
Sounds about as complex as adding @nick@domain support by doing a webfinger lookup to get the URL.