↳
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.
I also totally get whet you’re saying about a twtxt file potentially growing to be huge. I guess that, and the fact that it’s necessary to work around it with a significant caching architecture, is a major downside to the model of twtxt itself which I hadn’t considered.