# 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 13
# self = https://watcher.sour.is/conv/hzrblbq
@prologic So, there is an API! This is offtopic for the thread (sorry) but can you link me to its documentation? I'm thinking about creating a single-user barebones "pod", compatible with the mobile app but that manages a single twtxt file.
@darch Great stuff, thanks! That does solve my "publishing" part of the equation, even if it still doesn't work as a client (either web or mobile)…
@darch Great stuff, thanks! That does solve my "publishing" part of the equation, even if it still doesn't work as a client (either web or mobile)…
@marado you are welcome. Yes I also still need a timeline render. F ound some PHP attempt if this on git hub, but nothing that I could get working. Keep me posted about your project 😊
@marado you are welcome. Yes I also still need a timeline render. Found some PHP attempt if this on github, but nothing that I could get working. Keep me posted about your project 😊
@marado I _think_ the main thing that's important if you want to build your own client, publishing tools and host your own twtxt.txt file is to follow some or all of the specs we've documented at dev.twtxt.net. Probably the most important and useful ones are the Metadata, Twt Subject and Twt Hash extensions. For example, having an Avatar and Description in your feed is kind of useful and nice for others 👌 And being able to participate in "threads" by using the Twt Subject and Twt Hash exts is also useful 😅
@marado I _think_ the main thing that's important if you want to build your own client, publishing tools and host your own twtxt.txt file is to follow some or all of the specs we've documented at dev.twtxt.net. Probably the most important and useful ones are the Metadata, Twt Subject and Twt Hash extensions. For example, having an Avatar and Description in your feed is kind of useful and nice for others 👌 And being able to participate in "threads" by using the Twt Subject and Twt Hash exts is also useful 😅
or you could just stand up an instance of yarnd, there's a few folks that use it as a single-user pod 👌 (_probably we'll just support a --single-user option at some point_)
or you could just stand up an instance of yarnd, there's a few folks that use it as a single-user pod 👌 (_probably we'll just support a --single-user option at some point_)
@prologic yes, functionally an yarnd with --single-user is all/exactly what I'm seeking.
Technically I'd then probably still want a port/clone of it into a lighter-weight, easilly hostable alternative (so you can file-drop into any tilde host, or even those FTP-only hostings…), but that's a bridge to cross when I get there…
@prologic yes, functionally an yarnd with --single-user is all/exactly what I'm seeking.
Technically I'd then probably still want a port/clone of it into a lighter-weight, easilly hostable alternative (so you can file-drop into any tilde host, or even those FTP-only hostings…), but that's a bridge to cross when I get there…