↳ In-reply-to » @nexeq given lightweight nature of yarnd and the twtxt protocol in general relying on a text file and a cache layer, a poderator who would desire to have n(x) timeline (i.e. all tweets from 2017 to today) would have to invest heavily in infrastructure and the protocol twtxt and client yarnd would have to be redesigned from the ground up.

@caesar@twtxt.net

Particularly with the apparent convention of the newest posts being at the bottom of the file.

This is generally the convenatio, yes. And folks like @lyse@lyse.isobeef.org @xuu@txt.sour.is @movq@www.uninformativ.de and I have considered and talked about formalizing the “direction” of a feed including supporting “Range” requests. These are both things that I will likely do myself at some point, because it further helps with optimizing the traffic/bandwidth used and helps keeps things running smoothly as the network scales over time.