Hydrat Project Builds Automated WireGuard Gateway for Resilient VLESS and Tor Routing
A developer has introduced Hydrat, an automated WireGuard gateway designed to maintain connectivity when VLESS servers become blocked or degraded. The project allows users to keep a single WireGuard profile on phones, laptops, and routers while the server handles proxy selection and failover.
The gateway accepts VLESS links, subscription feeds, and Tor bridges through an admin panel. Candidates undergo preliminary and full testing that checks access to Cloudflare, YouTube, ChatGPT, OpenAI API, and Telegram services, including UDP performance. Up to 10,000 candidates can be stored, with a working pool limited to 200 high-quality routes.
Active monitoring detects outages through fast HTTP and DNS probes, while a separate QoE loop measures time-to-first-byte and throughput against historical baselines. Routes enter degradation status after three poor results out of five and recover only after four good measurements. Two confirmed failures within a 20-measurement window also trigger alerts.
Client assignment uses weighted rendezvous hashing for initial selection. Planned route changes require a sustained 30 percent advantage, at least 30 minutes on the current path, and confirmation across three checks. Failover prefers pre-assigned backups before scanning the pool, and transport-level blocking occurs only when no viable alternative remains.
Network changes are applied sequentially: a new Xray outbound is created first, nftables rules are updated next, and old exits are removed last to avoid transient client disconnection. Separate counters ensure that only newer test results update route state.
The service runs in Docker, supports obfs4 and webtunnel Tor bridges, and preserves the last applied routing plan across restarts. The author notes that the server must remain reachable via WireGuard and therefore recommends placement within Russian jurisdiction.
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.