BiliCommentManager v1.2

B 站评论管理器（黑历史管理器）v1.2：稳定性大修＋后台任务可感知可控制。

本版更新

稳定性修复（本版重点）

• 修复后台任务（拉取/删除）无声中断的多个根因：依赖缺失时任务秒退且无任何提示、任务存盘与界面读取撞车导致中断、进程存活误判导致进度条不显示
• 修复误判引发的重复拉起任务：新增文件锁，两个删除/拉取进程不可能同时运行
• 修复 pid 复用风险：停止按钮不会误杀无关进程
• 任何退出路径都会把原因写进任务日志并在界面显示——任务消失时总能知道为什么

拉取任务可感知可控制

• 底部状态栏实时显示拉取进度（百分比＋剩余时间预估）
• 停止按钮随任务切换：停止删除／停止拉取／停止全部
• 任务结束区分「完成／被停止／未启动成功」并附原因

提示语改进

• 故障消息同时包含界面操作指令（如「等几个小时再点一次开始删除」）与技术备注（如 --delay 参数），新手与命令行用户各取所需
• 任务失败原因常驻页面顶部红条（可关闭），不再 6 秒一闪而过
• 明确提示：长任务中途关闭窗口甚至关机都没关系，下次点同一按钮自动继续
• 预估耗时按实际评论数量计算，不再写死

其他

• 新增 35 个自动化测试用例（任务锁／进程探测／存盘重试／退出日志等关键路径）
• README 顶部新增「首次运行必读」：SmartScreen 警告与杀毒软件误报的处理步骤

下载 / Download

• BiliCommentManager.exe（约 21MB）：下载后双击即用，无需安装 Python（Windows 10/11）
• 首次运行的 SmartScreen 蓝色警告与杀毒误报处理，见仓库 README 顶部的「首次运行必读」
• 从 v1.1 升级：关闭正在运行的旧版窗口后直接替换 exe 即可，数据文件（Cookie、评论清单）通用

---

v1.2 of the Bilibili comment & black-history manager: a major stability overhaul, plus background tasks you can actually see and control.

Stability fixes (the headline)

• Fixed several root causes of background tasks (fetch/delete) dying silently: workers exiting instantly on missing dependencies with no message; saves colliding with UI reads mid-run; process-liveness misdetection that hid running tasks from the progress bar
• Duplicate task spawns are now impossible: a file lock guarantees at most one delete/fetch worker at a time
• PID-reuse hardening: the stop button can no longer kill an unrelated process
• Every exit path logs its reason and the UI surfaces it — a task never just vanishes

Observable, controllable fetch

• Live fetch progress in the bottom bar (percentage + remaining-time estimate)
• The stop button follows the running task: stop delete / stop fetch / stop all
• Task endings are classified (completed / stopped / failed to start) with the reason attached

Better messages

• Failure messages carry both a UI-level action ("wait a few hours, click Start Delete again") and a technical note (--delay etc.) — novices and CLI users each get their half
• Failure reasons persist in a dismissible red banner instead of a 6-second toast
• Long tasks now say explicitly: closing the window or even shutting down is fine — click the same button to resume
• ETAs are computed from your actual comment count

Also

• 35 automated tests covering the critical paths (locks, process probing, save retries, exit logging)
• The README opens with a first-run must-read: SmartScreen and antivirus false-positive guidance

Download

• BiliCommentManager.exe (~21MB): double-click to run — no Python, no dependencies (Windows 10/11)
• For the first-run SmartScreen warning and antivirus false positives, see the first-run must-read at the top of the repo README
• Upgrading from v1.1: close the old window and replace the exe; data files (cookie, comment inventory) carry over

BiliCommentManager v1.1

B 站评论管理器（黑历史管理器）首个公开发布：扫码登录、全量拉取、时间段筛选、低频删除。

下载 / Download

• BiliCommentManager.exe（约 22MB）：下载后双击即用，无需安装 Python 或任何依赖（Windows 10/11）
• 首次运行可能出现 SmartScreen 蓝色警告——未签名 exe 的常态，点「更多信息 → 仍要运行」
• 数据文件生成在 exe 同目录，整个文件夹拷走即迁移

快速上手 / Quick Start

1. 双击 exe，原生应用窗口自动打开
2. 点「扫码登录」→ 二维码弹出 → 手机 B 站 App 扫码确认
3. 点「重新拉取」→ 后台拉取全部评论（因接口限流约 1 小时，可关窗）
4. 时间段/类型/关键词筛选 → 「保留」想留的评论 → 「开始删除」（低频防风控，实时进度，可停可续）
5. 「查看全量评论」→ 只读快照，不随删除变化，删完仍可回看完整历史

注意 / Notes

• 删除不可恢复；删除前全部评论内容已留档在 exe 同目录的 my_comments.json
• 评论列表依赖第三方索引 AICU，部分网络环境可能不可达（此时无法列出评论，但已列出评论的删除不受影响）
• Cookie 只存本地、只发送给 api.bilibili.com；源码部署与工作原理见 README

---

First public release of the Bilibili comment & black-history manager: QR login, full-history fetch, time-range filtering, paced bulk deletion.

• BiliCommentManager.exe (~22MB): double-click to run — no Python, no dependencies (Windows 10/11). Expect a SmartScreen warning on first run (unsigned exe): "More info → Run anyway".
• Deletion is irreversible; the full inventory is archived locally (my_comments.json, next to the exe) before any deletion.
• Comment listing relies on the third-party AICU index, which may be unreachable on some networks (listing fails; deleting already-listed comments still works).
• Your cookie stays local and is only ever sent to api.bilibili.com. For source deployment and how it works, see the README.