# 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 12
# self = https://watcher.sour.is/conv/byjrkua
@lyse What is your working theory for why @maya ‘s posts appear ~40m into the future? 🤔
@lyse What is your working theory for why @maya ‘s posts appear ~40m into the future? 🤔
@fastidious Yeah 🤣 It’s been puzzling me for ages and something I want to fix 😁
@fastidious Yeah 🤣 It’s been puzzling me for ages and something I want to fix 😁
She have just not set a timezome for her feed and her local time is ahead of the rest of us
@darch That’s what I don’t get. If you look at her raw feed it looks like valid RFC3339 with a UTC tz?
@darch That’s what I don’t get. If you look at her raw feed it looks like valid RFC3339 with a UTC tz?
@prologic I didn't experience any future twts from her myself, so not sure. But @movq's theory sounds plausible. Now that I write these lines I think I discovered a bug in tt which throws away future twts. Let me address this quickly.
@prologic Turns out that this is not tt's fault, but the official twtxt client which I'm still relying on has the if created_at > now: raise ValueError("Tweet is from the future") check. So tt just never saw them. Fixed locally.