Andrej Shadura
Andrej Shadura
Thanks for the idea, I will consider it when I work on this project next time!
I believe your file should work when I finish my current refactoring effort: #33.

Not at the moment, but I can try again and see if I have anything.
I’m curious what happens if you try az Aztec code from this project: https://github.com/pbock/ticket-parser  I suppose it should be in the same format...
Right, easier said than done, I’m unable to transform this photo to be able to scan from it 😄

My understanding is that the most important information is indeed stored on Google’s servers, and it *not* in the JWT. I’m not sure Google provides API access to the data...
This is a great idea, @ligi could you please have a look at this as well if you find time? Thanks!
This would probably autosolved if #248 were implemented.