# 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 195626 # self = https://watcher.sour.is?offset=193194 # next = https://watcher.sour.is?offset=193294 # prev = https://watcher.sour.is?offset=193094
config.json like this:n
{
"host": "localhost:31212",
"protocols": ["http"]
}
twtxt.net) determines the canonical url of the instance in generated feed url metadata as well as every hash of every post made on the instance internally, i added this error message to make sure people don't accidentally set up their instance on localhost :p for testing i set it to localhost:31212 and protocols to ["http"], it's a recent addition that could definitely do with documenting in the getting started section
Uma pilha de revistas e autocolantes SHIFTER
Uma pilha de revistas e autocolantes SHIFTER
Uma pilha de revistas e autocolantes SHIFTER
Privacy-concerned duck in a creek
[2025/09/11 12:56:01.816] ⇒ please set config.host when trying to run "bbycll". How to bypass that tiny hurdle?
<details> aren't rendered. firstly they're not actually markdown, and secondly they style weird — details are forced onto a new line as a block element but you can't make the <summary> inline because it is inside <details>, and making <details> inline will also indent everything inside it
<details> need to have the open attribute set in order to expand it, so I cannot just define some custom CSS rules to do that in my browser.<details><details>