GitHub 永久封禁了我的账号,原因是使用 Actions 验证 VPN 节点。

1作者: shray883 天前
我是一名来自俄罗斯的 20 岁兽医学生,正在开发反审查工具。2026 年 3 月 17 日,GitHub 永久封禁了我的账户,理由是违反了与 GitHub Actions 相关的服务条款。 **项目** Raccoon Squad VPN — 一个基于 Xray-core 的 Android VPN 客户端,为俄罗斯用户提供 DPI 绕过功能。支持 VLESS、VMess、Trojan、Shadowsocks、Hysteria2、TUIC。完全由人工智能辅助构建,历时数月。 源代码:https://gitlab.com/shray77/rsquad **Actions 的作用** 我有一些仓库,用于聚合和验证来自公共来源的免费 VPN 节点: * hpp:Python 抓取器 — 获取节点列表,按 VLESS XTLS 的 SNI 筛选,验证格式,TCP ping。每 6 小时运行一次,耗时约 30 分钟。 * node-filter:Go L7 检查器 — 通过 Xray 连接,验证握手,下载 2MB 测试文件,测量速度。每 1 小时运行一次,耗时约 30 分钟。 * loshad-scoc:搜索新来源 — 50 多个 GitHub dork 查询,15 个 PAT 令牌轮换,HuggingFace API 验证。 * zhopa-bobra:SNI 流行度分析器。 关键事实:没有挖矿,没有密码破解,没有繁重的计算。节点来自公共 raw.githubusercontent.com 列表。网络软件的标准 CI/CD 验证。Actions 每天总共运行约 1 小时。 **时间线** 2 月 26 日:因“涉嫌入侵”被封禁 — 已恢复。 2 月 27 日:因“垃圾邮件标记”被封禁 — 已恢复。 2 月 27 日:仓库 rsquad 被封禁 — 被要求设为私有。 2 月 27 日:raccoon-release 被封禁 — 无法遵守:被锁定。 3 月 2 日:GitHub 要求我删除仓库。我仍然无法登录。 3 月 17 日:提交正式法律申诉(7 页),抄送 legal@github.com。 3 月 17 日:大约 70 分钟后 — 永久封禁。 **进退两难** GitHub 要求我删除仓库以解决封禁问题。但由于账户已被封禁,无法登录。我多次告知了支持团队。没有得到解决。 **他们扣押了我的代码** 我无法访问我的仓库。无法导出。没有备份。GitHub 实际上扣押了我的知识产权。根据 GDPR 第 20 条,我有无条件的数据可移植权。GitHub 拒绝遵守。 这实际上是盗窃知识产权。我编写的代码被锁在他们的墙后,没有任何法律依据可以保留。 **违反 GDPR** 第 20 条赋予数据可移植权。我被锁定,没有导出选项。除了自动工单外,DPO 请求未得到回复。 **当前状态** * 已提交 FTC 投诉 * 已联系 DPO — 只有自动工单号 * 项目已迁移到 GitLab:https://gitlab.com/shray77/rsquad 我分享这些是因为执行是武断的,过程缺乏透明度,当平台做出自动化决策时,开发人员无处申诉。
查看原文
I&#x27;m a 20-year-old veterinary student from Russia developing anti-censorship tools. On March 17, 2026, GitHub permanently suspended my account citing Terms of Service violations related to GitHub Actions.<p>THE PROJECT<p>Raccoon Squad VPN — an Android VPN client based on Xray-core with DPI bypass for Russian users. Supports VLESS, VMess, Trojan, Shadowsocks, Hysteria2, TUIC. Built entirely with AI assistance over several months.<p>Source: https:&#x2F;&#x2F;gitlab.com&#x2F;shray77&#x2F;rsquad<p>WHAT THE ACTIONS DID<p>I had repositories that aggregated and validated free VPN nodes from public sources:<p>- hpp: Python scraper — fetched node lists, filtered by SNI for VLESS XTLS, validated format, TCP ping. Every 6 hours, ~30 min runtime.<p>- node-filter: Go L7 checker — connected via Xray, verified handshake, downloaded 2MB test file, measured speed. Every 1 hour, ~30 min runtime.<p>- loshad-scoc: Scout for new sources — 50+ GitHub dork queries, 15 PAT tokens with rotation, HuggingFace API validation.<p>- zhopa-bobra: SNI popularity analyzer.<p>Key facts: No mining, no password cracking, no heavy computation. Nodes from public raw.githubusercontent.com lists. Standard CI&#x2F;CD validation for network software. ~1 hour Actions runtime per day total.<p>TIMELINE<p>Feb 26: Suspended for &quot;suspected compromise&quot; — restored. Feb 27: Suspended for &quot;spam flag&quot; — restored. Feb 27: Suspended for repository rsquad — asked to make private. Feb 27: Suspended for raccoon-release — COULD NOT COMPLY: locked out. Mar 2: GitHub demanded I delete repos. I still couldn&#x27;t log in. Mar 17: Filed formal legal appeal (7 pages), CC&#x27;d legal@github.com. Mar 17: ~70 minutes later — permanent ban.<p>THE CATCH-22<p>GitHub demanded I delete repositories to resolve the suspension. But the account was suspended, preventing login. I informed support multiple times. No resolution.<p>THEY ARE HOLDING MY CODE HOSTAGE<p>I have no access to my repositories. No export. No backup. GitHub is effectively holding my intellectual property hostage. Under GDPR Article 20, I have an unconditional right to data portability. GitHub is refusing to comply.<p>This is, de facto, theft of intellectual property. The code I wrote is locked behind their wall with no legal basis for retention.<p>GDPR VIOLATION<p>Article 20 grants right to data portability. I&#x27;m locked out with no export option. DPO request unanswered beyond automated ticket.<p>CURRENT STATUS<p>- FTC complaint filed - DPO contacted — only automated ticket number - Project migrated to GitLab: https:&#x2F;&#x2F;gitlab.com&#x2F;shray77&#x2F;rsquad<p>I&#x27;m sharing this because enforcement was arbitrary, the process lacked transparency, and developers have no recourse when platforms make automated decisions.