↳
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
⤋ Read More
twtxt and client yarnd would have to be redesigned from the ground up.
@mutefall@twtxt.net pagination is also kind of tricky to do in the first place, because the entire feed has to be parsed, loaded into memory, then paginated. it’s terribly inefficient. one could argue you could use a giant big SQL database and come up with some kind of schema, but that’s not really the point I don’t think nor really desirable for many reasons.