Edit: just use the built in QR code generator with a string in this format.
WIFI:T:WPA;S:$SSID;P:$PASSWORD
51–60 of 347 posts
Edit: just use the built in QR code generator with a string in this format.
WIFI:T:WPA;S:$SSID;P:$PASSWORD
For a moment I thought: What a great attack vector. Collect WiFi passwords from around the globe.
qrencode -t utf8 'WIFI:T:WPA;S:network;P:password;;'
Did you type this in from memory?!
>There are some standards -- de facto and otherwise -- already in use. This wiki attempts to catalog some possible standards for encoding various types of information, and suggest a standard action associated to them.
[1]: https://github.com/zxing/zxing/wiki/Barcode-Contents#wi-fi-n...
On ios it works fine with the default camera app, but what about android? I'd guess support varies depending on vendor?
Seems to be using the same format as https://qifi.org/ , which lists supported devices, but of course due to the lack of native QR on most Android devices it's per-app rather than per-phone.
I got a QR code like this on the wall with the SSID and the password written on the paper as well as a NFC tag with the wifi credentials between the paper and the wall. I think nobody ever has scanned the QR code.
Asking as a person who understands the fundamentals of all of the technologies involved but is horrified by much of what goes on in the minds of today's web developers and designers, what motivates the decision to make this repo use make, docker, yarn, npx, nginx, react, and jest rather than a bit of static HTML and css and something like qrjs2.js or VanillaQR.js with a simple canvas or datauri update in onInput?
There are chances out there, unbelievable.
Asking as a person who understands the fundamentals of all of the technologies involved but is horrified by much of what goes on in the minds of today's web developers and designers, what motivates the decision to make this repo use make, docker, yarn, npx, nginx, react, and jest rather than a bit of static HTML and css and something like qrjs2.js or VanillaQR.js with a simple canvas or datauri update in onInput?
Here is why I like using CRA for some projects:
1. Live reload. This comes for free with CRA. Makes dev work easy.
2. As easy as installing a component and getting started. And they logically fit in the code flow. Native import libraries, you have to write the JavaScript and point em to your divs and dom and initialize em.
3. Let’s say in the future, I want to reuse the code logic in a different app, I can just take the js and element as one unified component and move it across.
Tbh, for an app like this, after doing a production build (npm run build), I don’t think it’d make a radical difference in performance with raw html or react. Might just be dev preference, and ease of use.
I am sure that this is not what this site is for. But... For a moment I thought: What a great attack vector. Collect WiFi passwords from around the globe.