# 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/5nflr3a
@felixp7 That's correct. The backing twtxt.txt file (_it has a name that matches the username on the pod, e.g: felixp.txt_) is completely unaffected. At _some_ point the backend will have to be _taught_ how to rotate your primary feed and any other feeds you manage, but that's a problem for months down the track (_again for performance reasons_). But as I said above they are no longer in the cache, but the full feed is still downloadable/consumable.
@felixp7 That's correct. The backing twtxt.txt file (_it has a name that matches the username on the pod, e.g: felixp.txt_) is completely unaffected. At _some_ point the backend will have to be _taught_ how to rotate your primary feed and any other feeds you manage, but that's a problem for months down the track (_again for performance reasons_). But as I said above they are no longer in the cache, but the full feed is still downloadable/consumable.
@felixp7 That's correct. The backing twtxt.txt file (_it has a name that matches the username on the pod, e.g: felixp.txt_) is completely unaffected. At _some_ point the backend will have to be _taught_ how to rotate your primary feed and any other feeds you manage, but that's a problem for months down the track (_again for performance reasons_). But as I said above they are no longer in the cache, but the full feed is still downloadable/consumable.
@prologic I can't really argue with performance implications but I'm curious of one thing. Is the limit of 10 days / 150 items adjustable in any way? I can see why it matters for a crowded instance like the one we're on but what about a single-user self-hosted pod?
@prologic I can't really argue with performance implications but I'm curious of one thing. Is the limit of 10 days / 150 items adjustable in any way? I can see why it matters for a crowded instance like the one we're on but what about a single-user self-hosted pod?
@lukem Yes it is configurable, and for a single-user Pod with closed-registrations you _might_ want to increase these configuration values.
@lukem Yes it is configurable, and for a single-user Pod with closed-registrations you _might_ want to increase these configuration values.
@lukem Yes it is configurable, and for a single-user Pod with closed-registrations you _might_ want to increase these configuration values.