↳
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 The ideas I have in mind to deal wit this are basically to get good at “detecting edits” in the first place at ingestion time. I’ve played around with a few “text similarity” algorithms and I think we can reasonably (with high confidence) say that Twt A’ was an edit of Twt A – We would cache and archive them both, but in the User Interface collapse them and show the Twt A’ (with a visual indication/link that it was an edit of Twt A)