zlacker

>>nicbou+(OP)
Static PDF or text is a good protection against Murphys law! Having done forms like this I have learned that the hard way. If you want to save state on the server like you mention e.g. QR code, you need to save the form as a PDF or a readable text file and not only as data that is rendered by some frontend framework.

This means you can have multiple people digitally sign or even fill it out, then they can sign the text representation which is easier than a digitally signed PDF or json. You need this because when you update the backend and frontend between logins and there is always somekind of mismatch that will happen. This is especially hard when you have non linear form entries or optional parts like the C/O part in this form, there is always something that slips through the crack in regression testing.

Last time it happend to us someone had upgraded the front end calendar month chooser. It was well tested, but that ment another optional date picker was updated and testing did not happen there. Then organizational and technical Murphys law struck meaning complete data loss for people affected by that.

>>emj+V5
> you need to save the form as a PDF or a readable text file

Why?

In this case, the data will live for a few weeks at most. The goal would be a QR code that contains the data as a hash: https://forms.berlin/#[form data]. This is to avoid storing or seeing any user data.

I was also considering a P2P solution with WebRTC. This would let you transmit your form without the server seeing the data. You'd just need to both visit a URL at the same time.

The idea is that I can't store private information, and the Bürgeramt can't install any new software.