Limitations and caveats

Current implementation stores the session state in the browser local storage. This has following implications:

1) your browser must support local storage and have it enabled
2) you can't involve people in the session otherwise than sharing screen with them - people either need to be in the same place (e.g. conference room) or use some screen sharing service
3) you can't create multiple sessions simultanously simultaneously on the same browser/profile - first, you need to finish or discard the previous one   one
4) the relative session are not listed on the dashboard nor on the dropdown lists