我开 ticket 收到了回复：

Hi there,

（省略套话）

As a workaround, if you're familiar with the GitHub CLI, you can use the script below to mark all of your notifications as read. This may take care of the phantom message, but please note that the 1-0 of 1 message may still persist after the curl command is run. Our engineers are investigating this bug as well.

Running the script to mark notifications as "read" is generally considered safe, as it does not remove the notification itself, only updates the status of the notification. Here is the script:

gh api \
--method PUT \
-H "Accept: application/vnd.github+json" \
/notifications \
-F read=true

If you have a Personal Access Token (PAT), you can also use the following curl command to mark all of your notifications as read. Please note that in order to use the curl command, you will need to replace $TOKEN with your own PAT, which you can create here. Also note that the PAT must have the notifications scope.

curl -X PUT \
-H "Accept: application/vnd.github.v3+json" \
-H "Authorization: token $TOKEN" \
https://api.github.com/notifications

For your reference, here is the documentation for the Notifications REST API endpoint.

（省略套话）

Thanks,

xxx
GitHub Support

@MrVito 帮到你了就好😂我的 pro 2 可以直接用视频里的方法开

我参考的是这个视频 https://www.bilibili.com/BV1aH4y1j7HW

@zqguang3708 Windows 有定位权限啊，给微信授权了小程序大概率可以直接用的

祝好！

生日快乐

匪警请拨 110

我还以为是自己的网络问题

N26 必须从 app 里加

ETYPPLWJX377 已用

可能是过敏性鼻炎，可以去医院做一个过敏原检测然后开点药

啊？？

@ZhiyuanLin 有道理，但 http 就是更容易被篡改，比如说上面提到的重放攻击。而且不一定需要篡改，能看到你看的内容也足够建立一个用户画像了

@ZhiyuanLin 如果下发的 sha256 也在 http 里被篡改了呢

@zqqian 这种情况很显然三字经也有点救不了（狗头

不能，试试申请换发吧

@NoString 点赞了，但是历史文件不具有现实意义😂