我们需要一个安全的替代方案来取代Telegram,适用于像OpenClaw或Hermes这样的代理。

3作者: oger大约 12 小时前原帖
Telegram 的问题在于,它并不是端到端加密(E2EE)的,因此你发送的每条消息都会以*未加密*的形式存储在他们的服务器上。<p>想想看——你有多少次在 Telegram 聊天中发布过 Gmail 验证 URL 或其他 API 令牌?是的——你现在应该至少感到有些不安。<p>WhatsApp 可以使用,但整合性不够紧密。<p>至于 Signal,Meredith Whittaker 在上周的一次会议上正确指出,给你的代理提供网页访问权限会打开所有私人聊天的访问。这可能是你也不想要的。<p>那么,接下来该怎么做呢?在我看来,创建一个 Signal 的分支,用于处理所有代理相关的事务,以便将其与人类互动分开,这样的想法是合理的。或者至少进行隔离,以确保代理在未经批准的情况下无法访问重要信息。<p>还有其他想法吗?
查看原文
The problem with Telegram is, that it is not E2EE - so every message you send will end up *unencrypted* on their servers.<p>Think about it - how often did you post the Gmail authentication URL or another API token in the Telegram chat? Yes - you should feel at least a little uneasy now.<p>WhatsApp works but is not so tightly integrated.<p>And regarding Signal, Meredith Whittaker rightfully pointed out at a conference last week that giving web access to your agent opens up access to all private chats. Probably something you wouldn&#x27;t want either.<p>So what&#x27;s the way forward here? To me it feels like a fork of Signal that would be used for anything agentic in order to separate it from the human interactions would make sense. Or at least compartmentalization so that an agent never gets access to the Crown Jewels without approval.<p>Any other ideas?