https://linux.do/theme-Javascripts/d8897e3df35c565bfe07d668018107001716b9b4.js

```js
var i=a(e=>{const t=e.getCurrentUser()
if(!t)return
const a=t.username,i=s.watermark_intensity,n=s.watermark_density,o=s.watermark_angle,l=window.devicePixelRatio||1,d=r("<div>").css({fontSize:`var(${s.watermark_font_size_var})`,fontFamily:`var(${s.watermark_font_family_var})`,position:"absolute",visibility:"hidden"}).appendTo("body"),c=d.css("fontSize"),u=d.css("fontFamily")
```

@wKong753900 #5 https://github.com/marlock9/edge-debloat

https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository#fully-removing-the-data-from-github

Contact us through the GitHub Support portal, and provide the following information:

The owner and repository name in question (e.g. YOUR-USERNAME/YOUR-REPOSITORY).
The number of affected pull requests, found in the previous step. This is used by Support to verify you understand how much will be affected.
The First Changed Commit(s) reported by git-filter-repo (Look for NOTE: First Changed Commit(s) in its output.)
If NOTE: There were LFS Objects Orphaned by this rewrite appears in the git-filter-repo output (right after the First Changed Commit), then mention you had LFS Objects Orphaned and upload the named file to the ticket as well.

If you have successfully cleaned up all references other than PRs, and no forks have references to the sensitive data, Support will then:

Dereference or delete any affected PRs on GitHub.

Run a garbage collection on the server to expunge the sensitive data from storage.

Remove cached views.

If LFS Objects are involved, delete and/or purge the orphaned LFS objects.

Important

GitHub Support won't remove non-sensitive data, and will only assist in the removal of sensitive data in cases where we determine that the risk can't be mitigated by rotating affected credentials.

最佳实践是 Windows 11
次选 Windows 10 ESU 原位到 2028
再次选重装 Windows 11 IoT Enterprise LTSC 2024

这里几乎没有医生，期待随机网友能对一个疾病做出准确的、有参考价值的描述是不可能的。

https://www.msdmanuals.cn/professional/psychiatric-disorders/mood-disorders/depressive-disorders

本报告记录了我们对这一短暂但广泛的封禁事件的测量与分析。主要发现如下：

1. 无条件的 `RST+ACK` 注入仅发生在 TCP 443 端口，未见于其他常见端口（如 22 、80 、8443 ）。
2. 该无条件注入同时扰乱了出入境中国双方向的连接，但触发机制**不对称**：从中国境内向境外发起的连接，客户端的 `SYN` 包与服务器的 `SYN+ACK` 包各自触发三个 `RST+ACK`包；从境外向中国境内发起的连接，只有服务器返回的 `SYN+ACK` 会触发 `RST+ACK`，客户端发送的 `SYN` 不会触发注入。
3. 负责注入的设备指纹与已知 GFW 设备不匹配，因此**此次事件要么由新的 GFW 设备造成，要么是由已知设备以一种新的或误配置的状态运行造成的**。

aHR0cHM6Ly9nZncucmVwb3J0L2Jsb2cvZ2Z3X3VuY29uZGl0aW9uYWxfcnN0XzIwMjUwODIwL3poLw==

@issakchill https://linux.do/t/topic/773333

@abchendai00 对明确已知被墙的域名做 traceroute 时，应该使用 sudo traceroute -T -p 443 example.com ，因为墙不会影响 ICMP 。实际测试是在国内中断的。

Free Plan ，只有一个之前有记录的 xyz 有这个情况。

另一个 xyz 临时添加了记录，没有问题。其余域名，包括免费的，临时添加记录，都没有问题。

个人认为是 Cloudflare 的技术调整，毕竟配合极权政府进行审查是一个巨大丑闻。

v2ex.com###pro-campaign-container

@管理员 /go/pointless

/go/pointless