For program-to-program talking, use the "dev" channel, in a topic of your choice. (By default --topic-type=chat and changing it to dev keeps it out of the GUI)
For example:
keybase chat send friend1,friend2\
--topic-type=dev\
--topic-name=KEYBASE-SYSOPS\
"server-restart [reason:hot and bothered]"
I'll never see this in the GUI but you and your friend1 and friend2, can access the messages through the chat API. The topic-name can be whatever you want, and it allows you to structure messages into channels.
----
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.
Why is non-PFS the default? You wrote that somewhere in the documentation.
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.
For example:
I'll never see this in the GUI but you and your friend1 and friend2, can access the messages through the chat API. The topic-name can be whatever you want, and it allows you to structure messages into channels.----
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.