# 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/dy3n2cq
Today's discovery: Iris a Serverless text-based forum for tilde-likes. I still haven't posted anything out there yet, but I'm in love with it already. Let's see what we find out next... *rubbing hands*
@skinshafi Oh! interesting hmmm 🤔
@skinshafi Oh! interesting hmmm 🤔
@skinshafi If you liked that, wait till you find BBJ.
@skinshafi Cool!

> Iris leans heavily on convention. Iris' security and message authentication is provided by filesystem permissions and message hashing.
@skinshafi Cool!

> Iris leans heavily on convention. Iris' security and message authentication is provided by filesystem permissions and message hashing.
LOL the rest of it appears undocumented 🤦‍♂️

Messages

Message Hash

Bad Hashes

Edit Chain

Deleted Messages

Topic List

Replies

License

GPLv2
LOL the rest of it appears undocumented 🤦‍♂️

Messages

Message Hash

Bad Hashes

Edit Chain

Deleted Messages

Topic List

Replies

License

GPLv2
@prologic there is a bit more here: https://github.com/Calamitous/iris/blob/master/README.md#technical-bits. Of course, you could take a peek at the .rb file itself: https://github.com/Calamitous/iris/blob/master/iris.rb :-P
Worth noting that this is a local "forum". BBJ uses an SQLite database.
@bender Thanks! Also very interesting rid bits here 🤣

> The author, parent hash, timestamp, and message values go into the hash. (see Message Hash for details)
@bender Thanks! Also very interesting rid bits here 🤣

> The author, parent hash, timestamp, and message values go into the hash. (see Message Hash for details)
Also interesting:

> edit_hash: When a message is edited, a new message is created-- this field holds the hash of the modified message. The client follows the chain of edit hashes to end up at the final, edited message to display. This lets us keep an "undo" history (not yet implemented) and is a marker so the client can display a marker that the message has been edited.
Also interesting:

> edit_hash: When a message is edited, a new message is created-- this field holds the hash of the modified message. The client follows the chain of edit hashes to end up at the final, edited message to display. This lets us keep an "undo" history (not yet implemented) and is a marker so the client can display a marker that the message has been edited.
@prologic @bender Sorry lads! I've just now noticed the whole conversation... reading through right away