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

There are very good technical reasons for this design, but there are also very good human reasons for this too .

As my old man said to me many moons ago when I was first designing this (he helped and contributed ideas here!):

If I said something X ago, I don’t want someone to say “Hey but X ago you said this”. What if I’ve changed my mind since then and now have a different opinion?

I’m paraphrasing here of course, we talk regularly on the phone, but a lot of ideas ans inspiration has come from my Dad 👌 – The idea here is that Humans forget, so should Yarn.social