# 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/e5qz2gq
@apex that sounds interesting. Is you client offline first?
@apex by offline-first I mean that you can use the client locally on the phone without an account on a yarn pod, similar to how the original twtxt client works. If this is the case how will it post/upload to a self-hosted twtxt.txt-file?
It doesn’t make sense to me to make a client offline first—which in my mind it means online is simply optional—when it comes to Yarn/twtxt. There is no use for it offline.
Right now Yarn works on fetching. Increase the fetching interval to 8 hours and it gets close. A client for it can be made more asynchronous, yes, like an mail client, but offline first? 🤯
@david I'm not sure where I picked up the term "offline-first", but how @apex describes it above is what I had in mind.
@apex a Yarn pod is a local twtxt file, with a client in front, just you what you are working on. Other than the extensions added (subjects, multilines, hashes, metadata) Yarn is, still, twtxt. The fact we are here chatting about it is proof of that.