# 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 8
# self = https://watcher.sour.is/conv/yyuo34q
bender
twtxt.net
View Thread
@zvava I am getting [2025/09/11 12:56:01.816] ⇒ please set config.host when trying to run "bbycll". How to bypass that tiny hurdle?
zvava
twtxt.net
View Thread
@bender as the host (eg 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
zvava
twtxt.net
View Thread
@bender i also recently discovered there was a bug causing new users to initialize wrong leading to their posts not being saved :p ..and made breaking changes to how the config and database files are stored so um, make sure to clear your local tree before updating!
zvava
twtxt.net
View Thread
@bender ty for attempting to test, though, it means a lot! lmk if u find any more silly things i need to clarify or fix :> be prepared for everything breaking during beta :p
bender
twtxt.net
View Thread
Woot, thank you! Using a config.json like this:


n
{
  "host": "localhost:31212",
  "protocols": ["http"]
}


Indeed did the trick! I know it isn't production ready, but I wanted to see with my own eyes, locally, how did it look. :-) I like where you are going! It is looking very nice, and polished. Can't wait for an alpha, beta, and release!
bender
twtxt.net
View Thread
On the configuration topic, the example at the repo reads like this:

bender
twtxt.net
View Thread
Hmm, twtxt Yarn is misbehaving. Can't even edit, nor delete. Oh well.
quark
ferengi.one
View Thread
Adding too this. The configuration example at the repository reads:


{
	"nick": "Example",
	"description": "alice's twtxt instance!",
	"host": "twtxt.example.com",
	"admin": "alice"
}


Would it make more sense changing nick to instance_name or similar? Usually nick is reserved for users, like here, quark. Right? Also, is host the same FQDN to be used while proxying traffic to the application? That is, using the above configuration, it's Caddy configuration would be:


twtxt.example.com {
	encode
	reverse_proxy :31212
}


Is that correct?