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

@mutefall@twtxt.net It’s pretty easy to delete or even edit a Twt you posted on Yarn.social 😂 – But it has unintended side-effects, due to the decentralised nature, you end up with UX problems where for example, someone makes a Twt A, realizes they’ve made a typo or mistake or something, then edits it (which is equivalent to delete + repost) and posts a new Twt A’

Dealing with this is hard™ But I have some ideas 😅