LxBox Evolves from VPN Client to Comprehensive Network Traffic Management Ecosystem
LxBox has rapidly evolved from a simple Android VPN client into a complete ecosystem for managing network traffic across phones, desktops, and routers. The project now unifies VPN and proxy protocols under one routing engine, enabling users to handle corporate connections, personal proxies, and home networks through a single interface.
The developer began with a personal goal of creating a client for sing-box that met individual needs while demonstrating strong project management. Market feedback quickly expanded the scope: the core was forked to add AmneziaWG and XHTTP support, later extended to routers via OpenWrt, and then to desktop environments. Users demanded consistent experiences across devices, leading to the current multi-platform approach.
LxBox now supports numerous protocols in one routing table. VPN options include WireGuard, AmneziaWG, OpenVPN, SSL VPN via OpenConnect (covering Fortinet, Cisco, GlobalProtect, F5, and Pulse), and Tailscale. Proxy protocols cover VLESS, VMess, Trojan, Shadowsocks, Hysteria2, TUIC, AnyTLS, NaïveProxy, TrustTunnel, SSH, SOCKS, and HTTP. This integration allows rules such as routing work domains through corporate SSL VPN while sending other traffic via personal proxies.
The project operates along three main tracks: the sing-box-lx core with added features including MASQUE, post-quantum VLESS, and the lxd daemon for routers; the LxBox Android client available on Google Play, F-Droid, and GitHub; and the singbox-launcher desktop tool written in Go that also serves as a router interface.
Security receives particular attention. Default presets block incoming connections from VPN tunnels unless explicitly allowed, preventing unauthorized access from third-party servers or compromised peers. Additional rules catch traffic from excluded applications that might leak server addresses via direct binding to the tunnel interface. No telemetry or analytics SDKs are present in the APK, and subscription requests use only standard headers with optional random identifiers.
The interface follows a progressive disclosure model similar to progressive JPEG encoding. Users start with one-click Cloudflare WARP setup, advance to subscription-based routing with presets, and can reach deep customization through routing rules, per-app controls, diagnostics, subscription filters, and direct JSON editing. Documentation is structured in layers to support both human readers and AI agents.
Related articles
Understanding Russia's TSPU: How DPI Filtering, DNS Manipulation and Traffic Throttling Work
Russia's TSPU system combines hardware filters from RDP.ru with EcoFilter and EcoDPI software to perform both simple IP/port/transport blocking and advanced protocol recognition. The platform inspects DNS queries, SNI fields in TLS handshakes, QUIC packets and HTTP headers to enforce domain blacklists or apply throttling. When simple blocking fails, operators fall back to traffic shaping that drops packets or limits bandwidth after an initial window. Multiple bypass techniques including encrypted DNS tunnels, ECH, and specialized proxies such as Hysteria 2, NaiveProxy and Shadowsocks are examined in detail. The article also outlines future developments including expanded residential whitelists and neural-network-based traffic classification.
ONYX 2.0 Removes Central Servers for Fully Decentralized Tor-Based Messaging and Calls
ONYX 2.0-beta marks a major shift from its previously centralized design to a serverless architecture that relies entirely on Tor for all communications. Each user account is now represented solely by a cryptographic key pair generated on first launch, with recovery handled through a 12-word seed phrase. Devices connect directly via onion services, and the application bundles its own Tor daemon on desktop platforms while using tor-android on mobile devices. Voice calls are supported through an embedded local TURN server, delivering acceptable quality with 1-3 second latency despite the anonymity overhead. Message delivery now depends on recipient availability, with undelivered messages stored locally on the sender and retried automatically. The update deliberately removes features such as HTTP or SOCKS5 proxies and link previews to prevent IP leaks or external traffic. Developers released the beta to gather feedback on stability across network changes and multi-device scenarios.
Privacy-Focused Browser Tool Compresses PDFs Locally Without Uploading Sensitive Documents
A developer created a PDF compression tool that runs entirely inside the browser to protect sensitive personal and professional documents from third-party servers. The solution addresses repeated situations where embassy submissions, financial presentations, contracts, and internal reports exceeded size limits, forcing users to choose between installing desktop software or risking data exposure through online services. The tool reduces scanned and photographic PDFs by 66 to 97 percent depending on quality settings while honestly reporting weaker performance on text-heavy files compared with Ghostscript. It works on both desktop and mobile platforms, including iPhone and Android, requires no installation, and continues functioning offline after the first page load. On mobile devices the application respects memory constraints by limiting images to four megapixels, preserving readability for A4 documents intended for printing. The project originated from a single evening script built around Ghostscript and evolved into a full web application after similar compression needs recurred across multiple devices and locations.
Building Prizrak: How a Developer Created a Federated Messenger That Masks All Traffic as Legitimate HTTPS
A developer created Prizrak, a federated messenger with end-to-end encryption where all traffic, including calls, is indistinguishable from ordinary HTTPS connections. The project addresses three common limitations of existing messengers: centralized control points, mandatory phone numbers, and detectable encrypted traffic. It uses real TLS 1.3 handshakes to actual domains, multi-port listening, and a hidden token mechanism inside the encrypted channel. When servers cannot reach each other directly, messages are delivered through a network of storage nodes modeled after Ceph's RADOS system. Voice and video calls run on a native media stack with custom STUN-like functionality and careful UDP buffer sizing to avoid packet truncation. An integrated two-hop VPN reuses the same stealth transport while keeping messenger traffic outside the tunnel.