↳
In-reply-to
»
@darch I kind of agree that we can probably omit the nick part in mentions entirely. Since they can be looked up and cached, there's no need for this. But we'll have to spec this all up. First let's see what @lyse and @movq and others like @anth thing about finally formalising a standard way to lookup feed URI(s) and define a slightly more saner? @-mention syntax/usage pattern. I for one hate manually typing out (for example)
โค Read More
@<darch https://neotxt.dk/user/darch/twtxt.txt>
like this @darch ๐
It is not all twtxt.txt file that adhere to having a nick =
or url =
field int them, so the only information we can be sure of is a URL to where the twtxt.txt is served from. That leads to using a domain+path-to-twtxt.txt as be most unambiguous identification and also how the original @<URL>
mention are defined in line with the indieweb way of using a domain as id.
But with muti-user pods this get messing with urls like https://neotxt.dk/user/darch/twtxt.net
, when it would be much nicer if we had http://darch.neotxt.dk/twtxt.txt
like on https://darch.neocities.org/twtxt.txt and then we could omit the /twtxt.txt
in daily conversation. </ramble>