Open burdges opened 3 years ago
Note that uos protocol is pretty much wrapped in Raptor, as sketched in https://github.com/maciejhirsz/uos/pull/8. Don't just merge that though, the actual implemented uos protocol does not really match neither the master here nor what I sketched in PR, by now we actually need a proper analysis to figure out what barnacles have grown on this ship. I'll certainly do it myself once the core Signer is more or less finalized.
We've discussed using erasure codes in https://github.com/paritytech/parity-signer/issues/457 and https://github.com/paritytech/parity-signer/issues/320#issuecomment-546734733 probably a rateless code like Raptorq although one should work out the overhead.
And TXQR maybe works https://hub.packtpub.com/introducing-txqr-data-transfer-via-animated-qr-codes/ ref. https://github.com/w3f/research-internal/issues/143
If we used erasure codes then we'd simply stream QR codes until the decoder captured them all, but actually cameras can take so long to capture a dense QR code that this might prove tricky. I'd think one wants a protocol bespoke to streaming video honestly, so like QR codes but maybe lower resolution and faster.