# 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/iemlfpq
prologic
twtxt.net
View Thread
prologic/salty-chat: A rudimentary terminal / command-line based chat system using the salty command-line tool for encrypting and decrypting messages using the saltpack message format and using msgbus as transport - salty-chat - Mills

Thanks to @xuu have incorporated his improvements and rename the repo. This is now a single POSIX Shell script called salty-chat with a bit of a nicer setup. 👌
prologic
twtxt.net
View Thread
prologic/salty-chat: A rudimentary terminal / command-line based chat system using the salty command-line tool for encrypting and decrypting messages using the saltpack message format and using msgbus as transport - salty-chat - Mills

Thanks to @xuu have incorporated his improvements and rename the repo. This is now a single POSIX Shell script called salty-chat with a bit of a nicer setup. 👌
david
netbros.com
View Thread
@prologic why didn’t you use keys (CLI) instead? What’s the difference? Is salty just a wrapper around it?
prologic
twtxt.net
View Thread
@david No salty is not a wrapper around keys at all. salty is just using the same crypto libraries as keys.pub (because you shouldn't invent your own crypto), furthermore the keys CLI itself is actually a command-line client into the keys.pub service or your own instance of (I believe you can run one yourself, though I haven't tried).

salty is just a command-line tool around Saltpack.

salty-chat is a simple (written in Shell) "chat" that uses salty and msgbus
prologic
twtxt.net
View Thread
@david No salty is not a wrapper around keys at all. salty is just using the same crypto libraries as keys.pub (because you shouldn't invent your own crypto), furthermore the keys CLI itself is actually a command-line client into the keys.pub service or your own instance of (I believe you can run one yourself, though I haven't tried).

salty is just a command-line tool around Saltpack.

salty-chat is a simple (written in Shell) "chat" that uses salty and msgbus
david
netbros.com
View Thread
@prologic ah, I see, thanks for the explanation. So salty doesn’t use the key manager and user identities piece. Pretty neat!
prologic
twtxt.net
View Thread
@david No. Your "identity" withsalty is effectively your "Public Key'. salty-chat (for example)'s make-user runs salty-keygen and stores your private key in $HOME/.config/salty/$USER.key or $XDG_CONFIG_HOME/salty/$USER.key -- Then (prompts you) you should publish a piece of JSON to your top-level domain's web server at /.well-known/salty/user.json which is how it looks up your key, endpoint and what "inbox" to post to.
prologic
twtxt.net
View Thread
@david No. Your "identity" withsalty is effectively your "Public Key'. salty-chat (for example)'s make-user runs salty-keygen and stores your private key in $HOME/.config/salty/$USER.key or $XDG_CONFIG_HOME/salty/$USER.key -- Then (prompts you) you should publish a piece of JSON to your top-level domain's web server at /.well-known/salty/user.json which is how it looks up your key, endpoint and what "inbox" to post to.