↳ 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

As for pagination, sure, it can be hard, but why would it be harder in this case than in the cases where Yarn already does it?

It’s done in the background as a background job. See this Dashbaord for a visuaul:

(As for infinite scroll, if you have pagination on the server side already, it’s trivial on the client side. Yes you need JS of course, but not a lot)

Remember the builtin Web Interface (an SSR) is designed to be able to used without Javascript (graceful degradation).