# 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 3
# self = https://watcher.sour.is/conv/c5tzt7a
Hi @prologic, question regarding responsible use of twtxt.net's services. How much is "too intensive" an use of its endpoints? For eg, an "every minute" fetch of a twt feed is considered OK? (I honestly have no idea about the default frequency of communication between pods and all that...)
@marado Hey ! 👋 Good question! Right now the default fetch interval is 5m and I _believe_ there is a hard-coded minimum of 1m:


$ yarnd --help 2>&1 | grep interval
      --fetch-interval string         cache fetch interval (how often to update feeds) in cron syntax (https://pkg.go.dev/github.com/robfig/cron) (default "@every 5m")


However, Pods actually also utilise WebSub between each other to subscribe to each other's feeds. So fetches _can_ be near real-time without having to have an aggressive fetch interval.

We should have promoted the WebSub feature in the recent v0.15.x release but I forgot to 😅

Add websub to your "Operational Features" in the Web UI or --enable-feature websub until we do:


$ yarnd --help 2>&1 | grep feature
      --enable-feature feature        enable the named feature


Also, thanks for your PR! 🙏
@marado Hey ! 👋 Good question! Right now the default fetch interval is 5m and I _believe_ there is a hard-coded minimum of 1m:


$ yarnd --help 2>&1 | grep interval
      --fetch-interval string         cache fetch interval (how often to update feeds) in cron syntax (https://pkg.go.dev/github.com/robfig/cron) (default "@every 5m")


However, Pods actually also utilise WebSub between each other to subscribe to each other's feeds. So fetches _can_ be near real-time without having to have an aggressive fetch interval.

We should have promoted the WebSub feature in the recent v0.15.x release but I forgot to 😅

Add websub to your "Operational Features" in the Web UI or --enable-feature websub until we do:


$ yarnd --help 2>&1 | grep feature
      --enable-feature feature        enable the named feature


Also, thanks for your PR! 🙏