# 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 15
# self = https://watcher.sour.is/conv/whbni2a
@lukem Like a factor of x3? 🤣
@lukem Like a factor of x3? 🤣
@lukem Like a factor of x3? 🤣
@prologic more importantly, there are apparently two methods of setting expiry time on Redis keys and only one of them uses miliseconds. I'm still digging into it as I handle Redis via server drivers and it's not super obvious. But damn, do I feel so stupid sometimes.
@prologic more importantly, there are apparently two methods of setting expiry time on Redis keys and only one of them uses miliseconds. I'm still digging into it as I handle Redis via server drivers and it's not super obvious. But damn, do I feel so stupid sometimes.
@lukem So let me get this straight, there is a mix of Redis methods that accept either Milliseconds or Seconds? 😲 I guess consistency in API design is strong with Redis too 🤣 (_spekaing of which, we need to make our own API consistent! 😂_)_
@lukem So let me get this straight, there is a mix of Redis methods that accept either Milliseconds or Seconds? 😲 I guess consistency in API design is strong with Redis too 🤣 (_spekaing of which, we need to make our own API consistent! 😂_)_
@lukem So let me get this straight, there is a mix of Redis methods that accept either Milliseconds or Seconds? 😲 I guess consistency in API design is strong with Redis too 🤣 (_spekaing of which, we need to make our own API consistent! 😂_)_
@prologic also, thank you for serving as my rubber duck for this bug. Given the complexity of the matter and the fact I'm completely outside of my comfort zone it was super helpful.
@prologic also, thank you for serving as my rubber duck for this bug. Given the complexity of the matter and the fact I'm completely outside of my comfort zone it was super helpful.
@lukem Hah! No worries! 😀 To be honest I haven't used Redis all that much really, but for various reasons ended up writing my own KV Store 🤣 Every time I have found myself reading the Redis command reference I couldn't help but think to myself "man this is complicated, why are there so many freak'n commands?!"
@lukem Hah! No worries! 😀 To be honest I haven't used Redis all that much really, but for various reasons ended up writing my own KV Store 🤣 Every time I have found myself reading the Redis command reference I couldn't help but think to myself "man this is complicated, why are there so many freak'n commands?!"
@lukem Hah! No worries! 😀 To be honest I haven't used Redis all that much really, but for various reasons ended up writing my own KV Store 🤣 Every time I have found myself reading the Redis command reference I couldn't help but think to myself "man this is complicated, why are there so many freak'n commands?!"