↳ 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.

One thing I want to point out is that this “problem” (per se, remember it’s a design decision) also exists in other places like:

Cache expired posts vanish from threads with no warning - yarn - Mills

As Twts fall off the active Cache and are archived in an on-disk Archive, Yarns and Twts eventually “disappear” (they don’t really, they are still searchable and accessible as everything is content addressable).