This is awesome! Thanks!
Wondering if you can clarify a bit—what parameters cause a chat to/not to show up in the GUI? Different topics? Different channel names? I have a use for this immediately and am excited to give it a shot!
Wondering if you can clarify a bit—what parameters cause a chat to/not to show up in the GUI? Different topics? Different channel names? I have a use for this immediately and am excited to give it a shot!
For example:
keybase chat send friend1,friend2\
--topic-type=dev\
--topic-name=KEYBASE-SYSOPS\
"server-restart [reason:hot and bothered]"
----
If you're using the JSON api - which makes more sense if you're programming it - take a look at `keybase chat help api` to see some examples of how to structure the JSON going in. Anywhere you see a `channel` object, you can add `topic_type` and `topic_name` to them. Both should be strings.
You said something about violating expectations when you sync PFS'd chat contents, but I don't see why that's relevant unless people were promised otherwise.
There's nothing about the encryption algorithm itself that dictates how data going over it should be handled at the endpoints.
Just let users have a regular mode and an off-the-record mode where nothing is kept. Both PFS protected.