[–] [S] 1 point 21 hours ago* (last edited 20 hours ago)

Thank you! That is actually a very good use case and it should work well for it. Let me know if you run into any problems. The clipboard mode idea sounds interesting too. How do you imagine it would work?

In the cli you can already do something like this to send the clipboard contents:

wl-paste | blastqr

the command might be something different for your system though. wl-paste is the wayland version

  • source
  • parent
  • context
  • [–] [S] 18 points 1 day ago* (last edited 1 day ago) (2 children)

    For those asking about RGB, there are a few reasons why QR codes work better for now:

    • Black and white still reads fine in bad lighting or on cheap cameras. Phones are very optimized for scanning QRs so it's more reliable and less error prone.
    • Video compression, colors shifting with white balance, screen type, all of those make it harder to tell colors apart so you need more aggressive error correction. The real gain ends up smaller than it sounds.

    You can already transfer entire (small) programs and media with blastQR btw! Feel free to try and report back. The limit is around 4 GB files but that would take ages.

    That said, there is a project called libcimbar that is improving and does work with colors: https://github.com/sz3/libcimbar

  • source
  • parent
  • context
  • [–] [S] 7 points 2 days ago

    Yes, over the years I've tried many solutions. The latest popular one being Decimen and others mentioned in the readme.

    Since it seems you are interested in the field I'd be very happy if you tried it and told me how it compares to the rest. blastQR is still a work in progress so any feedback would be very helpful!

    A web UI is also possible. I'm not working on it right now but it's something the project should support in the future.

  • source
  • parent
  • context
  • [–] [S] 14 points 2 days ago* (last edited 2 days ago)

    You bring up great points!

    Here are some benchmarks including videos (Note that these are best case conditions but should be achievable): https://codeberg.org/blast/blastqr#real-world-benchmarks

    Most of the testing I did with my now 7 years old Galaxy S10e. It only scans at 30FPS but it can handle 6 codes at once which is a pretty decent 420 kB/s. During testing on the iPhone 17 which can scan at 60 or 120fps I think the CPU did not become the bottleneck until around 8 codes at more than 90fps. That is something I still need to test and document more thoroughly though.

    I do use standard QR codes. By default Version 40 which can store almost 3 KB. It is configurable in the app's settings.

    Regarding color, libcimbar (https://github.com/sz3/libcimbar) is a project that does exactly that although the speeds are not quite as high yet. Additionally, one of the cpu optimizations in blastQR (and qr scanners in general) is to drop color so that each frame that gets copied in memory is smaller. It makes a difference when you're processing at high fps.

  • source
  • parent
  • context
  • [–] [S] 10 points 2 days ago (1 child)

    The app is limited to 6 right now but I'll work on increasing it! The CLI tool does allows up to 12. Make sure you use Ghostty or Kitty for high frame rates if you do decide to try it.

    A lot of phones cap the camera preview at 30fps actually so 60fps is quite good already. From the devices I tested only the iPhone let me select 60,120,240. You can see some benchmarks here: https://codeberg.org/blast/blastqr#real-world-benchmarks I don't think you are missing out on performance if you can scan at 60fps. I recall at 120 the cpu was starting to be the bottleneck but I'll have to do some more testing to confirm.

  • source
  • parent
  • context
  • [–] [S] 18 points 2 days ago* (last edited 21 hours ago) (1 child)

    Some of the use cases I thought about:

    • Regular file transfers: It works well as long as the files are not too big. I use it often between my phone and laptop.
    • Sensitive information: You can transfer files without relying on cloud services or network infrastructure. There's a password encryption feature for that. If you don't enable that someone could decode the information from the QR codes.
    • Broadcast on a large screen so multiple devices can receive data without requiring an internet connection during internet outage/government internet crackdown.
    • Air-gapped systems: Transfer files to and from devices that are not connected to a network.

    Hopefully people will find new and interesting use cases for it too.

    EDIT: I'm adding use cases mentioned by users in this wiki page: https://codeberg.org/blast/blastqr/wiki/Interesting-use-cases

  • source
  • parent
  • context
  •  

    https://codeberg.org/blast/blastqr

    Hello! I've been working on blastQR for a couple of years now and I thought this community might find it useful. Feel free to try it and ask me anything!

    blastQR is a fully open-source file transfer app and protocol that works completely offline. You can even use it in airplane mode. Data is transferred through sequences of QR codes displayed on a sender device and scanned by a receiver device's camera. It uses RaptorQ codes so the receiver can recover the file from any sufficiently large subset of frames.

    Note that although I have made use of AI as a coding assistant I do not consider this to be a vibe-coded app and I do plan to continue improving it and supporting it in the future.

    See video of blastQR in action: https://github.com/user-attachments/assets/038a2567-70c8-47c8-b165-dea858d1aef3

    Here are some of the key features:

    • Works fully offline: No internet, Wi-Fi, Bluetooth or servers. Your data stays offline.
    • One-to-many distribution: Share the same file with multiple devices simultaneously using a single blastQR broadcast.
    • Cross-platform: Android, iOS, macOS, Linux and Windows, plus a command-line tool that can send from a terminal, even over SSH.
    • Password encryption: You can optionally encrypt files with an auto-generated password or a custom one.
    • Media compression: The app supports lossy image compression and video transcoding for quicker transfers.
    • Multiple codes on screen: Shows multiple QR codes at once for higher speed. With 8 codes at 60 fps, transfers peak at around 1.4 MB/s.
    • Send multiple files in one go: They're zipped into one transfer and unpacked into separate files on the receiver.
    • Sound feedback: The receiver plays a short tone when it has the whole file, and the sender stops automatically when it hears it.
    • Start scanning at any point: No need to catch every code, just keep the camera on the screen until it's done. Blurry or missed codes don't matter.
    • Regular QR scanner: You can also scan normal QR codes and save them.
    • Open protocol that other apps can implement
    • Built-in file manager

    I'm trying to build a small community around the project so it can be improved and maintained and so it can reach more people in the future.

    Downloads for all platforms can be found here: https://codeberg.org/blast/blastqr/releases/latest

    view more: next ›