# 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 18
# self = https://watcher.sour.is/conv/eql45zq
@prologic @darch I was in the #4ab7fcq conversation sending that reply to you and I got the "Bad Request" error we were talking about.

I pressed the back button on my browser, because I was at https://twtxt.net/post instead of the conversation page. My message was still in the reply box. I copied the text to the clipboard, pressed Ctrl+Shift+R (to reload with a clear cache), and tried to send the message again. Same error. I went to my timeline at the root of the pod, clicked "Reply" on your twt, pasted the message in, and it worked as normal. I'm using LibreWolf 100.0.2, which should be analogous to Firefox 100.0.2
I tried to upload an image from that thread's /conv/ page and I got an alert(): An error occurred uploading your media: 400 Bad Request. The error persisted after a hard reload. Could be related.

I also couldn't post this twt from this conversation's /conv/ page. I had to go back to the timeline.
I was able to upload the image from the timeline. I seem to be stuck in the Bad Request state. I'm unable to post from /conv/ pages, but I can post from the timeline and from Discover. Is there anything I can do while I'm in this state that might help squash this bug? @prologic
Test post from /twt/tbw5boq
It seems to be isolated to the /conv/ page.
Interesting...
Interesting...
@prologic I'm writing up my findings in a Git issue. I want to see if logging out and logging back in fixes it. Before I do that, is there anything else I should test while I'm in this state?
@mckinley I'm gonna look at the route... Hmmm
@mckinley I'm gonna look at the route... Hmmm
Hmmm there's no difference between those two routes 🤔
Hmmm there's no difference between those two routes 🤔
@prologic test
@prologic Here's my full bug report. I hope it can be of use. https://git.mills.io/yarnsocial/yarn/issues/957
@mckinley Thanks! I've been following along and I'm still a bit stumped 😆
@mckinley Thanks! I've been following along and I'm still a bit stumped 😆
I’m not quite sure what is going on either. I’m posting (and on my dev pod) just fine. Using Safari on iOS and FF Nightly on desktop. Also uploaded this…
I should mention that this was all from the /conv/ route.