# 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/4uj5wzq
Heya all 👋 (_long night for me, didn't get to sleep till ~2am 😢_); Woke up this morning to a lot of chatter about Twt Hashes and Reply-ID and Reply-To ala Email messages (_RFC2822 I believe_).
I don't think we should change how we chain Twts together just for the off chance someone decides to go edit a single Twt a while back in their feed. This is okay IHMO, slightly confusing albeit, but "okay". I agree with @lyse in https://twtxt.net/twt/xdqytia that keeping backwards compatibility here is important but also keeping simplicity too...
Heya all 👋 (_long night for me, didn't get to sleep till ~2am 😢_); Woke up this morning to a lot of chatter about Twt Hashes and Reply-ID and Reply-To ala Email messages (_RFC2822 I believe_).
I don't think we should change how we chain Twts together just for the off chance someone decides to go edit a single Twt a while back in their feed. This is okay IHMO, slightly confusing albeit, but "okay". I agree with @lyse in https://twtxt.net/twt/xdqytia that keeping backwards compatibility here is important but also keeping simplicity too...
... I _think_ I've said this a few times before, the cryptographic properties of Twt Hashes that we use (_based on blake2b + base32 encoding_) allows us to mirror Twts across pods, clients, etc seamlessly as well as Search engines like Yarns (https://search.twtxt.net) too. They can be used as cache keys (_conversations_) and so on. The moment you go to Message-ID and Reply-To-ID(s) you lose this and. these ID(s) can just be "made up" and have no meaning beyond just a number.
... I _think_ I've said this a few times before, the cryptographic properties of Twt Hashes that we use (_based on blake2b + base32 encoding_) allows us to mirror Twts across pods, clients, etc seamlessly as well as Search engines like Yarns (https://search.twtxt.net) too. They can be used as cache keys (_conversations_) and so on. The moment you go to Message-ID and Reply-To-ID(s) you lose this and. these ID(s) can just be "made up" and have no meaning beyond just a number.
@prologic @lyse it wasn’t that much of a chatter (not a lot, for sure). 😂
@prologic fair enough. I'm always in favour of KISS.