↳
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.
@tkanos@twtxt.net That’s right, I believe we have enough data to identify if a Twt was edited and I think we can figure out a nice way to deal with this. Essentially it causes forks.