Skip to main content
This version is being prepared for release: nothing described here is in the published packages and image yet. The latest release is 0.6.1.

​
Sign-in by a code

Where the channel link does not carry the transaction to the bot, the sign-in has a second path: the page shows a short code, and the user sends it to the bot. For Instagram and Messenger the code is offered automatically; under hop mode it is on the phone’s launch page and disappears as soon as the bot answers. BotName sets the bot’s name. The HTTP channel supports a start by a code for registrations with no owner — see Start by a code.

​
The sign-in page and hop mode

  • The hop pages and the sign-in page show where the question is waiting.
  • Canceling on the sign-in page sends a “declined” receipt into the channel.
  • A third QR code mode, QrMode: UnifiedWithChannels: the shared QR code and the buttons of every channel on the first tab, followed by a tab per channel with its own QR code.
  • Email under hop mode: one page with the address field, or the email right away — see Email under hop mode.
  • Fixes from live runs: the countdown and the live status of the OnWebPage question page, the “Choose another way” button.

​
The standalone server

The standalone server image includes the Redis stores, event publishing to RabbitMQ and MaxMind GeoIP — switched on by configuration keys, with no build of your own; see Quickstart self-hosted.

​
Samples and documentation

​
What to check when you upgrade

  • Email with LoginConfirmation.Mode = OnWebPage: the sign-in email no longer completes the sign-in; it only links the mailbox, and the sign-in page decides. “No” there gives declined_by_user.
  • Some built-in texts are reworded — if you override them, check them against Configuration & customization.