# 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 5
# self = https://watcher.sour.is/conv/hiu6boa
lyse
lyse.isobeef.org
View Thread
@darch @prologic As briefly mentioned in https://twtxt.net/twt/23pnlzq, I still rely on the official twtxt client (that I patched up on a few ends) for downloading and managing subscriptions. So my config contains:


[following]
darch = https://twtxt.net/user/darch/twtxt.txt
darch@neotxt = https://neotxt.dk/user/darch/twtxt.txt


My own client tt only acts as a viewer into the twtxt reference implemenation's cache and config. When replying to a thread, tt adds in all the participants of the thread as mentions. Since darch wrote from his account on neotxt.txt and not the one on twtxt.net my client of course added a mention with the second nick from the config above. I forgot to remove my chosen nick suffix and that's how it all came together. Ideally, the mapping would be reversed to use the URL as key, but that change would require even more temporary patching and I want to get rid of the original implementation eventually anyways.
prologic
twtxt.net
View Thread
open to building a new client? As a Go library and Cli?
prologic
twtxt.net
View Thread
open to building a new client? As a Go library and Cli?
prologic
twtxt.net
View Thread
open to building a new client? As a Go library and Cli?
prologic
twtxt.net
View Thread
open to building a new client? As a Go library and Cli?