Building Prizrak: How a Developer Created a Federated Messenger That Masks All Traffic as Legitimate HTTPS
A developer has built Prizrak, a federated messenger that uses end-to-end encryption and makes all traffic, including voice and video calls, appear as ordinary HTTPS connections on the wire.
The project began because existing messengers could not be configured to remove three persistent problems: a central point that can be shut down, mandatory phone number registration, and traffic that remains identifiable even when encrypted. Prizrak uses identifiers in the form name:domain, OpenPGP long-term keys for identity, X3DH and Double Ratchet for forward secrecy, and ChaCha20-Poly1305 for encryption. Federation occurs between independent homeservers that locate each other automatically.
Transport designed to resist DPI
The developer discovered that perfect encryption is useless if the first bytes of a packet reveal the protocol. Standard WebRTC calls expose the STUN magic cookie 0x2112A442 and DTLS record type 22. The solution was to stop imitating HTTPS and instead become it: clients perform genuine TLS 1.3 handshakes to real domains and present a hidden token only after the channel is encrypted. Servers listen on multiple stable ports including 443, 8801, 993 and others, silently ignoring occupied ones. Clients start at port 443 and discover a working port automatically.
Key management and multi-device support
Long-term OpenPGP keys serve as identity passports verified via QR code and sign ephemeral X25519 prekeys. Each device receives its own identity key signed by the account root. Messages are encrypted separately for every device of the recipient. Revoking a device simply stops delivering envelopes to it. The design accepts O(participants × devices) encryption cost and plans to adopt MLS (RFC 9420) for very large groups.
Resilient delivery through storage nodes
When homeservers cannot reach each other directly, messages travel through a network of storage nodes. Each node stores opaque blobs addressed by HKDF-derived identifiers. The system replicates data across four nodes using a placement model taken from Ceph RADOS, including rendezvous hashing, Merkle reconciliation, and anti-entropy. Delivery acknowledgments are the only source of truth; nodes delete blobs only after receiving a signed ACK.
Native media stack and careful buffer sizing
Calls use a fully native media stack on Android with Camera2, MediaCodec, AudioRecord and Opus. A custom address-mapping service replaces public STUN to avoid detectable signatures. After switching to direct P2P paths, video frames were being truncated because the receive buffer was only 2048 bytes. Raising the buffer to 65536 bytes, adding proper fragmentation, and implementing PLI-based recovery eliminated artifacts. Bitrate is now controlled by queue length rather than observed loss.
Ringback tones and call-state machine
Users complained that calls lacked ringback tones. The developer added a full state machine that reports presence after an offer is sent, distinguishes “subscriber unavailable,” “busy,” and “no answer” conditions, and plays 425 Hz tones with familiar cadences. The same work exposed several signaling bugs that had previously gone unnoticed.
Built-in two-hop VPN
The stealth transport is reused for a two-hop VPN. The first hop sees the user’s IP but not the destination; the exit hop sees the destination but not the user. Messenger traffic is excluded from the tunnel to avoid loops. Node selection uses Bayesian reputation with 60-day freshness and make-before-break switching.
Related articles
AWG Router Delivers Script-Free AmneziaWG Cascades with Load Balancing, Speed Limits and Leak Prevention
AWG Router is an open-source Python-based web panel that manages complex AmneziaWG VPN cascades without hundreds of lines of bash scripts. The tool generates nftables rules, ip rules, and tc queues to route Russian networks directly while sending other traffic through foreign AmneziaWG servers or SOCKS5 proxies. It enforces strict leak protection so that traffic never falls back to the entry server’s Russian IP when an upstream tunnel fails. The panel supports per-client routing policies, domain-based rules via SNI inspection, automatic load balancing across multiple exits, and granular speed limits using HTB and fq_codel. All state is stored in resilient JSON files, and the system continues operating even if the panel itself is restarted or updated. The project is released under the MIT license with full source available.
TV Manufacturers Admit They Cannot Fully Disable User Data Collection
The Verge surveyed 11 major television and streaming device makers about their data collection practices, receiving responses from seven companies including Amazon, Apple, Google, LG, Roku, Samsung and TCL. Automatic Content Recognition (ACR) technology, used for targeted advertising and audience measurement, remains a central concern, with Samsung, LG and Amazon disabling it by default. Google enables diagnostic and advertising data collection under standard settings, while Apple stated that Apple TV 4K does not employ ACR. Amazon, Google, Samsung and Roku acknowledged that complete opt-out from data transmission is impossible, with devices caching information offline for later upload. Research from Northeastern University revealed that Vizio continued sending data even after users declined collection, labeling it as operational telemetry. LG was found to potentially store unencrypted voice command transcripts and determine location via nearby Wi-Fi networks when ACR is active.
Personal Data in Russian Franchise Networks: Who Qualifies as Data Operator Under 152-FZ
In typical franchise models, customer personal data is collected at franchisee points, stored in the franchisor’s central system, and used for network-wide loyalty programs and marketing. The key legal question is which party determines the purposes of processing and therefore bears operator status under Federal Law No. 152-FZ. The law defines an operator as the entity that independently or jointly sets processing purposes, data composition, and actions, regardless of contractual labels. Franchisees usually act as operators when concluding contracts with customers, while franchisors become processors unless they pursue independent goals such as running loyalty schemes or sending branded advertising. When a franchisor defines its own purposes, both parties may simultaneously qualify as operators for different processing objectives, requiring separate legal bases and documentation. Proper data-processing instructions must be embedded in the commercial concession agreement and must list specific data categories, actions, security measures, and breach-notification timelines to avoid administrative fines ranging from 150,000 to 500,000 RUB.
Dynamic Sites on Yandex Cloud Storage Enable Communication Under White-List Restrictions
A developer facing mobile internet white lists explored ways to exchange encrypted messages without relying on blocked infrastructure. Initial attempts with a national messenger bot failed due to poor API documentation and account hijacking. The team then modeled the problem as three neighboring plots where Alice and Bob route messages through Eve while a slow postman handles delivery. Yandex Disk was tested as a message store accessible via direct GET and POST requests, though it required accounts and suffered from 15-25 second latency. The final approach used Yandex Cloud object storage, whose domains remained whitelisted, allowing HTML files to load and function even when only government services and select platforms were reachable.