# 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 1
# self = https://watcher.sour.is/conv/4o45tpa
prologic-twtxt-atom-feed
feeds.twtxt.net
View Thread
(#k5dgh7q) @bender probably no more expensive than keyword based filtering to be honest. Right now it's O(n) complexity. It would probably be wo ...
@bender probably no more expensive than keyword based filtering to be honest. Right now it’s O(n) complexity. It would probably be worth caching “filtered per-user views” (including the timeline) some of which we don’t do right now. It would probably save a few % points of cpu utilisation of a larger pod. ⌘ Read more