# 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 6
# self = https://watcher.sour.is/conv/guseeja
@eldersnake Not a bad idea, I thought about this too, since Yarn.social's landing page is s static page though, yeah it would have to be done with some client-side JS 😅
@eldersnake Not a bad idea, I thought about this too, since Yarn.social's landing page is s static page though, yeah it would have to be done with some client-side JS 😅
@prologic Just check it once a day via cronjob and regenerate the page. Or maybe each hour. And also publish the last checked timestamp along with the results.
@lyse Actually that's a great idea! 😅 Why didn't I think of that, the landing page is a static site built with zs and Markdown, so it _would_ be trivial to re-generate the
@lyse Actually that's a great idea! 😅 Why didn't I think of that, the landing page is a static site built with zs and Markdown, so it _would_ be trivial to re-generate the table with some dynamic data 👌
@lyse Actually that's a great idea! 😅 Why didn't I think of that, the landing page is a static site built with zs and Markdown, so it _would_ be trivial to re-generate the table with some dynamic data 👌