Author here, this is a refactoring of qr-filetransfer, already discussed in the past [0].<p>Here's how it works: qrcp binds a web server to the address of your Wi-Fi network interface on a random port and creates a handler for it. The default handler serves the content and exits the program when the transfer is complete. When used to receive files, qrcp serves an upload page and handles the transfer.<p>The tool prints a QR code that encodes the text:<p><pre><code> http://{address}:{port}/{random_path}
</code></pre>
Most QR apps can detect URLs in decoded text and act accordingly (i.e. open the decoded URL with the default browser), so when the QR code is scanned the content will begin downloading by the mobile browser.<p>To send one or more files (or directories):<p><pre><code> qrcp /path/to/file
# Or
qrcp send /path/to/file
</code></pre>
To receive one or more files:<p><pre><code> qrcp receive --output ~/Downloads
</code></pre>
[0] <a href="https://news.ycombinator.com/item?id=16647977" rel="nofollow">https://news.ycombinator.com/item?id=16647977</a>
This is the feature I'm missing the most from KDE Connect, transferring from Computer to mobile, I ended up using syncthing with a 'send_to_mobile' folder, not the main purpose but... it works.
That is nice and delightfully simple.<p>When I saw the title I thought, that it will transfer a file entirely via continuous QR code scanning. But it would be probably too error prone and too slow, especially without a back channel to signify acks.<p>Maybe such a thing could work between two phones facing each other screens using front cameras. I wonder how fast could it practically get.