# 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 3
# self = https://watcher.sour.is/conv/x62snya
@jdtron I'm wondering whether we should split out the lextwt parser library that @xuu wrote that yarnd uses for parsing. If we split this out into a library (_actually you can already import it_) then both twet and yarnd can share the same parser - thus reducing efforts and sharing the same behaviour and bug fixes 👌 -- I _believe_ even @lyse has managed to import lextwt via a C-extension with his Python written tt client too 👌
@jdtron I'm wondering whether we should split out the lextwt parser library that @xuu wrote that yarnd uses for parsing. If we split this out into a library (_actually you can already import it_) then both twet and yarnd can share the same parser - thus reducing efforts and sharing the same behaviour and bug fixes 👌 -- I _believe_ even @lyse has managed to import lextwt via a C-extension with his Python written tt client too 👌
@prologic Yup, I managed to make an older version of lextwt available to Python as a shared library using cgo. I should update the binding to the current lextwt version, a few things have changed in the meantime. Unfortunately, that briged lextwt is not being used at the moment, tt currently still uses my own Python parser.