# 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 15
# self = https://watcher.sour.is/conv/xsnmvda
@adi This looks interesting! Thanks for sharing.
I didn't really get it 🤷♂️
I didn't really get it 🤷♂️
@prologic If I'm understanding it properly, it allows you to start with existing server-side code in whichever language you like, have it output specialized HTML templates of the views you want your frontend to have, and then those views are rendered server-side and sent to the web browser. What's interesting is you get a frontend experience much like other single-page web app frameworks, without many of the headaches those cause. A lot of frontend frameworks have the web browser do this rendering work, and require back-and-forth communication with the server to move data around, which then forces you into the world of serializing your server-side app objects to something like JSON, marshalling them over to the frontend (and back) with all the associated networking code complexity, issues, bugs, etc etc.
Svelte also compiles server-side and is pretty popular right now.
@abucci Hmmm okay, I'll have another closer look 🤔
@abucci Hmmm okay, I'll have another closer look 🤔
@abucci It doesn't have to output specialized templates, it works with normal full server side pages. It extracts the main element's content and replaces it in the current page. Of course, it could be optimized for sending only fragments.
Basically, just add it over any server side rendered web site and it works.