HAXXX: A crude form of setup message acceptance

README.md

@@ -36,7 +36,7 @@ Here's where we're at right now:
 - [~] Contacts handling
 - [x] Text messages
 - [ ] Multimedia messages
-- [ ] Setup messages
+- [~] Setup messages
 - [ ] Import/Export
 - [ ] Group chats
 - [ ] Geolocation messages
@@ -167,6 +167,26 @@ development. Just run the `telepathy-padfoot` binary as the same user that your
 chat client will be running as. It registers to the DBUS **session bus**, and
 will be picked up next time your chat client scans (which may need a restart).
 
+### Setup messages
+
+If you send an autocrypt setup message while a padfoot connection is up, it will
+notice it and open a channel asking you to reply with a message like:
+
+```
+IMEX: <id> nnnn-nnnn-nnnn-nnnn-nnnn-nnnn-nnnn-nnnn-nnnn
+```
+
+The ID is the delta-generated message ID, while the rest is the setup code. No
+whitespace!
+
+This bit is still extremely janky; it should instead be a magic channel type or
+action button of some kind. It is, however, functional.
+
+Delta wants us to enable the "Send copy to self" option in settings, but that
+isn't exposed in padfoot yet, so messages you send from padfoot won't appear in
+other clients. Messages from other clients won't appear either, because messages
+from yourself are mostly ingnored by padfoot. Still, it's progress.
+
 ### Autogenerated telepathy DBUS bindings
 
 It makes use of the `dbus-codegen-rust` crate to convert the