ICDYCT / I Can Do, You Can Too

Effect

效果

Preface I set up a keyword-reply bot in the group. There are tons of projects on Github. Skipping that. But none of them had a feature to auto-delay-delete reply messages. I always assumed that a Worker only runs when there's an HTTP request — meaning it only runs when someone sends a message in the group. So naturally, it couldn't handle delayed message deletion.

前言 在群里搞了一个关键字回复机器人. Github 上面大把的项目. 略. 但是一直没有自动延迟删除回复消息的功能. 我的概念里面 worker 是 http 请求时才会运行的, 也就是说, 有人在群里发了消息, 这个worker才会运行. 那自然就做不了延迟删除消息了.

I like one design of Hermes-agent . During the installation and setup process, a telegram bot is bound, so I can chat with this bot directly no matter where I am. DM-ing the bot directly, or finding the bot to chat in different groups — these are all different sessions, and the contexts won't pollute each other. What I commonly use is, open a group, enable the topic feature, then open different topics to chat with the bot for different subjects, and the contexts won't pollute each other. Does it look a bit like the effect of switching between different sessions on a webui? Compared with webui, telegram solves the network setup and operation for remote connection Note that with this usage, the agent is still the same one, so after the session is summarized into memory, the memory is shared. If you're worried that the stuff saved in memory is too messy and affects the usage effect, then you need to isolate at the agent level. My usage has some common scenarios,  For example, ...

我喜欢 Hermes-agent 的一个设计. 在安装设置过程中, 绑定了一个 telegram bot, 我不管在什么地方都可以直接和这个bot交流. 和bot直接dm私聊, 在不同的群里面找bot聊, 都是不同的session, 不同的上下文之间不会污染. 我常用的就是, 开一个group, 打开 topic功能, 然后不同的话题就开不同的topic和bot聊, 上下文不会污染.