Urgent.News

600+ sources. One page. See who else covered it.

Tuesday, 4 August 2026 Reading Room
Editions ▾
🌐 Global edition🇦🇷 Argentina🇦🇺 Australia🇧🇷 Brazil🇨🇦 Canada🇨🇴 Colombia🇫🇷 France🇩🇪 Germany🇬🇭 Ghana🇭🇰 Hong Kong🇮🇳 India🇮🇩 Indonesia🇮🇱 Israel🇯🇵 Japan🇰🇪 Kenya🇲🇾 Malaysia🇳🇬 Nigeria🇵🇰 Pakistan🇶🇦 Qatar🇷🇺 Russia🇸🇦 Saudi Arabia🇸🇬 Singapore🇿🇦 South Africa🇰🇷 South Korea🇪🇸 Spain🇹🇭 Thailand🇦🇪 UAE🇺🇦 Ukraine🇬🇧 United Kingdom🇺🇸 United States🇻🇳 Vietnam

Tech

Telegram’s Brief App Store Removal Renews Questions About Apple’s CSAM Enforcement

The Telegram CEO says Apple made the app unavailable for download without any warning.

cnet.com ·

Telegram’s Brief App Store Removal Renews Questions About Apple’s CSAM Enforcement

Apple briefly removed the widely-used messaging app Telegram from its iOS App Store on Monday, sparking renewed debate about the company's approach to enforcing its rules against child sexual abuse material (CSAM). Telegram CEO Pavel Durov blamed Apple's swift action on a ransom attempt by a user within a public group chat. Durov accused Apple of overreacting after the app, which boasts over 1 billion users, was restored to the App Store within hours.

Apple confirmed to CNET that Telegram remained available in the Mac App Store and that existing users were not impacted. The company stated it removed Telegram after finding content that violated its strict guidelines. Durov accused Apple of singling out Telegram, warning that a single app with user-generated content could be at risk of removal without prior notice.

Telegram's X account responded to the controversy with a series of pointed posts, including a play on Durov's famous line "reports of my demise are greatly exaggerated," followed by an apple emoji.

Written by urgent.news from CNET's reporting — not their text. Machine-written — it may contain errors, so check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at cnet.com →

More in Tech

RAG vs. Direct Context: I Tested Both on Real Documents, Here's What Broke

A hands-on test of BGE-M3 + Qwen3 (RAG vs. direct-context answering) on a real research paper and a full-length book including a retrieval bug hiding in a footnote, and one surprisingly good model…

  • RAG and direct-context answering tested on real documents
  • RAG failed with full-length book, retrieved footnote as main contribution
  • RAG excelled with specific question about book, identified lack of relevant context

·dev.to

AWS WAF Challenge : bloquer les bots avant qu’ils n’atteignent l’application

Quand on m’a appelé, l’attaque durait depuis environ une semaine. Elle visait la page de connexion d’une application historique qui générait son HTML côté serveur.

  • Attack targeted legacy application's login page
  • Million queries from vast IP addresses, ineffective IP blocking
  • AWS WAF Challenge feature placed at infrastructure layer

·dev.to

Why RAG on legal text keeps hallucinating dates - and what actually fixed it

A couple of weeks ago I dropped the CRA text (the EU's cybersecurity regulation for IoT devices) into ChatGPT and asked when the main requirements actually kick in.

  • ChatGPT incorrectly stated CRA regulation entered force in 2024, 3 years off.
  • Dispersed dates in EU regulation PDF caused AI confusion.
  • Platanor rebuilt repository with proper file structure to fix RAG hallucinations.

·dev.to