↳
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 Re RFC 3339 timestamps, if I understand you correctly, I think it’s extremely unlikely for someone to repost a Twt (an edit) within the same second (at least not humanly possible). In any case, I’ve only validated the ideas so far in isolation, the algorithm(s) need to be built, feature gated, measured, understood and finally put in place with some UX (I like @ullarah@txt.quisquiliae.com’s gugestion)