↳
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.
Pagination? Like Yarn uses elsewhere. Or infinite scroll, but from the server side that’s still pagination.
Sure. Possible. Infinite scroll on an SSR isn’t really possible without significant use of JS AFIAK.
Exactly. Every other social network has that feature; I’ve missed it here serveral times already and it looks like I’m not the only one.
We don’t 😀 See philosophical reasons.
I still don’t get the difficulty from a technical point of view I’m afraid. 🤔
It’s a design decision…