@andros Thanks for consolidating a lot of good ideas. Especially how you have deiced to just extend the mention syntax for location-based treads. This might even be backward compatible with older (pre-yarn) clients. What about using Z for UTC +00:00- is that allowed in your specs? Regarding url = I would suggest to only allow one and the maybe add url_old = or url_alt = !? I'm still not a fan of a DM feature, even thou it helps that i have now been split out into a separate feed file. Instead if would suggest a contact = field for where people can put an email or other id/link for an established chat protocol like signal or matrix.

@sorenpeter you wrote:

"This might even be backward compatible with older (pre-yarn) clients."

Yarnd is as backwards compatible with older clients as this. I dare to say, even more so. 😅

@bender My point was that the suggested syntax for extending mentions to point to a specific message (<a href="/profile?url=url timestamp">@nick</a>) and having location based treading this way, might not break older clients, since they might just igonore the last value within the brackets.

Yes it seem to work(ish) on timeline at least: https://darch.dk/timeline/post/imopblq

But Yarn does not like it: https://twtxt.net/twt/yoatzwa

Why are we testing, or playing with, an alternate non-fully-compatible feed format within the same feed that we use daily?

In other words, why didn't you all do the same that @movq did, and setup a completely different feed for this?

@bender I think this would be a good idea as @movq and @andros have done ✅ I may even join the experiments if I have any spare time to hack a custom yrand branch and run it up on say something like a yarnexp.mills.io or something 🤔

Well because I can and want to see what will happen :)