@imnpc 谢谢

@imnpc 国际站的轻量有 CN2 吗？想买一个 200Mbps 款的但不清楚线路质量，众说纷纭

《实 习 生》（狗头

双持，没有不习惯一说

海外 Cloudflare+内地 EdgeOne ，关键词“edgeone 国内外分流”

没有，至少到今年 8 月的镜像

google 不验证卡的发行国家，所以随便选

@allendavis #85 很好看！礼貌请教一下大概是怎么配置的？

推荐试试楼上推荐的 manjaro ，保留了 arch 一些特性的同时稳定性也不错，也没有那么折腾

内网穿透/Zerotier/TailScale/EasyTier

@MYDB 国产软件基本上都命中了（ doge

我开 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

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