User Flow

This document covers how a new user would be processed within the application.
First Connection to a server hosting the application code (found by the applications recourceId) is established and the registerUser command is invoked.
It returns the created recourceId and a secret to the connection which registerd the user. After this step the user can already receive messages.
After this you should authenticate the user. This is done by using loginUser with the recourceId and the secret received from registration.
This upgrades the connection and you can now execute commands like createDevice or addDevice which will create or add a device respectively. While a user can receive messages, only devices can be pushed to.
A message for a user will be distributed to all devices authenticated.

devices should subscribe to the users messagestream.

New:

1. The device Tries to register itself (may need a captcha token) registerDevice
2. The server responds with captcha_required error or registerResponse
3. After the user accepted the terms the device registers it with createUser or logs in with loginUser requiring the existing Device to approve.
   In each case the Device will be added to the User and receive messages and be able to send.