# 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/xvlyzfa
I have noticed that twtxt timestamps differ. For example:
* @prologic (and I assume any Yarn user)
2024-09-18T13:16:17Z
* @lyse
2024-09-17T21:15:00+02:00
* @aelaraji (and @movq, and me)
2024-09-18T05:43:13+00:00
So, which is right, or best?*
I have noticed that twtxt timestamps differ. For example:
* @prologic (and I assume any Yarn user)
2024-09-18T13:16:17Z
* @lyse
2024-09-17T21:15:00+02:00
* @aelaraji (and @movq, and me)
2024-09-18T05:43:13+00:00
So, which is right, or best?*
@movq alright, fair, and interesting. I was expecting them to be all the same (format wise), but it doesn't matter, for sure, as it works just fine. Thanks!
@movq alright, fair, and interesting. I was expecting them to be all the same (format wise), but it doesn't matter, for sure, as it works just fine. Thanks!
@quark @movq Yep, they're all RFC3339. Obviously, +02:00 and +01:00 are best, because I use them! :-P In all seriousness, Z might be the best timezone, as it is shortest. And regarding privacy, it leaks the least information about the user's rough location. But of course, one can just look at the activity and narrow down plausible regions, so that's a weak argument.