For example, this links to the previous post, no crypto needed: http://a.9srv.net/tw.txt#:~:text=2024-10-23T18:59:49-07:00

@sorenpeter ’s webmentions uses this trick: http://darch.dk/mentions-twtxt

@anth@a.9srv.net that doesn’t work because you need encode that URL, like so http://a.9srv.net/tw.txt#:~:text=2024%2D10%2D08-,2024%2D10%2D23T18%3A59%3A49%2D07%3A00

@doesnm@doesnm.p.psf.lt finally someone read my blogpost ;)

@doesnm@doesnm.p.psf.lt like OP, that will not work, as it has wrong/incomplete information.

@Codebuzz@www.codebuzz.nl I really like this idea of just using the Feed’s # nick as a sort of “identifier”. This gets us out of this mess of when feeds move locations or authors decide to host on 3 or 4 different protocols 🤣 Downside? Something picks the same nick? (they’ll still hash differently, so that’s fine).

@prologic@twtxt.net yeah short Nick is going to be unique enough. There is always olong Nick that adds the domain for differentiation.