# Telegram Published articles for Telegram. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Disrupting a new covert influence campaign from Russia DevFeed: [Disrupting a new covert influence campaign from Russia]() Original publisher: [Read original article]() Published: 2026-08-25T00:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [Artificial Intelligence](), [OpenAI](), [IO](), [ChatGPT]() Tags: [ai](), [articles](), [chatgpt](), [global-affairs](), [identity](), [linkedin](), [openai](), [social-media](), [telegram]() ### AI overview OpenAI describes disrupting a Russia-origin covert influence operation that used ChatGPT to generate social media comments promoting a fabricated Israel-based think tank and a Russia-favorable sovereignty index. The operators used VPNs and attempted to conceal their Russian origins. ### Source excerpt OpenAI banned Russia-origin accounts using AI to promote a fake Israel-based think tank and a "sovereignty" index praising Russia and criticizing the West. ## The Permanent Threat: Analyzing Aeternum's Blockchain-Based C2 Operations and Communications DevFeed: [The Permanent Threat: Analyzing Aeternum's Blockchain-Based C2 Operations and Communications]() Original publisher: [Read original article]() Author: Chris Navarrete, Sai Sathvik Ruppa and Haozhe Zhang Published: 2026-08-10T22:00:02Z Content type: article Language: en Sources: [Unit 42]() Topics: [Aeternum](), [C++](), [Firewall]() Tags: [aeternum](), [analysis](), [blockchain](), [c-plus-plus](), [c2](), [infection-chain](), [json](), [malware](), [python](), [rpc](), [telegram](), [threat-research](), [xmrig](), [xor]() ### AI overview An analysis of the Aeternum botnet loader, which uses Polygon blockchain smart contracts and public RPC endpoints for decentralized command-and-control. It also examines related Python malware using the Telegram API and a blended threat involving XWorm RAT, XMRig, and data exfiltration. ### Source excerpt Analysis of the Aeternum botnet loader, a threat leveraging Polygon blockchain smart contracts for decentralized C2 infrastructure and payload execution. The post The Permanent Threat: Analyzing Aeternum's Blockchain-Based C2 Operations and Communications appeared first on Unit 42. ## Telegram's Short-Link Domain Was Temporarily Suspended by Montenegro's .me Registry DevFeed: [Telegram's Short-Link Domain Was Temporarily Suspended by Montenegro's .me Registry]() Original publisher: [Read original article]() Published: 2026-07-14T00:00:00Z Content type: article Language: fr Sources: [Blog de Stéphane Bortzmeyer]() Topics: [domain](), [client](), [service]() Tags: [article](), [client](), [dns](), [domain](), [telegram]() ### AI overview Telegram's short-link domain became unavailable after Montenegro's .me registry stopped publishing it in DNS. The article examines the resulting NXDOMAIN responses, resolver caching, and the domain's later reactivation. ### Source excerpt Si vous utilisez le service de messagerie instantanée Telegram, vous avez sans doute vu aujourd'hui 14 juillet 2026, que des services ne marchaient pas, notamment les liens vers des ressources diverses (images, etc). C'est parce que le registre de noms de domaine du Monténégro l'avait décidé. Voyons les détails. ## macOS.Gaslight | Rust Backdoor Turns Prompt Injection on the Analyst, Not the Sandbox DevFeed: [macOS.Gaslight | Rust Backdoor Turns Prompt Injection on the Analyst, Not the Sandbox]() Original publisher: [Read original article]() Author: Phil Stokes Published: 2026-06-23T21:59:42Z Content type: article Language: en Sources: [SentinelLabs - We are hunters, reversers, exploit developers, and tinkerers shedding light on the world of malware, exploits, APTs, and cybercrime across all platforms.]() Topics: [AI Bots](), [AI Chat]() Tags: [agent](), [analysis](), [api](), [apple](), [attacks](), [backdoor](), [c2](), [data](), [llm](), [logs](), [macos](), [malware](), [payload](), [rust](), [sandbox](), [spoof](), [telegram](), [tls](), [update](), [virustotal]() ### AI overview SentinelLABS analyzes macOS.Gaslight, a Rust implant whose embedded prompt injection attempts to derail LLM-assisted malware triage. The report describes Telegram Bot API command and control, encrypted communications, token redaction, and a suspected DPRK-linked activity cluster. ### Source excerpt DPRK-linked implant embeds 38 fabricated system messages that spoof an LLM triage harness, hiding a credential stealer and Telegram C2 underneath. ## Chat SDK adds Novu support DevFeed: [Chat SDK adds Novu support]() Original publisher: [Read original article]() Author: Ben Sabic Published: 2026-06-22T14:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [SDKs](), [Command-line interface](), [Microsoft Teams](), [Slack]() Tags: [agent](), [bridge](), [channel](), [cli](), [documentation](), [identity](), [mapping](), [microsoft-teams](), [oauth](), [sdk](), [slack](), [support](), [telegram](), [tokens](), [whatsapp]() ### AI overview Chat SDK adds Novu support through a vendor-official adapter, allowing one handler set to connect agents to Slack, Microsoft Teams, WhatsApp, Telegram, and email. Novu manages credentials, identity, delivery, OAuth, and tokens, while a CLI command configures a channel and adds its credentials to the project. ### Source excerpt Chat SDK now supports Novu with the new vendor-official adapter. One handler set puts your agent on Slack, Microsoft Teams, WhatsApp, Telegram, and email. Novu handles credentials, identity, and delivery, keeping OAuth and tokens outside your app and mapping each channel to one user. Your agent always knows who they're talking to. Your agent can also send proactive notifications and handle the replies in the same loop, on whichever channel the customer used. One CLI command connects a real channel to your agent: It signs you in, creates a bridge agent, sets up the channel you pick (e.g., Slack), and adds the credentials to your project. Read the Novu documentation to get started. Read more ## Analysis of Telegram IPv6 BGP announcements by Indian ISPs DevFeed: [Analysis of Telegram IPv6 BGP announcements by Indian ISPs]() Original publisher: [Read original article]() Published: 2026-06-17T23:52:47Z Content type: opinion Language: en Sources: [Personal blog of Anurag Bhatia]() Topics: [BGP](), [networking](), [DDoS]() Tags: [as135709](), [as152144](), [as45820](), [bgp](), [ddos](), [lightstorm](), [rfc7999](), [rtbh](), [telegram](), [ttsl]() ### AI overview The article examines unusual BGP announcements for Telegram IPv6 prefixes by several Indian ISPs after a reported Telegram prefix hijack. It proposes that existing BGP blackholing configurations may have been used to block Telegram traffic, while noting this is the author's interpretation. ### Source excerpt Since the Telegram's prefix hijack (4 days ago on 17-Jun-2026) by RCom, there is visible noise in the BGP routing table from multiple other Indian ISPs, including Tata Teleservices (AS45820) / Lightstorm (AS135709/AS152144), etc. mostly in IPv6. Let's look at 2a0a:f280::/48 (Live lookup here) Notice all the ASNs here largely seem to be downstreams or peers of AS45820 in India, no major large peer or upstream that would take this announcement outside of India. Similarly, take the case of aggregate - 2a0a:f280::/32. This has TTSL (AS45820) as well as Lightstrom (AS152144/135709) originating these prefixes to smaller peers. Analysis: Possible reason and impact of this behaviour Today I tested some config in lab to see why this could be happening. Here's what I strongly feel is happening (quite sure, unless someone has a better explanation): Indian Govt. has asked ISPs to block Telegram and unlike past blocks mostly at the DNS layer, ISPs have been asked to drop IPs as well. Technically in these cases ISPs could simply add a blackhole route and that would drop traffic going towards these prefixes (from their customers) and that would not be visible at BGP (control plane) but only in traceroutes (data plane). If any of these customers had a full routing feed from those respective ISPs, they would keep on learning Telegram's route with the correct/expected AS_PATH and expected origin AS. Very likely these players had blackhole config setup for the DDoS protection and ended up using the same i.e they are treating Telegram's IPv6 prefixes like they would treat their own when under attack. Also, blackholing is a common practice during DDoS attacks. Imagine a network with a 100G uplink gets hit by a 400G volumetric attack. It will take up all the link bandwidth and thus in these cases ISPs blackhole their own (or downstream) IPs (often small - single /32s or a few) and they signal this to their BGP adjacencies as well. There is a standard BGP blackhole community: 65535:666 as ## Telegram prefixes hijack by Rcom AS18101 DevFeed: [Telegram prefixes hijack by Rcom AS18101]() Original publisher: [Read original article]() Published: 2026-06-16T19:44:03Z Content type: opinion Language: en Sources: [Personal blog of Anurag Bhatia]() Topics: [BGP](), [networking](), [Routing (disambiguation)]() Tags: [airtel](), [as15412](), [as18101](), [as4755](), [bgp](), [india](), [outage](), [rcom](), [ripe-ris](), [routers](), [routing](), [rpki](), [telegram](), [traffic]() ### AI overview The article examines Rcom AS18101's apparent BGP hijacking of Telegram prefixes during Telegram's blocking in India. It confirms that Rcom originated at least one Telegram prefix and argues that the incident was more likely an accidental configuration error than intentional sabotage, while noting that the impact varied by upstream connectivity. ### Source excerpt The last few hours were quite noisy with a lot of discussion around Telegram block and Rcom's hijack of Telegram prefixes. For those who may not know, Telegram has been blocked in India till 22 June 2026 (news here). The justification has been to avoid paper leak over the telegram. Anyways, I am not going into whether the block is good or bad as it can be part of an endless discussion depending on how one views it. Maybe some separate time but let's look at the BGP routing side of things. ISPs went for blocking it in all possible ways - from the usual DNS layer to block resolution of Telegram to also blackhole its prefixes. Telegram is a special case as they have their own ASN, IP prefixes etc making it easy to block them at the routing layer directly. I saw this on Airtel, where traffic seems to be dropping at their routers. mtr -wby0 -4 web.telegram.org Start: 2026-06-17T01:20:46+0530 HOST: desktop Loss% Snt Last Avg Best Wrst StDev 1. AS??? _gateway (172.16.0.1) 0.0% 10 0.2 0.2 0.2 0.2 0.0 2. AS??? 10.240.9.204 0.0% 10 4.6 7.4 4.2 25.7 6.5 3. AS??? 172.31.0.154 0.0% 10 8.1 13.5 6.4 26.4 6.2 4. AS9498 169.168.18.125.dhcp.anaronline.net (125.18.168.169) 0.0% 10 5.2 6.8 4.9 13.6 2.6 5. AS??? ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 At 11:58 PM - Telegram CEO Pavel Durov tweeted and accused Reliance (technically Rcom and not Jio) for outage of Telegram outside of India by BGP hijacking. Indian telecom Reliance is sabotaging access to Telegram for millions of users OUTSIDE India (including the UAE) via a rogue method called BGP hijacking. The sabotage seems intentional, as Reliance has ignored multiple reports. This may be part of a competitive war, as... -- Pavel Durov (@durov) June 16, 2026 Technically it's true that Rcom AS18101 has hijacked Telegram's prefixes. Take e.g 91.105.192.0/23 - AS18101 started originating this prefix at 16:14:19 GMT / 21:44:19 IST on 16 June as visible from many RIPE RIS collectors including RIPE RIS RRC01 in London. It's bad and they should not ha ## Chat SDK now supports rich text in Telegram DevFeed: [Chat SDK now supports rich text in Telegram]() Original publisher: [Read original article]() Author: Josh Singh Published: 2026-06-15T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [SDKs](), [Bot](), [Streaming](), [Markdown]() Tags: [documentation](), [guide](), [markdown](), [sdk](), [streaming](), [telegram]() ### AI overview Chat SDK now supports native rich-text rendering for explicit markdown and AST messages in its Telegram adapter. Bots can display headings, lists, tables, task lists, formulas, and separate media blocks, with streaming previews in private chats and automatic fallback for existing message types. ### Source excerpt Chat SDK now renders explicit markdown and ast messages as native rich messages on the Telegram adapter. Your bots get real headings, lists, tables, task lists, formulas, and separate media blocks instead of flattened text. What you get: Native formatting: headings, lists, tables, task lists, formulas, and media blocks. Streaming: private chats show live draft previews and persist the final response. Automatic fallback: plain strings, raw messages, cards, and captions continue to work exactly as before. Read the Telegram adapter documentation to get started. Read more ## Chat SDK adds Twilio adapter support DevFeed: [Chat SDK adds Twilio adapter support]() Original publisher: [Read original article]() Author: Ben Sabic Published: 2026-06-02T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [SDKs](), [AI Chat]() Tags: [bots](), [discord](), [github](), [history](), [media](), [slack](), [support](), [telegram](), [voice](), [whatsapp]() ### AI overview Chat SDK adds a Twilio adapter for building SMS, MMS, and voice-call bots across its supported messaging platforms. ### Source excerpt Chat SDK now supports Twilio, extending its single-codebase approach to Slack, Discord, GitHub, Teams, Telegram, and WhatsApp with the new Twilio adapter. Teams can build SMS and MMS bots that handle direct messages, inbound media, and message history. The adapter also ships low-level voice helpers, so you can build an app that handles voice calls using TwiML primitives. Modals, buttons, and reactions are not supported, and cards display as plain text. Outbound media must link to a URL accessible by Twilio. Read the documentation to get started, browse the directory, or build your own. Read more ## How I Run My Daily Standup on a Local LLM: Git, Gemma 4, llama.cpp and Telegram DevFeed: [How I Run My Daily Standup on a Local LLM: Git, Gemma 4, llama.cpp and Telegram]() Original publisher: [Read original article]() Author: Ivan Morgillo Published: 2026-05-27T09:51:06Z Content type: tutorial Language: en Sources: [Ivan Morgillo]() Topics: [gemma4](), [llama.cpp](), [Git](), [Large Language Model](), [API](), [Claude]() Tags: [anthropic](), [api](), [claude](), [gemma](), [gemma-4](), [git](), [llama-cpp](), [llm](), [local](), [local-llm](), [sdk](), [telegram]() ### AI overview A developer describes replacing a cloud-based daily standup pipeline with a local Gemma 4 E4B model running on llama.cpp. The pipeline reads Git commits, formats them, and posts the summary to Telegram. The article also explains how empty API-key settings caused several automations to use personal Claude subscription authentication instead of the Anthropic API. ### Source excerpt A real-world pipeline that scans my Git repos every morning, formats the day's commits with a local Gemma 4 E4B on llama.cpp, and posts the summary to Telegram -- no cloud, no API key, no AUP warnings. ## Chat SDK adds Messenger adapter support DevFeed: [Chat SDK adds Messenger adapter support]() Original publisher: [Read original article]() Author: Vishal Yathish Published: 2026-05-08T04:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [SDKs](), [Bot](), [Streaming](), [Pull Request]() Tags: [bots](), [building](), [community-contribution](), [discord](), [github](), [guide](), [sdk](), [slack](), [streaming](), [support](), [telegram]() ### AI overview Chat SDK adds a Messenger adapter, extending its single-codebase bot development approach across multiple messaging platforms. The adapter supports messages, reactions, attachments, postback buttons, and direct conversations, with display names fetched from user profiles. ### Source excerpt Chat SDK now supports Messenger, extending its single-codebase approach to Slack, Discord, GitHub, Teams, and Telegram with the new Messenger adapter. Teams can build bots that support messages, reactions, attachments, postback buttons, and direct conversations, with display names fetched automatically from user profiles. Try the Messenger adapter today: The adapter does not support message history, editing, or deletion. Certain components, like tables and fields, render as text fallbacks. Streaming is handled by accumulating and then sending the final message. Read the documentation to get started, browse the directory, or build your own adapter. Special thanks to @mitkodkn, whose community contribution in PR #461 laid the groundwork for this adapter. Read more ## Claude Code Persistent Memory: How I Wired Mempalace Into My Telegram Bot DevFeed: [Claude Code Persistent Memory: How I Wired Mempalace Into My Telegram Bot]() Original publisher: [Read original article]() Author: Ivan Morgillo Published: 2026-04-07T14:53:59Z Content type: tutorial Language: en Sources: [Ivan Morgillo]() Topics: [Claude Code](), [context](), [Bot](), [SQLite]() Tags: [agent](), [claude-code](), [guide](), [how-to](), [implementation](), [memory](), [sdk](), [sqlite](), [telegram](), [telegram-bot]() ### AI overview The article explains how the author added persistent, searchable memory to a Telegram bot wrapping Claude Code by integrating MemPalace. The approach stores conversation information outside expiring sessions and uses semantic search to retrieve relevant context, avoiding reliance on lossy session summaries. ### Source excerpt Claude Code forgets everything between sessions. Here's how I added persistent memory across conversations with Mempalace, wired into a Telegram bot. ## How to build an autonomous AI agent like OpenClaw (from scratch) DevFeed: [How to build an autonomous AI agent like OpenClaw (from scratch)]() Original publisher: [Read original article]() Author: Ashish Pratap Singh Published: 2026-04-07T04:20:00Z Content type: tutorial Language: en Sources: [AlgoMaster Newsletter]() Topics: [AI Agent](), [OpenClaw](), [Tutorial](), [coding](), [Large Language Model](), [Open Source](), [Security](), [Tool]() Tags: [ai-agent](), [autonomous](), [coding](), [context](), [how-to](), [llm](), [open-source](), [openclaw](), [prompt](), [security](), [telegram](), [tools]() ### AI overview This tutorial explains how to build Tiny-OpenClaw, a simplified autonomous AI agent inspired by OpenClaw. It describes capabilities such as web browsing, form filling, persistent memory, Skills, and Telegram communication, while deliberately excluding full system access because of security risks. ### Source excerpt This is a guest post by Dr. ## Chat SDK adds Zernio support DevFeed: [Chat SDK adds Zernio support]() Original publisher: [Read original article]() Author: Ben Sabic Published: 2026-04-01T14:00:00Z Content type: news Language: en Sources: [Vercel News]() Topics: [SDKs]() Tags: [api](), [bots](), [documentation](), [feature](), [integration](), [media](), [platform](), [social-media](), [streaming](), [support](), [telegram](), [whatsapp]() ### AI overview Chat SDK adds an official Zernio adapter for building bots across multiple social media platforms through one integration. Platform capabilities vary, with rich cards supported on Facebook, Instagram, Telegram, and WhatsApp, while editing and streaming are limited to Telegram. ### Source excerpt Chat SDK now supports Zernio, a unified social media API, with the new Zernio adapter. This is an official vendor adapter built and maintained by the Zernio team. Teams can build bots that work across Instagram, Facebook, Telegram, WhatsApp, X/Twitter, Bluesky, and Reddit through a single integration. Try the Zernio adapter today: Feature support varies by platform; rich cards work on Facebook, Instagram, Telegram, and WhatsApp, while editing and streaming are currently limited to Telegram. Read the documentation to get started, browse the directory, or build your own adapter. Read more ## How to Monetize a Telegram Mini App DevFeed: [How to Monetize a Telegram Mini App]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-03-29T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [web applications](), [API](), [JavaScript](), [Web Development]() Tags: [api](), [backend](), [global](), [guide](), [how-to](), [javascript](), [mobile](), [payments](), [subscriptions](), [telegram]() ### AI overview A guide to monetizing Telegram Mini Apps with Dodo Payments. It covers integrating a billing backend to support global payments, subscriptions, taxes, localized payment methods, and premium features. ### Source excerpt Complete guide to adding payments to Telegram Mini Apps. Accept global payments, handle subscriptions, and manage premium features using Dodo Payments as your billing backend. ## How to Sell Access to a Telegram Bot DevFeed: [How to Sell Access to a Telegram Bot]() Original publisher: [Read original article]() Author: Aarthi Poonia Published: 2026-03-28T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Bot](), [Messaging](), [API](), [Software as a service]() Tags: [how-to](), [license-keys](), [payment](), [payments](), [saas](), [subscription](), [technical](), [telegram](), [telegram-bot]() ### AI overview This guide explains how to monetize access to a Telegram bot using payment links, user payment verification, subscription pricing models, and access control. It presents Dodo Payments as a way to handle payment flows, taxes, and compliance for global sales. ### Source excerpt Monetize your Telegram bot with ease. Learn how to generate payment links, track user access, and handle global payments using Dodo Payments. ## Chat SDK brings agents to your users DevFeed: [Chat SDK brings agents to your users]() Original publisher: [Read original article]() Author: Eric Dodds Published: 2026-03-19T04:00:00Z Content type: article Language: en Sources: [Vercel News]() Topics: [SDKs](), [Bot](), [Messaging](), [TypeScript](), [Bots](), [API](), [Discord](), [Google Chat](), [Microsoft Teams](), [Slack](), [Google]() Tags: [agent](), [agents](), [api](), [apis](), [bots](), [coding-agents](), [developers](), [discord](), [github](), [integration](), [library](), [messaging](), [microsoft-teams](), [platform](), [platforms](), [sdk](), [slack](), [streaming](), [telegram](), [typescript]() ### AI overview Chat SDK is a TypeScript library for building bots and agents that work across Slack, Microsoft Teams, Google Chat, Discord, Telegram, GitHub, and Linear from a single codebase. It abstracts platform-specific messaging APIs through adapters, covering differences in streaming, formatting, branching logic, event routing, and reaction handling. ### Source excerpt In early March, we gave the entire organization a challenge: figure out how to multiply your output. People created agents. Mostly chat bots, but dedicated ones, purpose-built for real workflow augmentation: the agents were doing things automatically that would otherwise be tedious and time consuming. Initially people built individual interfaces for their agents, and AI SDK made that easy with out-of-the box model integrations and AI Elements to simplify UI design. Then we hit a constraint. People wanted to interact with the agents in Slack, meaning everyone had to figure out how to integrate with Slack's API. Then the problem got worse. Once the agents were in Slack, people wanted to integrate them with even more platforms, like Discord, Github, and even issue trackers like Linear. Each of those introduced a new integration adventure for every agent. It hit us. Instead of asking people to come to agents, we needed to deliver agents to the places they were already working. Chat needs integration abstraction We realized we had made it easy for our teams to create agents, but we needed to make it easier to extend them for adoption across platforms. This is true for every company. People are already using Microsoft Teams, WhatsApp, Telegram, and Google Chat, and agents need to be available in all of them. That's exactly what the Chat SDK does: makes agents available across enterprise and consumer chat platforms. Just like the AI SDK unified model provider APIs into a single interface, we built Chat SDK to abstract the quirks of messaging APIs into a simple framework for developers and their coding agents. Developers no longer need to think about the way streaming might differ from one platform to the next, or how formatting, branching logic, or even reaction-handling should be tackled for individual APIs. Write once, deploy everywhere Chat SDK is a TypeScript library for building bots that work across Slack, Microsoft Teams, Google Chat, Discord, Telegram, GitHub, and ## DigitalOcean launches OpenClaw on App Platform for elastic scaling and production operations DevFeed: [DigitalOcean launches OpenClaw on App Platform for elastic scaling and production operations]() Original publisher: [Read original article]() Author: DigitalOcean Published: 2026-02-05T18:48:11Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [OpenClaw](), [Digital Ocean](), [Artificial Intelligence](), [Deployment](), [Open Source](), [Messaging]() Tags: [ai](), [ai-agents](), [deployment](), [digitalocean](), [discord](), [open-source](), [openclaw](), [product-updates](), [slack](), [telegram](), [whatsapp]() ### AI overview DigitalOcean is launching OpenClaw on App Platform to help teams operate always-on, multi-agent AI assistants with elastic scaling, safer defaults, predictable instance-based pricing, and simpler operations. ### Source excerpt OpenClaw has quickly become a popular open-source framework for building personal AI assistants connected to services as well as messaging platforms such as Telegram, WhatsApp, Discord, and Slack. As more developers move from local experiments to always-on assistants, the challenge shifts from building an agent to operating one reliably over time, often across multiple agents handling different workstreams. Once an assistant is running continuously, handling real traffic, and coordinating tools or APIs, new questions surface quickly: How do you keep it running without constantly managing servers? How do you scale from one assistant to multiple agents without re-architecting? How do you apply security and access controls you can trust by default? How do you grow usage without turning operations into a second job? How do you scale agents without losing visibility or predictability into costs? Today, we're launching OpenClaw on DigitalOcean App Platform to answer these questions. It is designed for this stage--helping teams move from proof of concept to sustained production operation with elastic scaling, safe defaults, and simpler day-to-day operations. Further, OpenClaw on App Platform brings cost predictability to always-on AI systems. Instead of variable, request-driven pricing that can spike unexpectedly as usage grows, App Platform uses clear, instance-based pricing. Teams can understand how costs change as they add agents or increase capacity without surprises. OpenClaw on App Platform: Built for always-on, multi-agent AI systems As OpenClaw usage grows, developers naturally reach different stages of operation. Some teams want a fast, VM-based deployment with full system control. That's exactly what the 1-Click Deploy OpenClaw on a DigitalOcean Droplet® server provides: a secure, hardened environment where you own the virtual machine and manage the underlying infrastructure directly. Other teams reach a point where infrastructure ownership becomes unnecessary ove ## Operation "False Witness": Fake recovery service impersonating authorities DevFeed: [Operation "False Witness": Fake recovery service impersonating authorities]() Original publisher: [Read original article]() Published: 2026-02-01T00:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [Artificial Intelligence](), [OpenAI](), [Messaging](), [Website]() Tags: [ai](), [case-study](), [crime](), [financial](), [fraud](), [law](), [messaging](), [openai](), [reporting](), [safety](), [scam](), [social-media](), [telegram]() ### AI overview OpenAI banned a cluster of ChatGPT accounts that very likely originated in Cambodia and were used in a recovery scam targeting fraud victims. The operation used AI to create content for fake law firms, impersonate attorneys and authorities, build trust, and solicit money through fraudulent recovery services. ### Source excerpt OpenAI banned accounts that very likely originated in Cambodia and used AI to pose as recovery services, law firms, and authorities targeting people affected by fraud. ## Operation "Date Bait": AI-enabled scam targeting loveseekers DevFeed: [Operation "Date Bait": AI-enabled scam targeting loveseekers]() Original publisher: [Read original article]() Published: 2026-02-01T00:00:00Z Content type: news Language: en Sources: [OpenAI News]() Topics: [Artificial Intelligence](), [OpenAI](), [ChatGPT](), [Automation](), [API]() Tags: [ads](), [ai](), [api](), [automation](), [chatgpt](), [engagement](), [openai](), [safety](), [scam](), [social-media](), [structured](), [tasks](), [telegram](), [translation](), [trust]() ### AI overview OpenAI describes Operation "Date Bait," in which accounts likely originating in Cambodia used ChatGPT and API access for a semi-automated romance and task scam targeting Indonesian men. The operation used translated and emotionally manipulative outreach across advertisements, an AI chatbot, Telegram, and dating platforms. ### Source excerpt OpenAI banned accounts that very likely originated in Cambodia and used AI for scam outreach to Indonesian loveseekers, including translation and engagement. ## Operation "Fish Food": Russia-origin content farm activity DevFeed: [Operation "Fish Food": Russia-origin content farm activity]() Original publisher: [Read original article]() Published: 2026-02-01T00:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [Artificial Intelligence](), [ChatGPT](), [OpenAI](), [Open Source](), [Internet]() Tags: [ai](), [case-study](), [chatgpt](), [language](), [openai](), [report](), [safety](), [social-media](), [telegram]() ### AI overview OpenAI reports banning ChatGPT accounts linked to the Rybar network in an operation it called Fish Food. The accounts used AI to generate multilingual content, social media comments, and Sora videos for dissemination across websites and social platforms. OpenAI says some accounts likely originated in Russia and that it could not independently confirm how all generated content was posted. ### Source excerpt OpenAI banned accounts linked to the Rybar network, some of which likely originated in Russia, that used AI to support multilingual influence activity across websites and social platforms. ## How red\_mad\_robot integrated Daisy's AI layer into Beeline's "план б." platform DevFeed: [How red\_mad\_robot integrated Daisy's AI layer into Beeline's "план б." platform]() Original publisher: [Read original article]() Author: redmadrobot (red\_mad\_robot) Published: 2025-12-18T11:43:04Z Content type: article Language: ru Sources: [Redmadrobot EN](), [Redmadrobot RU]() Topics: [Artificial Intelligence](), [User experience (UX)](), [Large Language Model]() Tags: [agentic](), [ai](), [genai](), [llm](), [llm-12323b29df45](), [red-mad-robot](), [telegram](), [ux]() ### AI overview The article describes red_mad_robot's 2025 partnership with Beeline and the creation of an AI layer for the "план б." platform using the Agentic-First Daisy solution. It discusses integrating AI capabilities into an existing digital ecosystem and user experience rather than requiring a separate service. ### Source excerpt В 2025 году AI окончательно вышел за рамки экспериментальных функций и стал инфраструктурным слоем цифровых продуктов. Он всё чаще определяет не отдельные возможности, а логику развития экосистем, скорость запуска новых продуктов и качество пользовательского опыта. Именно в этом контексте в 2025 году red_mad_robot и Билайн заключили стратегическое партнёрство. Мы развиваем сразу несколько направлений -- от AI-сервисов до клиентских продуктов, где технологии усиливают ежедневный UX. Одним из первых шагов стало создание полноценного AI-слоя для платформы Билайна "план б." на базе Agentic-First решения Daisy. Рассказываем, как мы подошли к проектированию AI-функциональности, какие решения легли в основу архитектуры и что получилось на практике. Читать далее ## CSAM Regulation Update: Dutch Intelligence agency weighs in DevFeed: [CSAM Regulation Update: Dutch Intelligence agency weighs in]() Original publisher: [Read original article]() Published: 2024-10-01T17:52:22Z Content type: opinion Language: en Sources: [Bert Hubert's writings]() Topics: [End-to-End Encryption](), [Security](), [Cryptography](), [Mobile](), [Artificial Intelligence](), [communications]() Tags: [aivd](), [apple](), [civil-rights](), [csam](), [encryption](), [eu](), [politics](), [privacy](), [security](), [signal](), [telegram](), [whatsapp]() ### AI overview The article discusses a proposed EU CSAM regulation that could require scanning private messages and images on encrypted communication services. It reports that the Dutch government consulted the AIVD, which regarded detection orders and the associated scanning infrastructure as too large a security risk for digital resilience. ### Source excerpt A quick update - The European Commission and EU member states have been pondering, for years now, if they should force WhatsApp/Apple/Signal/Telegram to scan all our private messages for suspected child sexual abuse material (CSAM). For various reasons it is a horrendous idea to break end to end encryption in this likely highly ineffective way. Variations of the proposal have also included a mandate to perform such scanning of images using AI, and even to also read our text messages to see if we aren't "grooming" children. ## Postgres Realtime location sharing with MapLibre DevFeed: [Postgres Realtime location sharing with MapLibre]() Original publisher: [Read original article]() Author: Thor Schaeff Published: 2024-07-04T07:00:00Z Content type: tutorial Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [JavaScript](), [React](), [Remote Procedure Call (RPC)](), [API](), [data](), [Database]() Tags: [api](), [build](), [capture](), [code](), [function](), [getting-started](), [guide](), [how-to](), [javascript](), [js](), [map](), [migrations](), [postgres](), [react](), [realtime](), [remote](), [rpc](), [state](), [subscription](), [telegram]() ### AI overview This tutorial shows how to build live location sharing with Supabase, Postgres, Supabase Realtime, a Telegram Bot, and MapLibre GL JS in React. It covers capturing location data in a Supabase Edge Function, inserting it through an RPC, subscribing to database changes, and displaying updated markers on a map. ### Source excerpt Use Supabase Realtime to draw live location data onto the map with MapLibre GL JS. [Next page]()