# 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 9
# self = https://watcher.sour.is/conv/lmg6spq
@prologic Maybe her -00:00 timezones throws off a parser? I think I tried this edge case when coming up with the twt hash spec, but can't tell anymore for sure. At least I've written this (2020-12-13T07:45:23-00:00 → 2020-12-13T07:45:23Z) explicitly down. The thing is, I just documented Go's behavior to make sure I don't break anything. Maybe add a test similar to this one and see what's happening. :-?
@lyse Nah, I think her timezone is simply off. When you go back to the beginning of her feed, there’s a few posts about her script being broken. 🥴
@lyse Nah, I think her timezone is simply off. When you go back to the beginning of her feed, there’s a few posts about her script being broken. 🥴
@lyse Nah, I think her timezone is simply off. When you go back to the beginning of her feed, there’s a few posts about her script being broken. 🥴
@lyse @movq Oh 🤦‍♂️ I’ve tried to encourage her to fix it but hmmm 🤔
@lyse @movq Oh 🤦‍♂️ I’ve tried to encourage her to fix it but hmmm 🤔
@prologic She's probably not following anybody of us.
@lyse I do believe I’ve emailed her about it once 👌
@lyse I do believe I’ve emailed her about it once 👌