# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 26
# self = https://watcher.sour.is/conv/x7b3vsa
@bender @prologic I've went further down - sometimes to seek something I've read and caught my attention at the time, othertimes to reference old threads in new ones. In this context, nothing is "too old".
@marado @bender I'd rather we figure out a way to improve the UX (_if we can_) without introducing a "forever visible" or "a rdbms". I'd like to see something like (_for example_) "Click here to load older replies..." or something like this π€
@marado @bender I'd rather we figure out a way to improve the UX (_if we can_) without introducing a "forever visible" or "a rdbms". I'd like to see something like (_for example_) "Click here to load older replies..." or something like this π€
@marado @bender I'd rather we figure out a way to improve the UX (_if we can_) without introducing a "forever visible" or "a rdbms". I'd like to see something like (_for example_) "Click here to load older replies..." or something like this π€
@marado @bender I'd rather we figure out a way to improve the UX (_if we can_) without introducing a "forever visible" or "a rdbms". I'd like to see something like (_for example_) "Click here to load older replies..." or something like this π€
@prologic how about not a βclick to loadβ, but if I get into a conversation, the related twt are fetched on demand, without interaction?
@bender fetched on demand, implies some kind of client-side JavaScript; so probably not.
However, there is another way that we talked on IRC last night...
Which again leads to searching and indexing the archive π
@bender fetched on demand, implies some kind of client-side JavaScript; so probably not.
However, there is another way that we talked on IRC last night...
Which again leads to searching and indexing the archive π
@bender fetched on demand, implies some kind of client-side JavaScript; so probably not.
However, there is another way that we talked on IRC last night...
Which again leads to searching and indexing the archive π
@bender fetched on demand, implies some kind of client-side JavaScript; so probably not.
However, there is another way that we talked on IRC last night...
Which again leads to searching and indexing the archive π
@prologic you can do a reasoanable lazy loading type thing without JavaScript
@abucci Without Javascript you say? Hmmm? π€ How? (unless we're tlaking about the same thing in different ways...)
@abucci Without Javascript you say? Hmmm? π€ How? (unless we're tlaking about the same thing in different ways...)
@abucci Aithout JacaSceipt you say? Hmmm? π€
@abucci Without Javascript you say? Hmmm? π€ How? (unless we're tlaking about the same thing in different ways...)
@abucci Without Javascript you say? Hmmm? π€ How? (unless we're tlaking about the same thing in different ways...)
@abucci is that like some sort of pagination?
@eldersnake that's the only thing I can think of -- which we do on the backend anyway for our server-side-rendered web app (SSR)
@eldersnake that's the only thing I can think of -- which we do on the backend anyway for our server-side-rendered web app (SSR)
@eldersnake that's the only thing I can think of -- which we do on the backend anyway for our server-side-rendered web app (SSR)
@eldersnake that's the only thing I can think of -- which we do on the backend anyway for our server-side-rendered web app (SSR)
@prologic well, I lied a bit. You can with small js glue fragments in "onclick' events on buttons (for instance). You don't need libraries or frameworks, just a short fragment that's easy to understand and debug, functioning as an event handler.
However, you can fake it with the checkbox trick, where you send the client much more data than you reveal at first and use CSS/HTML to incrementally reveal it. You can also do the meta-refresh thing combined with server-side page rendering to pull in new content periodically.