@zaofan/dsh-qqbot 1.6.5 → 1.6.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +24 -0
- package/README_EN.md +23 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -71,6 +71,30 @@ QQ 官方**没有开放踢人接口**，所以这一块走"你自己的 QQ 号 +
|
|
|
71
71
|
|
|
72
72
|
---
|
|
73
73
|
|
|
74
|
+
## 🆚 官方 Bot 方案 vs onbot / NapCat 等第三方协议端
|
|
75
|
+
|
|
76
|
+
本插件走的是**腾讯官方 QQ 机器人开放平台**（AppID + AppSecret + 官方 SDK），
|
|
77
|
+
**不是**"模拟 QQ 客户端协议"那条路。两者差别不小，先把话说清楚：
|
|
78
|
+
|
|
79
|
+
| | **本插件（官方 Bot API）** | 第三方协议端（onbot / NapCat / Lagrange…） |
|
|
80
|
+
|---|---|---|
|
|
81
|
+
| **登录方式** | 填 **AppID / AppSecret** 即可，**不扫码、不登录你的真人 QQ 号** | 扫码登录**你的个人 QQ 号**，常掉线、要保活 |
|
|
82
|
+
| **账号安全** | ✅ **完全不碰你的个人号**，无封号风险 | ⚠️ **有封号风险**：协议模拟违反 QQ 用户协议，腾讯明确禁止 |
|
|
83
|
+
| **稳定性** | ✅ 官方接口，腾讯自己在维护；变更会提前公告 | ⚠️ 协议一变就挂，得等签名服务（qsign 之类）跟进 |
|
|
84
|
+
| **资源占用** | ✅ **极低**：纯 HTTP + WebSocket，无浏览器、无协议端常驻 | ⚠️ 高：要挂 QQ 客户端 / 协议端，内存几百 MB 起 |
|
|
85
|
+
| **低配 / 手机部署** | ✅ **能跑**：安卓 Termux、树莓派、1 核 1G 的小机器都行（见下方「📱 装到手机上」） | ⚠️ 难：协议端对架构/内存有要求，安卓上尤其折腾 |
|
|
86
|
+
| **隐私** | ✅ 只与腾讯官方通信，没有中间人 | ⚠️ 要经过第三方协议实现 |
|
|
87
|
+
| **功能范围** | ⚠️ **受官方开放范围限制**（例：**踢人接口官方没开放**） | ✅ 全功能 |
|
|
88
|
+
|
|
89
|
+
**关于"功能受限"，本插件的态度**：官方没开放的，能补就补、不能补就明说 ——
|
|
90
|
+
例如**踢人**：官方接口至今未开放，插件用 **🔨 锤子** 面板让你**用自己的号**走群官网接口把这块补上
|
|
91
|
+
（扫码一次、之后长期免扫，登录态还会和 AI 共享，详见下文）。
|
|
92
|
+
|
|
93
|
+
> **一句话**：想要**安全、省心、还能塞进手机或小机器**，就选官方 Bot 方案；
|
|
94
|
+
> 只有当你非要第三方协议端的"全家桶"、并且愿意承担封号风险时，才另说。
|
|
95
|
+
|
|
96
|
+
---
|
|
97
|
+
|
|
74
98
|
## 安装
|
|
75
99
|
|
|
76
100
|
> ## ⚠️ 必须装到 `web` profile
|
package/README_EN.md
CHANGED
|
@@ -91,6 +91,29 @@ QQ User → QQ WebSocket → dsh-im-qqbot → ctx.agents → dsh agent loop →
|
|
|
91
91
|
(assistant reply → QQ sendMarkdown)
|
|
92
92
|
```
|
|
93
93
|
|
|
94
|
+
## 🆚 Official Bot API vs third-party protocol bridges (onbot / NapCat / …)
|
|
95
|
+
|
|
96
|
+
This plugin uses the **official Tencent QQ Bot Open Platform** (AppID + AppSecret + the official SDK),
|
|
97
|
+
**not** the "simulate a QQ client protocol" route. The difference is not cosmetic:
|
|
98
|
+
|
|
99
|
+
| | **This plugin (Official Bot API)** | Third-party bridges (onbot / NapCat / Lagrange…) |
|
|
100
|
+
|---|---|---|
|
|
101
|
+
| **Login** | Just paste **AppID / AppSecret** — **no QR scan, your personal QQ is never logged in** | Scan a QR code to log in **your personal QQ account**; drops often, needs keep-alive |
|
|
102
|
+
| **Account safety** | ✅ **Never touches your personal account** — no ban risk | ⚠️ **Ban risk**: protocol simulation violates QQ's ToS and is explicitly forbidden |
|
|
103
|
+
| **Stability** | ✅ Official API maintained by Tencent; breaking changes are announced ahead | ⚠️ Breaks whenever the protocol shifts; must wait for signature services (qsign etc.) |
|
|
104
|
+
| **Footprint** | ✅ **Very low**: plain HTTP + WebSocket — no browser, no resident client | ⚠️ Heavy: a QQ client / bridge must stay resident, hundreds of MB of RAM |
|
|
105
|
+
| **Low-spec / mobile** | ✅ **Runs anywhere**: Android (Termux), Raspberry Pi, a 1-core / 1 GB box | ⚠️ Hard: bridges have arch/RAM requirements, especially painful on Android |
|
|
106
|
+
| **Privacy** | ✅ Talks only to Tencent's official endpoints — no middleman | ⚠️ Traffic passes through a third-party implementation |
|
|
107
|
+
| **Feature coverage** | ⚠️ **Limited to what the official platform opens** (e.g. **kicking is not exposed**) | ✅ Everything |
|
|
108
|
+
|
|
109
|
+
**About "limited coverage"** — we patch what we can, and say so plainly when we can't.
|
|
110
|
+
Example: **kicking members**. The official API still doesn't expose it, so the plugin adds a **🔨 Hammer**
|
|
111
|
+
panel where **your own account** calls the group website API to fill the gap
|
|
112
|
+
(scan once, then it stays logged in; the credential is shared with the AI — see below).
|
|
113
|
+
|
|
114
|
+
> **TL;DR**: want **safe, low-maintenance, deployable on a phone or a tiny box**? Go official.
|
|
115
|
+
> Only pick a third-party bridge if you genuinely need its full toolkit and accept the ban risk.
|
|
116
|
+
|
|
94
117
|
## Installation
|
|
95
118
|
|
|
96
119
|
> ⚠️ **Install into the `web` profile** (host of the `dsh web` settings panel); other profiles get a bare
|