然而收信并不能保号🤣

美国 IP 访问，可加入 waitlist 。

hey, here’s an invite to Arc, the browser I was telling you about!

https://arc.net/gift/83253498

hey! here’s an invite to Arc, the browser I was telling you about -

https://arc.net/gift/9a435626

刚在 Hack News 上看到 BBEdit 30 岁啦。

https://grahamrpugh.com/2021/04/06/delete-system-extension-command-line.html

用这个。直接把 filter 删了，kext 也会一起删除。

@h4lt #9
找到问题了。我之前用 brew 安装了 gnu-sed 。
手动指定 /usr/bin/sed 即可。

感谢。

@gettoset #7
安装路径是没问题的。
前面的 md5sum 、备份以及 codesign 都已经通过。
sed 那一步报错了。

./Wechat: replacing existing signature
sed: can't read s/\(\x89\x4D\xC4\x48\x8B\x5E\x08\x48\x85\xDB\)\x74/\1\xEB/g: No such file or directory
The application cannot be opened for an unexpected reason, error=Error Domain=NSOSStatusErrorDomain Code=-10661 "(null)" UserInfo={_LSLine=3746, _LSFunction=_LSOpenStuffCallLocal}

脚本报错了怎么解决呢

之前咸鱼科技的翻车了。现在还有哪家在卖吗？

遇到同样问题。
请问有人解决了吗？

How are DNS over TLS and DNS over HTTPS different?

Each standard was developed separately and has its own RFC* documentation, but the most important difference between DoT and DoH is what port they use. DoT only uses port 853, while DoH uses port 443, which is the port that all other HTTPS traffic uses as well.

Because DoT has a dedicated port, anyone with network visibility can see DoT traffic coming and going, even though the requests and responses themselves are encrypted. In contrast, with DoH, DNS queries and responses are somewhat camouflaged within other HTTPS traffic, since it all comes and goes from the same port.

Ref: https://www.cloudflare.com/learning/dns/dns-over-tls/

哇这个 lan-play 简直开启了新世界大门。
原来 switch 还能这么玩的。

https://www.scss.tcd.ie/Doug.Leith/pubs/browser_privacy.pdf

丢一个隐私报告就跑

@g67261831 #70 所以手机更新是不影响的吗？