Telegram Will Not Allow Scanning of Private Chats — Pavel Durov Strongly Criticizes EU Over Chat Control Initiative
Pavel Durov, founder of the messaging platform Telegram, has delivered a sharp rebuke to the European Union over renewed efforts to advance the Chat Control initiative. The proposal, which has resurfaced in EU legislative discussions, could authorize or require online services to scan private messages, emails, and photographs in order to detect prohibited content.
Durov reacted forcefully to the development, stating that methods previously associated with banana republics are now being employed within the EU to push through surveillance legislation. He made it unequivocally clear that Telegram will not scan users’ personal messages, irrespective of any regulatory maneuvers attempted by European authorities.
The founder reiterated the platform’s longstanding position: private correspondence must not be converted into material for mass automated monitoring. This stance directly challenges the direction of the proposed Chat Control regulation currently under debate.
Background on the Legislative Initiative
The European Parliament has returned the bill linked to the Chat Control initiative for further consideration. Earlier drafts explored the possibility of allowing online platforms to voluntarily scan user-generated content, including text messages and media files, with the stated goal of identifying illegal material.
Opponents of the measure contend that the legislation would establish a de facto system of mass surveillance of private communications, despite being presented under the banner of public safety. Proponents, however, maintain that such scanning capabilities are essential for combating illegal content and safeguarding users online.
In this ongoing debate, Telegram has aligned itself firmly with privacy advocates. Durov’s statements signal that the service intends to resist any attempts to transform encrypted personal chats into accessible data streams for regulatory oversight, even as the EU continues to tighten requirements for technology platforms.
Related articles
TSPU Filtering Disrupts Timeweb Cloud Servers: Diagnosis, CDN Failures, and Reverse Proxy Bypass
Russian hosting provider Timeweb Cloud experienced widespread TSPU-based DPI filtering starting in early June that selectively blocked TLS handshakes on port 443 while leaving SSH, ICMP, and TCP connectivity intact. The issue affected multiple providers including Beget and Selectel, was publicly acknowledged by Timeweb on June 5, and proved highly variable by region, operator, and time of day. Attempts to mitigate via new IP addresses or Timeweb's own CDN failed due to poisoned caches and platform outages, while Yandex Cloud CDN blocked all POST requests required for WordPress functionality. A working solution involved deploying a minimal nginx reverse proxy on another Russian cloud VPS that preserves full HTTP methods, handles certificate synchronization, and routes ACME challenges correctly. Timeweb support later closed tickets without resolution after requesting ineffective mtr traces that cannot detect DPI behavior. The case highlights systemic challenges in diagnosing state-mandated filtering and the limitations of standard network diagnostics against selective TLS interference.
UnifiedPush and Public ntfy.sh: Why Push Notifications Fail on Android Without Google Services
Developers building a messenger without Google services adopted UnifiedPush with the public ntfy.sh instance as the default distributor and push server. Production logs revealed that four out of five delivery attempts failed from day one, with error codes 507, 429, and 400 dominating. The 507 errors occurred because ntfy from Google Play relies on Firebase for instant delivery, leaving no active subscriber visible to the server when FCM is unavailable. Rate-limit 429 responses were triggered against the recipient's IP rather than the sender, collapsing under carrier-grade NAT used by mobile users. WebPush endpoints additionally rejected requests missing the mandatory TTL header. The team ultimately deployed a self-hosted ntfy instance and an embedded distributor inside the app to bypass these constraints.
Innovative Tunneling Techniques Leverage File Storage, IMAP, Meek, and NTP for Covert Connectivity
A new wave of experimental tunneling tools has emerged for establishing network connectivity through unconventional channels such as shared file storage, email accounts, legacy CDN protocols, and NTP. File-Tunnel enables TCP proxying by writing data to common storage backends including S3 and WebDAV, allowing traffic to blend with ordinary object storage access. True IMAP Tunnel (Secure) turns an IMAP mailbox into a bidirectional transport by storing encrypted frames as draft messages, supporting providers like Gmail, Outlook, and Yandex while offering optional AES-256-GCM encryption. Meek, originally from the Tor project, is being repurposed as a standalone pluggable transport that uses HTTP POST requests with session headers to traverse CDNs and shared hosting environments. ntptun implements IP-over-NTP and UDP-over-NTP by embedding payloads in NTP extension fields, with poll and push modes for downstream traffic and integration options with GOST for KCP-based proxies. These methods target dissidents and network experimenters seeking resilient bypass techniques against filtering and surveillance.
Six Bitrix24 Disk Migration Errors That Force Portal Redesign After Six Months
A detailed analysis reveals that copying a legacy file share structure directly into Bitrix24 Disk creates persistent access control, ownership and performance problems that surface only after several quarters of operation. The article examines six specific mistakes including one-to-one folder replication, overuse of personal My Disk storage, assignment of rights to individual users instead of departments, dumping unclear documents into the common drive, attaching file copies rather than links to CRM and tasks, and enabling full desktop synchronization. Each error is illustrated with real symptoms, root causes from rushed migrations, and concrete remediation steps using REST and D7 API calls. A Toyota T-Connect case from 2013-2023 demonstrates how unmonitored open permissions can remain undetected for a decade. The guidance stresses pre-migration inventory, pilot testing on one department, named owners for every top-level section, and quarterly rights audits. The piece is aimed at integrators and IT leads who handle large Bitrix24 deployments.