# 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 11
# self = https://watcher.sour.is/conv/f73asbq
Definitely something going on with replies. This one was replying to the wrong twt and even when I got clever and pasted the right hash it didn't work.
@mckinley Yeah, all this JS and HTMX garbage messes up a lot of things which used to work better in the earlier days.
HTMX is fine! You can add dynamic sections with a simple endpoint. It is better that JavaScript.
HTMX is fine! You can add dynamic sections with a simple endpoint. It is better that JavaScript.
@twtxt.andros.dev it might be fine, but not here. It just causes more issues than fixes.
@mckinley Ahh. I _think_ this is some kind of weird caching issue at my edge! 😱
@mckinley Ahh. I _think_ this is some kind of weird caching issue at my edge! 😱
I need to understand how the caching is at play here at the edge. I hit CTRL+R on @mckinley's OP to get the _right_ subject reply after poking at the underlying HTML elements on the page.
I need to understand how the caching is at play here at the edge. I hit CTRL+R on @mckinley's OP to get the _right_ subject reply after poking at the underlying HTML elements on the page.
The cache is only suppose to be for 120s though, but I reckon the caching layer is just stupid? 🤔 (_and maybe buggy_)?
The cache is only suppose to be for 120s though, but I reckon the caching layer is just stupid? 🤔 (_and maybe buggy_)?