Awesome! Thanks for this!

It rely on auto-create. We should ensure this feature is enabled and fallback to a proper create with config otherwise.

I asked around and heard that the auto-create is pretty common. So we probably don't have to bother with adding the fallback.

There is the corner case with the static variable mentioned in the review above.

Instead of using a static variable we maybe could also pass it along the userdata parameter. That's a long line of calls. According to paul:

• _omemo_devicelist_publish_result
• omemo_devicelist_configure
• _omemo_devicelist_configure_submit
• _omemo_devicelist_configure_result
• omemo_devicelist_request
• _omemo_receive_devicelist
• omemo_set_device_list
• _handle_own_device_list
• omemo_devicelist_publish
• _omemo_devicelist_publish_result

omemo_devicelist_request and _handle_own_device_list seem to be not so easy.

The corner cases probably will be quite rare anyways.

The issue with the static boolean could arise in two cases:

• deconnection from a client that already reconfigured it's own device list. Followed by a connection to another account that also have a misconfigured device list.
• running client that has already reconfigured it's own device list. With another client misconfiguring the existing devicelist and removing the running client from the list.
  Each time the effect would be that profanity won't be able to reconfigure correctly the devicelist.