# 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 8
# self = https://watcher.sour.is/conv/najpaha
So all that silly testing with "Test 1", "Test 2" was me and @ullarah trying to figure out a weird observable behaviour we were seeing between our pods with this new WebSub feature. Turns out @ullarah's server running his Pod was out by 18s (clock skew) and was treating my individual twts in near-real-time as being in the future (this is a feature).
What do y'all think about tolerating up to say 30s of clock skew? 🤔
So all that silly testing with "Test 1", "Test 2" was me and @ullarah trying to figure out a weird observable behaviour we were seeing between our pods with this new WebSub feature. Turns out @ullarah's server running his Pod was out by 18s (clock skew) and was treating my individual twts in near-real-time as being in the future (this is a feature).
What do y'all think about tolerating up to say 30s of clock skew? 🤔
@prologic is that in regards of detecting post in the future? If not, where are we to tolerate those 30 seconds? Either way, I think 30 seconds is not much but will be curious to know what others have to say.
@david Yes it's the "detecting posts in the future". Remember the trouble we had with Maya and her inability to correctly set the timezone on her PC and spit out correct timestamps on her feed? 😅
@david Yes it's the "detecting posts in the future". Remember the trouble we had with Maya and her inability to correctly set the timezone on her PC and spit out correct timestamps on her feed? 😅
@prologic 30 seconds is reasonable. Even a little more would be fine, I think. It's only really annoying when someone's time is set so far into the future that it's effectively a "sticky" post at the top of the Discover feed for a while.
@mckinley Agreed 👌 And yes that was the annoying thing about _some_ (albeit small in number) folks who seemed to not be capable of understanding timezones 😆 So we "fixed" that! (A little too well apparently 🤣)
@mckinley Agreed 👌 And yes that was the annoying thing about _some_ (albeit small in number) folks who seemed to not be capable of understanding timezones 😆 So we "fixed" that! (A little too well apparently 🤣)