QR-Code-generator VS Pion WebRTC

The funny thing is that no-one AFAICT has realized that the same content can be encoded in different-looking QR codes. Beside the obvious (different error-correction levels), the content itself can be changed while maintaining its semantic meaning (e.g. "https://example.com/foo", "HTTPS://EXAMPLE.COM/foo", or "HtTpS://eXaMpLe.CoM/foo" are all semantically identical) and even the QR encoding itself can be tweaked (e.g. by changing the version and mask, see the demo on https://www.nayuki.io/page/qr-code-generator-library). Each combination would yield a different-looking QR code that would encode the same meaning, and it could therefore allow the diffusion models even greater freedom.

I'm sure somebody will get to this soon.

Make a hidden Veracrypt vault on cold computer. Inside the Veracrypt vault save Keepassxc vaults. Store your seeds inside the Keepassxc vaults. For a paper backup, encrypt your seeds using an offline AES256/512 text encryptor/decryptor. Encode the encrypted text using an offline qrcode generator. Print out the qrcode. Test recovery using a dummy wallet. Be sure you can scan and decrypt. Bonus: Laser etch the qrcodes on metal plates. Make a multi-factor recovery vault, in case you forget your passwords. Shimar's secret sharing scheme is a useful tool for making your recovery vault. Never store your seed unencrypted anywhere, ever. Never input your seed on an online computer, ever. Always protect your seeds with something you know (password), something you have (vaults and keyfiles). Do not upload your vault to the cloud. Keep backups in multiple locations. Necessary tools: Cold computer: Any old computer will do. Just physically disable network access. Veracrypt: https://www.veracrypt.fr/code/VeraCrypt/ KeepassXC: https://keepassxc.org/ Cross-platform, open-source text string encryptor. https://github.com/a3diti/aes256-offline/ Cross-platform, open source QR code generators: https://kazuhikoarase.github.io/qrcode-generator/js/demo/ https://github.com/amanuel/JS-HTML5-QRCode-Generator https://github.com/nayuki/QR-Code-generator Shamir's Secret Sharing: https://github.com/paritytech/banana\_split

Necessary tools: Cold computer: Any old computer will do. Just disable network access. Veracrypt: https://www.veracrypt.fr/code/VeraCrypt/ KeepassXC: https://keepassxc.org/ Cross-platform, open-source text string encryptor. https://github.com/a3diti/aes256-offline/ Cross-platform, open source QR code generators: https://kazuhikoarase.github.io/qrcode-generator/js/demo/ https://github.com/amanuel/JS-HTML5-QRCode-Generator https://github.com/nayuki/QR-Code-generator Cross-platform, open-source text string encryptor. https://github.com/a3diti/aes256-offline/ Shamir's Secret Sharing: https://github.com/paritytech/banana\_split

I probably know this only because back in time I wrote a QR code generator in JavaScript [1] which was also one of such libraries reviewed by Nayuki [2], and as I haven't actually implemented a decoder my knowledge stops there. Sorry :-)

[1] https://github.com/lifthrasiir/qr.js

[2] https://www.nayuki.io/page/qr-code-generator-library

I guess it helps to understand how to generate a QR code: https://www.nayuki.io/page/qr-code-generator-library (see also the references at the end)

Good luck. ;-)

i think i found what i was looking for

I am really excited about https://github.com/sepfy/libpeer. It has examples ready for ESP32 etc....

When working on KVS I wasn't familiar with the embedded space at all. I saw 'heavyweight' embedded where you were running on Linux. Then you had RTOS/No OS at all. I wasn't prepared for these devices at all. If we can make WebRTC work in the embedded space I think it will really accelerate what developers are able to build!

Remotely driven cars, security cameras, robots in hospitals that bring iPads to infectious patients etc... Creative people are building amazing things. The WebRTC/video space needs to work harder and support them :)

-----

I love how diverse the WebRTC space is now. Outside of this implementation you have plenty of other options!

* https://github.com/shinyoshiaki/werift-webrtc (Typescript)

* https://github.com/pion/webrtc (Golang)

* https://github.com/webrtc-rs/webrtc (Rust)

* https://github.com/algesten/str0m (Rust)

* hhttps://github.com/sepfy/libpeer (C/Embedded)

* https://webrtc.googlesource.com/src/ (C++)

* https://github.com/sipsorcery-org/sipsorcery (C#)

* https://github.com/paullouisageneau/libdatachannel (C++)

* https://github.com/elixir-webrtc (Elixir)

* https://github.com/aiortc/aiortc (Python)

* GStreamer’s webrtcbin (C)

See https://github.com/sipsorcery/webrtc-echoes for examples of some running against each other.

I have worked four jobs related to https://github.com/pion/webrtc and one for https://webrtcforthecurious.com

Two companies used Pion. The other two were just using the protocol (WebRTC)

In my experience Go has been relatively approachable for people that are good at PHP. It has a great standard library and a pretty solid ecosystem, though frameworks aren’t as popular in Go. There are some well regarded libraries for things like WebRTC via https://github.com/pion/webrtc WebSicket via https://github.com/nhooyr/websocket

Don't try to make RTC yourself, it looks easy, but in fact, it's a really hard problem to solve. Use https://pion.ly/ it's a pretty solid package they also have a discord/slack channel with a lot of helpful people there.

Maybe you can reuse some of this code: https://github.com/pion/webrtc/blob/master/examples/data-channels/main.go