# 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 14
# self = https://watcher.sour.is/conv/ej6bbpq
Why do I get Bad request when I try to reply to posts/yarn-treads?
Like this one: https://neotxt.dk/conv/jp2bwta
@darch I get this occasionally on twtxt.net. I don't know why it happens.
This happens because the CSRF token is old and invalid. We need to improve the UX of that error cc @ullarah -- Refreshing normally is the right thing to do here to get a new valid token 👌
This happens because the CSRF token is old and invalid. We need to improve the UX of that error cc @ullarah -- Refreshing normally is the right thing to do here to get a new valid token 👌
@prologic Do you mean to just refresh the page in the browser? Because I have tried it and it does not work. It seem to only happen when I try to replay
So to post this is had to copy/past the twthash manually
@darch what do you mean by replay?
@darch what do you mean by replay?
@prologic i meant "reply"
@darch is it possible you hit the reply button and then come back sometime after and try to type out your reply and hit post?
@darch is it possible you hit the reply button and then come back sometime after and try to type out your reply and hit post?
@prologic maybe, but i doubt that is what happens all the time. Often it keeps the draft text from some other "session" if that makes sense and I have a suspension that this might be part of the problem. Like the hidden (#txthash) messing things up, maybe a JS-issue... CC: @ullarah
@darch I just did some testing here and didn't notice anything immediately obvious. But you _may_ be on to something there... Hmmm 🤔
@darch I just did some testing here and didn't notice anything immediately obvious. But you _may_ be on to something there... Hmmm 🤔