Why do I get Bad request
when I try to reply to posts/yarn-treads?
Like this one: https://neotxt.dk/conv/jp2bwta
This happens because the CSRF token is old and invalid. We need to improve the UX of that error cc @ullarah@txt.quisquiliae.com – Refreshing normally is the right thing to do here to get a new valid token 👌
@darch@neotxt.dk what do you mean by replay?
@prologic@twtxt.net i meant “reply”
@darch@neotxt.dk 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@twtxt.net 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@txt.quisquiliae.com
@darch@neotxt.dk I just did some testing here and didn’t notice anything immediately obvious. But you may be on to something there… Hmmm 🤔