Decimen Optical Transfer utilizes fountain coding to create an endless stream of QR frames, treating frame loss as normal rather than exceptional. The sender splits files into source blocks, while the receiver collects frames to reconstruct the data. This architecture supports joining mid-stream and recovering files from distinct frames without retransmission requests. The system relies on WebAssembly for decoding, ensuring compatibility across browsers including Safari, which lacks native BarcodeDetector support. The default configuration targets a transmission rate of 24 FPS with a payload of 1,465 bytes per frame. While the reference configuration is designed as a proof of concept, the underlying mathematics use IEEE-754 operations to ensure consistency across different JavaScript engines. The documentation highlights that sensitive use requires additional encryption and authentication, as visual observation alone does not guarantee security. This makes it suitable for air-gap research and coding education, though practical throughput depends on camera capabilities and environmental factors like exposure and refresh rates.
Questions about Decimen Optical Transfer
What is Decimen Optical Transfer?
Decimen Optical Transfer is an open-source browser application that transfers files between devices using animated QR codes displayed on a screen and captured by a camera. It operates entirely in the browser through WebAssembly and uses fountain codes to convert files into a stream of encoded QR frames. The receiver can reconstruct the original file from any sufficient subset of frames without requiring retransmission, making it ideal for network-free data exchange.
Who is Decimen Optical Transfer best suited for?
The tool is designed for environments where pairing, accounts, or cables are inconvenient, such as air-gap research, offline transfers, or coding education. It handles missed or degraded frames caused by camera motion or display timing by treating them as normal operating conditions rather than problems. This makes it particularly useful for study of visible, one-way data paths between devices without a direct network connection.
How does the fountain-coding mechanism work step by step?
The process begins when the browser divides the local file into fixed-size source blocks, which are then encoded by XORing a deterministic pseudorandom subset of blocks. Self-describing packets become a continuous animated QR stream that the receiver captures via the camera. Any sufficient set of distinct frames allows the receiver to peel the original blocks out once it has enough information to reconstruct the file.
What are the specific technical specifications and payload limits?
The reference configuration operates at a default transmission rate of 24 FPS with a payload of 1,465 B per QR frame. Users can select demo payloads ranging from 128 KB to 2 MB, though the 128 KB/s result belongs to a larger parent experiment using denser frames and an error-corrected color channel. The system uses ZXing compiled to WebAssembly to cover browsers that do not ship BarcodeDetector, including Safari.
What technical features ensure data integrity during transmission?
The system includes features such as hash verification, self-describing frame headers, and tolerance for missed or degraded frames caused by camera motion or display timing. It operates entirely in the browser through WebAssembly, utilizing local file LT encoder, QR generator, display, and camera components. Parallel capture dispatches video frames to workers, where busy workers simply drop frames that the fountain layer absorbs.
How does the system handle network constraints and hardware limitations?
The tool is intended for local, network-free data exchange and does not require Wi-Fi, Bluetooth, or internet access. It splits the stream across multiple QR codes to optimize performance, though this can lead to challenges like phone thermal throttling. The system is designed to handle the inevitable misses from motion blur, autofocus, exposure, and display refresh timing without needing retransmission.
What are the licensing and development status of the project?
The project is publicly available on GitHub and operates under an MIT License. It is described as a reference configuration designed for a comfortable proof of concept rather than a production-grade solution. The browser-based nature means it requires no native application installation, making it accessible for immediate experimentation.
What are the primary use cases for this technology?
The tool is intended for small payloads when pairing, accounts, or platform-specific apps are inconvenient. It is particularly useful for study of visible, one-way data paths between devices without a direct network connection. The system allows users to move small payloads efficiently in scenarios where traditional methods are impractical.
How does the recovery algorithm calculate frame requirements?
The system uses a robust soliton distribution for its fountain coding, where the receiver can join mid-stream and collect frames in any order. It requires approximately K × 1.15 distinct frames for K source blocks to achieve typical recovery targets. The deterministic math specified IEEE-754 operations keep V8 and JavaScriptCore in agreement when building the soliton distribution.
What specific data structures are used for frame management?
The tool includes a compact header that carries the session ID, sequence number, block geometry, file length, and hash. It uses parallel capture where video frames are dispatched to workers, and busy workers simply drop frames. The fountain layer absorbs these losses, ensuring the system remains resilient to interruptions during the capture process.
How does the system handle frame loss during capture?
The system is designed to handle missed frames caused by motion blur, autofocus, exposure, and display refresh timing. It treats these misses as normal operating conditions rather than errors that require correction. This approach allows the receiver to reconstruct the original file even when some frames are lost during the capture process.
What are the key operational requirements for using the tool?
The tool is intended for local, network-free data exchange and operates entirely in the browser through WebAssembly. It includes features such as hash verification and self-describing frame headers to ensure data integrity. The system is designed to work without requiring retransmission, making it efficient for quick file transfers.
What are the main advantages of using this system?
The project is publicly available on GitHub and is intended for local, network-free data exchange. It is designed to work without requiring Wi-Fi, Bluetooth, or internet access. The system is particularly useful for study of visible, one-way data paths between devices without a direct network connection.
What is the official website of Decimen Optical Transfer?
The official website of Decimen Optical Transfer is decimen-optical-transfer.online.
How is Decimen Optical Transfer rated on Trustburn?
On Trustburn, Decimen Optical Transfer has a rating of 3.6 out of 5 based on 5 reviews.
AI-generated from reviews on this page. Verify anything important with the company directly.
The browser-based pipeline using WebAssembly workers is a strong technical choice. It allows parallel capture and handles frame loss gracefully through the fountain layer. This makes it a reliable option for offline data transfer without requiring native applications.
While the optical transfer mechanism is interesting, the documentation notes that optical is not synonymous with secure. It requires encryption and authentication for production use, but specific implementation details for these controls are not clearly spelled out in the main text. This ambiguity leaves users guessing about safety.
Decimen offers a refreshing approach to file transfer by using light. The fountain coding architecture means the receiver never needs to ask for retransmission, making it resilient against motion blur or focus issues. Since it runs in the browser with WebAssembly, there is no need to install native apps. This is ideal for air-gap environments where network connectivity is limited. The self-describing frames carry all necessary session data, allowing recovery even if frames are dropped. It is a clever, minimalist solution for moving small payloads without cables or pairing.
I was immediately intrigued by the concept of Decimen Optical Transfer. The idea of moving files through light using fountain-coded QR frames is genuinely clever. It treats missed frames as normal operating conditions rather than errors, which is a smart engineering choice. Reading about how the browser divides the file into source blocks and encodes them with XOR operations shows a solid technical foundation. The fact that the receiver does not need to ask for retransmission is impressive. I appreciate that this is a browser-based solution using WebAssembly, meaning no native app download is required. The documentation clearly explains the soliton distribution and how distinct frames reconstruct the original file. It feels like a well-thought-out experiment for air-gap research or offline transfers. The performance specs suggest it works well within browser constraints. It is a neat way to move small payloads when pairing accounts or cables is inconvenient. The open-source nature under MIT License adds to its appeal for tech-savvy users who want to inspect the code.
News
No news yet. This is where the business shares its own updates and press.
Photos
No photos yet. Photos shared by reviewers will show up here.
Widgets
Get the widget for your site →About Decimen Optical Transfer
Decimen Optical Transfer is an open-source browser application that enables file transfer between devices using animated QR codes displayed on a screen and captured by a camera. It uses fountain codes to convert files into a stream of encoded QR frames, allowing the receiver to reconstruct the original file from any sufficient subset of frames without requiring retransmission. The tool operates entirely in the browser through WebAssembly and includes features such as hash verification, self-describing frame headers, and tolerance for missed or degraded frames caused by camera motion or display timing. The project is publicly available on GitHub and is intended for local, network-free data exchange.