Kelana Logo
Ghost Drop - Serverless P2P Browser File Sharing

GHOST DROP

Transfer Code
------
DROP FILE TO TRANSFER
Universal formats supported: ZIP, MP4, PDF, Docs, and more.
0%
filename.zip
0.00 MB
Streaming live chunks...
Backup Advisory: Both browser tabs must remain open during the transfer. If either tab is closed or your internet disconnects mid-stream, transmission halts immediately since no intermediary server holds your data.
Device-Dependent Limits: Transmission speeds depend solely on your local Wi-Fi or internet bandwidth between the two devices. There are zero cloud bandwidth limits.
Zero Cloud Storage: Data flows straight from device to device through an encrypted WebRTC SCTP pipeline. No servers ever see, record, or buffer your files.
Encrypted Tunnel: All packets are automatically shielded by DTLS (Datagram Transport Layer Security) end-to-end cryptography, preventing packet sniffing across public Wi-Fi networks.

1. Introduction to Decentralized In-Browser Data Relays

GHOST DROP is a serverless, peer-to-peer (P2P) binary payload transfer engine operating natively inside modern web browsers. Developed to circumvent the privacy risks, speed throttles, file size ceilings, and surveillance vulnerabilities inherent to centralized cloud storage providers, GHOST DROP constructs an encrypted point-to-point data bridge directly between two computing devices. By coordinating session handshakes over lightweight signaling infrastructure and establishing direct WebRTC DataChannel connections, files of arbitrary formats stream through local device memory without ever touching, buffering on, or staging across intermediate web servers.

2. Interface Architecture & Component Nomenclature

Every operational interface module, button, and visual indicator corresponds to a distinct network state or pipeline stage:

  • Top Role Allocator (tabSenderMode & tabReceiverMode): Bilateral state toggle designating whether the local browser initializes as the transmission origin (Sender) or the destination listener (Receiver). This control locks into a fixed state once an active session handshake completes to prevent accidental socket disconnection.
  • Sender Transfer Code (mySenderCode): A high-entropy, ephemeral 6-digit numeric token generated in local memory that uniquely addresses the sender's PeerJS registration point on the public STUN network.
  • Target Code Receiver Console (targetCodeInput): Symmetric numeric input field enabling the receiver to declare the remote peer destination code manually, automatically triggering handshake dialing upon entry of the sixth digit.
  • Optical Telemetry Transceiver (btnSenderAction & btnReceiverAction): Dual-mode modal trigger exposing an upscaled QR code on the sending terminal and activating an accelerated 25 FPS camera scanner on the receiving terminal to eliminate manual entry errors.
  • Kinematic Tunnel Icon (dropIconContainer): Real-time connection status beacon. A crossed gray arrow denotes an idle or severed link; an emerald green glowing arrow confirms an authenticated, active WebRTC DataChannel.
  • Spacious Transfer Dropzone (dropzoneBox): Interactive drag-and-drop ingestion viewport allowing zero-friction file selection, bound directly to an in-memory FileReader ArrayBuffer stream.
  • Stream Visualizer HUD (dropzoneStreamView): Real-time telemetry dashboard presenting an uncompressed percentage readout, file metadata, exact byte volume, and a linear progress bar calibrated to outgoing or incoming memory chunk buffers.
  • Session Termination Gate (disconnectConfirmModal): State verification modal preventing accidental link termination, ensuring active packet transfers are not discarded without explicit user confirmation.

3. Technical Operator Tutorial

