(v0.1.0) The Camera update

Changelog: What is new, camera improvements, more and less buttons, fixes

  • Added What is new section (it never gets old!)
  • Added option to choose camera on scanning qr-code (man that was hard!)
  • Made camera output good quality image, should make qr code scanning a breeze (too big angles still suck tho)

  • Added a nice overlay frame for scanning qr’s

  • Added delete button to list of sessions, delete all you like
  • Renamed “Additional check” into “Followup check” and made it less appealing to press (it is destructive!)
  • Renamed “Save” into “Save name”

  • Added button to export attendance on finished session screen

  • Reduced qr code redundancy (made qr code bigger, who needs redundancy anyway)
  • Fixed a loop-login bug for Safari users
  • Fixed big-cookie problem (Who new that big cookies are bad for you?)
  • Timer is now restarted if you reenter empty session
  • Now we use Moscow timezone by default
  • Masked big scary error when pressing “back” button after login

Details

What is new

We are doing a lot – but nobody can notice this unless we explain it. Thanks jekyll!

Camera

Before, when you tried scanning qr-code app randomly picked a camera. People with 4 cameras only one of which was okay went on strike! Now while scanning qr-code using some incredibly dark magic you can change a camera that you are using for the optimal result.

Browser before gave us a small video resolution, but we made it output maximum full-hd video, should make things better for now. Big angles still distort image too much for it to readable by default. Also bad contrast sometimes renders code unreadable. We are working on improvements in that area.

We’ve never thought that cookies could pose such a problem.

There was a parameter that was connected with security. Earlier you could set it to use a stricter mode (named lax), but otherwise it would be None. Google disliked it – they decided that everyone should set None explitly, otherwise it would be lax (stricter than None).

Unfortunately, if you own IPhone 5 or 6, your IOS version does not allow you to update Safari enough to acommodate these changes and your browser would not recognise None as a valid value resulting in a infinite loop of logging in. We decided to use a user-agent detection system to change cookie headers for these users.

Recently, our project crashed =) Asp.net cookies became ridiculosly big (over 10Kb). What is worse, in http1 there is no header compression, which surely wasnt helpful. We quickly reduced cookie size and placed special apache flags to make sure that this never happens again.