v1.15.1

The Chrome Web Store update follows separately, after the store's review. Until it is approved, the store still installs 1.15.0; the files below are this exact build.

A first run that starts where you are

Half of the people who install the extension never open it, and of those who
do, many stop at the first screen. This release is mostly about those first
two minutes.

• The extension opens itself after installing. The welcome page that opens
  on install asks the extension to show its window, and it unfolds from the
  toolbar — so you see where it lives instead of hunting behind the puzzle
  piece. If the window closes, Open the extension on the page brings it
  back. This is the one message the extension accepts from a web page, and only
  from authenticator.sh (externally_connectable); it answers only whether the
  window opened.
• Scan the QR code on this page, at the top of the first screen. Most people
  open the extension while a website is showing them a QR code: one click now
  reads it from the tab and adds the account. The tab is captured only when
  you press the button.
• Turning on 2FA right now — the commonest case — is first in the list, and
  its steps end in the scan itself, with No QR code? Type the key instead
  beside it. Before, the same scan was two screens further on.
• A site asks for a code, but I don't have one — a link under the choices,
  for anyone sent here by a sign-in screen: where that code comes from, what to
  do when the app that had it is gone, and how to link this extension once the
  site shows a new QR code.
• No camera? On the Google Authenticator path, using a photo of the QR code
  is now a full-size button next to the camera, not a line among the steps.

Clearer when something goes wrong

• Camera blocked: the scan page tells apart a camera blocked for the page,
  a camera prompt that was closed, a camera blocked by the operating system and
  a camera another app is using — and shows the steps for each one, with a
  picture of where the camera icon is in the address bar.
• Typing a key: instead of "Must be Base32", the form says what is wrong —
  a 6-digit code pasted instead of the key, a key cut short, characters a key
  cannot contain — and points at the field. A name left empty beside an issuer
  is no longer an error: the issuer becomes the name.
• Scanning: "No QR code on this page" says to open the page with the code
  in this tab; a QR code that is not an authenticator setup code says so,
  rather than "Invalid QR code format". Where Chrome does not let the extension
  read the tab — it was not opened from its icon on that page, as with the
  window the welcome page opens or a side panel left open — it says to open it
  from the icon there, instead of blaming the page.

Also new

• New accounts go to the top of the list, where you are about to read their
  code. An import keeps the order of its file, above the accounts already here,
  and a Google Authenticator export split over several codes keeps its own
  order across them; nothing already in the list moves.
• Banners at the top of Settings or above the accounts are now set by our
  server — what they say, where they stand and what they lead to (the cloud
  backup, Pro, password protection, or a page on authenticator.sh or the Web
  Store). Closing one hides that banner for good.
• A bell in the header for notes from us — a new feature, a reminder to
  set a password, cloud backup. A red dot means something new; opening the
  bell marks it read, and the cross on a note removes it for good. The bell is
  there only when there is something in it. Our server decides who gets which
  note, from the same facts the daily check-in already carries (language,
  country, number of accounts, whether a password is set, whether Pro is on);
  the extension leaves out a note whose button could not work here — a
  password prompt when a password is already set, say.
• The Pro screen closes by itself when Pro reaches this browser while it is
  open — a key entered on another of your browsers, a purchase finished in
  another tab — and our server no longer starts a purchase for a browser that
  already has Pro.

What the extension now sends

The check-in described in 1.14.0 and 1.15.0 gains these, and nothing else:

• Banners and notes behind the bell: that one was shown, clicked or
  closed — its id, what it does and where it stands — in place of the cloud
  backup offer's two events; and that the bell was opened, with how many notes
  it held and how many of them were new.
• The welcome page: whether it asked the extension to open, and whether it
  did. The window it opens reports its first showing marked as such, apart
  from the first time you open the extension yourself.
• The first screen: the two new ways on it (the page scan and the
  "a site asks for a code" link) are reported like the others, as a kind; and
  a refused camera as one of four kinds instead of one.

Never an account's name, issuer, secret or the site it is for. The full list
is in the README under "What is sent to our server".

No new permissions. Still no host permissions and no content scripts.