To execute a seamless, zero-cloud peer-to-peer GHOST DROP between two machines, execute the following operational sequence:

  1. Establish Role Hierarchy: Open the application on both endpoints. Designate the transmitting device as Sender and the target device as Receiver using the top header switch.
  2. Complete Out-of-Band Pairing: The Sender clicks QR Code to project the visual pairing token. The Receiver clicks Scan QR, grants camera access, and frames the screen. Alternatively, the Receiver can manually type the Sender's 6-digit code into the target field.
  3. Verify DTLS Cryptographic Lock: Upon SDP (Session Description Protocol) handshake completion, both terminals signal connection readiness: the slashed icon transforms into an emerald green arrow, the role buttons lock, and the action button shifts to a crimson Disconnect trigger.
  4. Stream Binary Payload: On the Sender terminal, drag and drop any file into the central dropzone, or click inside to launch the OS file picker. The binary payload is automatically sliced into 64 KB memory chunks and dispatched sequentially across the WebRTC SCTP pipeline.
  5. Receive & Save: The Receiver terminal reflects incoming packet chunks on its progress HUD. When all bytes are accounted for, an internal Blob is assembled in volatile memory and automatically downloaded to local disk storage.
  6. Clean Socket Disconnection: Once verified, tap Disconnect on either device to safely sever the WebRTC data tunnel, reset both interfaces to idle mode, and release allocated memory buffers.

4. Historical Evolution of Peer-to-Peer Data Architectures

The distribution of digital files has cycled through centralized and decentralized paradigms over five decades. In the 1970s and 1980s, file exchange relied on physical "sneakernets" (magnetic tape, floppy disks) and early GHOST DROP Protocol (FTP) client-server architectures over ARPANET. The late 1990s witnessed the rise of peer-to-peer networking with Napster (1999), which paired centralized indexing with direct peer audio streaming, and Gnutella (2000), which implemented fully decentralized query routing.

In 2001, Bram Cohen formulated the BitTorrent protocol, introducing simultaneous multi-source file chunking and swarming algorithms that transformed internet data distribution. However, these systems required standalone desktop clients, port-forwarding configurations, and torrent trackers. In May 2011, the World Wide Web Consortium (W3C) and Internet Engineering Task Force (IETF) standardized WebRTC (Web Real-Time Communication). GHOST DROP represents the modern maturation of this lineage: transforming web browsers into self-contained, zero-install peer-to-peer data relays capable of streaming high-throughput binary files across networks without third-party desktop software.

5. International Standards, Network Protocols & Regulatory Compliance

GHOST DROP operates in strict compliance with globally recognized networking standards, cryptographic baselines, and data privacy frameworks:

  • IETF RFC 8831 & RFC 8261 (WebRTC Data Channels over SCTP): Data transport executes across Stream Control Transmission Protocol (SCTP) encapsulated within Datagram Transport Layer Security (DTLS). This standard ensures message-oriented reliability, selective retransmission, and packet-level congestion avoidance without socket starvation.
  • IETF RFC 8489 (Session Traversal Utilities for NAT - STUN): Interactive Connectivity Establishment (ICE) traversal resolves private IP addresses to public network endpoints across Symmetric and Full-Cone NAT routers using standardized STUN binding discovery requests.
  • ISO/IEC 18004 (Information Technology — QR Code Symbology): Optical pairing complies with international two-dimensional matrix barcode specifications, employing Reed-Solomon Error Correction (Level M) to support reliable camera acquisition under varied screen reflections and ambient angles.
  • EU General Data Protection Regulation (GDPR - Article 5 & Article 25): Exemplifies complete compliance with Data Minimization and Privacy by Design. Because no database, file cache, or server-side telemetry pipeline exists, transmitted files are never processed, staged, or retained on external computing resources, neutralizing third-party subpoena and data breach vectors.

6. Core Architectural Advantages

  • Complete Data Sovereignty: Files stream directly from sender RAM to receiver RAM over encrypted network paths. No corporate cloud provider holds, inspects, or logs your data assets.
  • Unconstrained Bandwidth & File Size: Unlike commercial cloud drives that impose daily bandwidth throttling or upload limits, transfer speeds are bounded solely by the physical local Wi-Fi or broadband capacity of the participating endpoints.
  • Universal Cross-Platform Operation: Bridges incompatible operating systems without friction, functioning as a platform-agnostic alternative to Apple AirDrop, Google Quick Share, or proprietary USB drivers across iOS, Android, macOS, Windows, and Linux.
  • Zero-Install Ephemeral Footprint: Runs entirely inside standard browser tabs without requiring native application store downloads, administrative privileges, user registration, or telephone number verification.

