↳ In-reply-to » @prologic For all the twtxt archeologists out there, that is the historic moment on how it all began. Unfortunately, yarns doesn't seem to have all (?) of prologic's archive feed, but somehow mine, hence only my replies show up when I search for that conversation. Quite weird. Maybe user error, no idea. But it must have been after the twt hash change, so the hashes should match, as seen by the first link in this twt. Anyways, I reconstructed that conversation by hand using the archive feeds: https://lyse.isobeef.org/tmp/avatar-story.txt

Btw, @prologic@twtxt.net, I reckon the yarnd generated archive feed URLs are not stable and thus kind of contradict the Archive Feeds Extension, which states:

Once they are made public, [archive feeds] are supposed to be left alone and won’t receive further updates. Deletion or editing is still allowed, but feed authors should not expect clients to retrieve archived feeds on a regular basis (or at all).

Looking at your main feed URL https://twtxt.net/user/prologic/twtxt.txt, the prev points to https://twtxt.net/user/prologic/twtxt.txt/1 and that in turn links to https://twtxt.net/user/prologic/twtxt.txt/2. Here the chain ends. That means whenever a new archive feed is generated, the URLs change. Or viewed differently, the URL suddenly provides a differnt content. That probably causes clients to not update their caches properly, because they always see the same …/twtxt.txt/1 in the main feed’s prev and think that nothing changed, which contradicts the promise of the spec.