7. Mathematical Formulations & Transmission Physics

Packet throughput, transmission delays, and binary chunking across the GHOST DROP engine adhere to fundamental communication theory models:

A. Shannon-Hartley Channel Capacity Theorem

The theoretical upper bound on error-free data transmission capacity C (in bits per second) across an analog or digital network channel with bandwidth B (in Hertz) and signal-to-noise ratio SNR is governed by:

C = B × log2(1 + SNR)

In local Wi-Fi environments (e.g., 802.11ax with 160 MHz channel width and high SNR), channel capacity expands to gigabit speeds, allowing local WebRTC peer streams to dramatically outperform cloud-routed uploads.

B. SCTP Packet Chunking Formulation

To prevent buffer bloat and avoid browser tab memory starvation, files of total byte length S_file are partitioned into uniform discrete chunks of size C_size = 65,536 bytes (64 KB). The total chunk count N is calculated as:

N = ⌈ S_file / C_size ⌉ = ⌈ S_file / 65536 ⌉

Each chunk is dispatched sequentially across the reliable DataChannel pipeline, with execution pauses managed via recursive tick offsets to keep the browser UI responsive during intense transfer workloads.

C. Transmission Latency & Transfer Time Formula

The total wall-clock duration T_transfer required to deliver a complete binary artifact over effective throughput R_effective with round-trip network latency RTT is modeled as:

T_transfer = (S_file / R_effective) + (RTT / 2) + T_reassembly

Where T_reassembly represents the client-side Blob instantiation time when compiling binary chunk arrays into final downloadable file structures.

D. Dynamic Progress Scalar

The real-time percentage index displayed on the HUD terminal at any given byte offset B_current is determined by integer truncation:

Progress(%) = min( 100, ⌊ (B_current / S_file) × 100 ⌋ )

8. Frequently Asked Questions (FAQ)

Q: Can third parties intercept or inspect my files during transfer?

A: No. All WebRTC DataChannel connections are secured using mandatory Datagram Transport Layer Security (DTLS) with modern cipher suites. Data packets are encrypted directly between the two peer devices, preventing packet sniffing even across open public Wi-Fi networks.

Q: Why do role switches lock when a session is active?

A: WebRTC establishes an asymmetrical peer-to-peer session: one node acts as the offerer and the other as the answerer. Locking the role switch while connected prevents accidental pipeline teardowns and transmission errors mid-stream.

Q: What happens if a browser tab is accidentally minimized or closed?

A: Because files stream live between device memories without intermediate cloud buffering, closing either browser tab severs the connection and halts transfer immediately. For large files, keep both browser tabs active and visible until completion.

Q: Does GHOST DROP impose any file size limits?

A: There are no arbitrary software caps on file size. However, because the receiving browser reconstructs files in volatile device RAM before saving to disk, transfers are physically bounded by the available memory of the receiving device.

9. Closing Remarks & Open-Source Community Support

GHOST DROP was created to prove that personal computers and mobile devices can communicate directly without corporate intermediaries, surveillance backdoors, or subscription paywalls. If this decentralized utility simplifies your workflow, speeds up cross-device sharing, or helps safeguard your personal data, consider supporting our ongoing development: share the platform with colleagues, star the open-source repository, contribute technical improvements, or support our engineering team. Own your data, connect directly, and let peer-to-peer technology power your digital freedom!

Sender Pairing QR

Scan with your camera or Receiver scanner:

Scan Sender Screen

Align sender's QR code within the frame:

Disconnect Transmission?

Are you sure you want to terminate this connection? Any ongoing transfer will be canceled.

All Tools Directory 118+ Free Apps