# For people afraid of account bans, they moved Claude Code onto a VPS: how cc-desk-tunnel got 364 stars from a single L-site post · GitHub open-source project

> Source: https://stringers.io/en/github/gh_sun168567__cc-desk-tunnel.html (Stringers / 什么值得做, generated 2026-11-08)
> Stringers answers one question every day: what small product can one or two people build in a few months and actually make money from. Numbers come from 15 databases we collect daily, each with source and date.
> For agents: these verdicts and the underlying databases (verified revenue, App Store / Google Play charts, ad libraries, GitHub, Product Hunt…) are queryable live over MCP — tools today / hot / products / directions / direction / data. Setup: https://github.com/komako-workshop/stringers (the user logs in at stringers.io → "配置 agent" to get a personal URL). Site index: https://stringers.io/llms.txt

> Chinese developers feared getting Claude banned for running it locally, so they moved it to overseas VPS boxes, but the experience was poor. This project filled the "Claude on the VPS, work done locally" gap, and spread through a linux.do post with 371 likes and later tutorial citations.

[GitHub open-source project](https://stringers.io/en/github/index.md) · written 11-6

sun168567/cc-desk-tunnel · sun168567

# For people afraid of account bans, they moved Claude Code onto a VPS: how cc-desk-tunnel got 364 stars

**What it is** An open-source desktop client that runs Claude Code on an overseas VPS while directly editing code and running commands on your own Windows PC.

**Why it took off** Chinese developers feared account bans from using Claude locally, so the popular move was to install it on an overseas VPS, but the experience was poor. This tool fills the gap of "Claude on the VPS, work on the local machine." It spread through a linux.do post with 371 upvotes and later tutorials citing it.

**C** **How you could follow it** Don't copy it head-on. Learn from its posting strategy on linux.do, and build the parts of the anti-ban setup it did poorly: for example, the structured Windows local tool users asked for in issues, or a VS Code / Cursor plugin form.

C grade: the playbook is clear and worth learning, but the position is already held by a fast-iterating author. The need exists only inside the Chinese anti-ban circle, the star ceiling is low, and Anthropic's rule changes could upend it at any time. Spreading in small circles

Data (updated daily) · Repo created 2026-10-07 · 381 stars · 7 days +114

GitHub · stars

Data 2026-10-09 → 2026-11-08 (31 days, 31 observations). Points before 10-28 come from deeply / archive backfill, not every day has one

A single-repo author with 5 followers created the repo in Oct 7, posted on linux.do 5 hours later, and within 30 days got 364 stars and 70 forks. The installer was downloaded about 13k times. English-speaking developers barely knew it. It took off because of a very specific anxiety among Chinese developers using Claude: fear of being banned.

### A post with "Fenjue" (焚决) in the title

On Oct 2026 7 afternoon (Beijing time 16:23), an open-source promo post titled "[Open Source] Ditch Claude's old playbook -- run Claude Code in the cloud directly on your local projects (lower account-ban risk)" appeared on linux.do. By Nov 6 it had 371 likes and 160 replies.

The author explained where he came from: he had been splitting an OpenAI Pro account with others, but "over the last month things have been rough, with dumbed-down models and cut quotas popping up everywhere." He couldn't resist opening a Claude account, and was "blown away after using opus5.5." But "because of the well-known Claude ban problem," he didn't dare install Claude Code on his own machine, so he moved it to an overseas VPS.

A few days in, problems appeared: remote desktop needed a beefy VPS, code had to be shuttled back and forth, and whenever debugging needed the local intranet environment, the VPS didn't have it, so he had to "develop with claude, copy back locally, then have codex debug. The experience was just awful."

So he built CC Desk Tunnel: Claude Code runs unchanged inside Docker on the VPS, with model requests and login both going out from the server. A desktop client on your PC handles chat and project selection. A reverse SSH tunnel then lets the remote Claude Code read and write files and run commands directly on your Windows machine. In his words, it feels "close to installing claude code directly on your machine," and "the VPS can be a low-spec box, so mom doesn't have to worry about my tiny chick (VPS slang for a small server) not being powerful enough."

He also wrote: "I've opened a new account and have been testing it for a week, and the account is still alive."

### How the numbers moved

| Date | star | fork |
|---|---|---|
| 10-17 | 180 | 35 |
| 10-26 | 223 | 44 |
| 11-01 | 267 | 52 |
| 11-03 | 307 | 56 |
| 11-06 | 364 | 70 |

(GitHub, daily stars / forks)

It got half its stars in the first 10 days, with the biggest single day on Oct 11 at +33. It then slowed, with only single-digit daily gains in late October. Starting Nov 2 it picked up again, with 13 to 27 a day for five straight days. The last 7 days added 106, more than double the previous 7 days (39). There's no direct data on where the second wave came from; the author swapped new screenshots into the original post around Nov 2 (the new multi-platform client and terminal ccdt), and the timing lines up (inference).

Two numbers say more than stars. First, forks: 70, roughly 19% of stars, far above what similar-sized repos usually see, so many people actually deployed it. Second, downloads: the release packages on GitHub Releases total about 13k downloads, and v0.3.6, released on Oct 22, alone has 3,307 (GitHub, 11-06; how many are repeat downloads from auto-updates is unclear).

In 30 days the author shipped more than 20 versions, from v0.2.4 to v0.3.13, with issue and PR numbers reaching #177, mostly opened by himself (with AI). On Nov 4 one user left a long piece of feedback that opened with "Overall the experience is great, it has replaced my previous remote tool setup," then listed five suggestions, one being a structured file-and-command toolkit for Windows, "similar to the Desktop Commander project."

### Where users come from

Almost all of it came from this one community, linux.do.

**The original post was the main channel.** It went up 5 hours after the repo was created, following L-site's "open-source promotion" rules to the letter: tagged, fully open source declared, README linking back to the community, AI-written intro with screenshots. The title's "ditch" and "playbook" are L-site slang, and "lower ban risk" hits the community's collective anxiety head-on. It was picked up the same day by a newsletter, "Linux.do AI Frontier & Freebies Evening Digest."

**Other people's tutorials treat it as standard practice.** On Oct 31, another user posted "[Tutorial/Hands-on] Windows, practical Claude Pro use, two routes" with 38 likes, listing "CC Desk Tunnel + dual SSH" as Route 1. On Nov 5, a help thread asking "how to elegantly use a friend's Claude on their overseas computer" got a reply recommending it.

**It was also posted on NodeSeek.** The same title went up on NodeSeek, where VPS hobbyists gather and already have spare "chicks" (small servers).

**English-speaking world: nothing.** Searching the project name on X turns up 40 posts in the last 0 days, and no media coverage. No sign of paid acquisition, star-buying, or influencer promotion.

### Why it took off at this moment

**Ban avoidance is a heating-up topic.** Around the same time, GitHub repos related to "Claude ban avoidance" were piling up: check-cc with 2,821 stars, +471 in the last 7 days; Claude-Guardian, created Oct 15, with 1,761 stars and +487 in 7 days; plus Claude-anti-ban (457 stars) and anti-claude (created Oct 22). One of the ban-avoidance "playbooks" circulating on L-site is "install Claude Code on an overseas machine and use it remotely."

**It fills the last gap in this makeshift method.** People were already running Claude Code on VPSes; the pain was the experience: VPSes needed high specs, toolchains had to be reinstalled, code had to be synced, local intranet and desktop software were unusable, remote desktop lagged, and Chinese input was clunky. It solved all of this at once, and only needs one low-spec VPS.

**It isn't confronting anyone.** The README repeatedly stresses "no changes to the official CLI, no adversarial tactics, the server's location is the place of use," with account and security notices attached. The original post also honestly says "the project is mainly vibe coding," "no guarantee the account won't be banned," and "the server must be one you control and trust, because once connected it can directly operate your local computer." For a tool that is essentially remote control, this framing lowers wariness.

**The install barrier is very low.** The server side deploys with a single curl command, and later there was a prebuilt Docker image. The Windows installer bundles OpenSSH and PowerShell 7, and the client can upgrade both ends with one click. The 0.2.10 release dropped frpc, which antivirus software often flagged as malware.

### Who it's competing with

| Project | Scale | How it differs |
|---|---|---|
| farion1231/cc-switch | 152k stars | Switching model providers and relays; the largest install base in the Chinese-speaking world, regardless of which machine Claude Code runs on |
| slopus/happy | 24.5k stars | Remotely controlling local Claude Code from your phone; the direction is the opposite |
| winfunc/opcode | 22.4k stars | A graphical shell for local Claude Code |
| siteboon/claudecodeui | 14.4k stars | Remotely operating Claude Code on a given machine from web or phone; code and execution on the same machine |
| DesktopCommanderMCP | 10.2k stars | Giving Claude local terminal and file access |
| check-cc / Claude-Guardian / Claude-anti-ban | 2.8K / 1.7K / 457 star | Making detection and ban-avoidance guides, not a development workbench |
| The official Claude Code desktop app's SSH | Official | Claude Code and the code both live remotely; no split where the exit is on the VPS and execution is local |
| Remote desktop or VS Code Remote-SSH into a VPS | Lots of tutorials on L-site and YouTube | These makeshift methods are exactly what it replaces |

(GitHub stars, early November)

Other tools let a person remotely operate an agent; this one lets the remote agent operate the person's computer. As far as I can tell, it's the only one that does this split and also ships a proper GUI.

But this split barely makes sense without the ban angle: overseas users can just install Claude Code locally. That's also why it has no English-speaking buzz. Its ceiling is the group in the Chinese-speaking world willing to tinker with VPSes.

People are already building on it: one fork added an external terminal CLI with 7 stars and was merged back upstream; a proxy vendor reached out in an issue to pitch a sponsor slot in the README, because many people in the thread were asking whether the VPS exit should be routed through residential broadband.

### If it were you

**One-line verdict:** the project's playbook is worth learning, but building another one just like it will struggle to get the same stars. The spot is already held by an author iterating fast, and the whole topic's ceiling sits inside the Chinese ban-avoidance circle, under a platform rule that could change at any time.

**Who it suits:** developers already hanging out on linux.do and NodeSeek, who are the "afraid of bans but still want Claude" people themselves, and who can see what's still missing along this route.

**Who it doesn't suit:** people who want to build a global project that steadily gains stars over time; people unfamiliar with the norms and slang of Chinese developer communities; people unwilling to take on the security responsibility of a "remote control" tool.

**How to do it:**

1. Don't copy it head-on. It already has Windows, Linux, and macOS clients plus a terminal version, with more than 20 versions shipped in 30 days. A latecomer with no differentiation is just a runner-up.

2. Do the part it hasn't done well. Users have already written the requirement in issues: a structured Windows local toolkit for remote agents (read, write, search, validated transfers, a persistent PowerShell session). It could be a standalone open-source project that works with this tool and with other remote agents.

3. Or change the form factor: the same "exit on the VPS, execution local" split, delivered as a VS Code / Cursor extension instead of a standalone desktop client, for people who don't want to open yet another app.

4. Copy its framing: don't modify official programs, don't fight the platform, and state account and security risks clearly.

**How to get users:** Walk its path: on the day the repo is created, post on linux.do under the "open-source promotion" rules, with a title that names the specific anxiety it solves, in the community's own words; cross-post to NodeSeek; after each major update, swap screenshots into the original post to bump it, and reply under the "ban-avoidance route" tutorial threads. The English-speaking world takes no effort.

**When it was before its time:** This wave of "OpenAI users moving to Claude while worried about bans" began around 2026 9 and October and is still heating up. The window you can work with is probably the next month or two (estimate).

**What would show I'm wrong:** If Anthropic tightens rules on third-party tools or login methods, or if people on L-site start saying "even with the VPS setup you still get banned," the topic's reputation could flip overnight. If cc-desk-tunnel's daily gains quickly drop back to single digits, that means the November wave was just bump-driven, not growing demand.

[GitHub repo ↗](https://github.com/sun168567/cc-desk-tunnel)

**Research notes: competitor table, acquisition evidence, full research report**

Competitors

| Name | Where | Launched | Scale | How it differs from this one |
|---|---|---|---|---|
| siteboon/claudecodeui (CloudCLI) | Open source | 2025-06 | 14.4k stars | Remotely operating Claude Code on a given machine from web or phone; execution and code on the same machine, no split back to local |
| slopus/happy | Open source | 2025-07 | 24.5k stars | Remote-controlling local CC from a phone; opposite direction, doesn't solve the exit problem |
| winfunc/opcode | Open source | 2025-06 | 22.4k stars | A GUI shell for local CC; doesn't involve a VPS |
| farion1231/cc-switch | Open source | 2025-08 | 152K stars | Switching providers or relays; doesn't run CC on an overseas machine |
| Claude Desktop SSH / self-hosted environment runners | Big-company features | 2026 | Official | Official SSH keeps code and CC on the same remote side; no split with the exit on the VPS and execution local |
| Remote desktop / VS Code Remote-SSH into CC on a VPS | Other | — | Lots of ban-avoidance tutorials on L-site/YouTube | Moving the project and toolchain onto a VPS that needs high specs and gives a poor experience is exactly the approach it replaces |
| check-cc / Claude-Guardian / Claude-anti-ban | Open source | 2026-06~10 | 2.8k/1.7k/457 stars | Makes environment detection and ban-avoidance guides, doesn't provide a development workbench |
| Qiao-920/claude-desktop-cn | Open source | 2026-04 | 270 stars | A Chinese-language CC desktop client that runs locally |

Where users come from

- **Verified** **Open-source promo post on linux.do** : 5 hours after the repo was created on 2026-10-07, a post titled "Claude Stealth Mode…Lower Account Ban Risk" went up. It got 371 likes and 160 replies. The same day it was picked up in Linux.do's AI evening digest.

- **Verified** **cited in community tutorials** : linux.do 10-31 "Hands-on Claude Pro, two routes" lists CC Desk Tunnel as Route 1; recommended in 11-05 help-thread reply; Hai News rewrite

- **Verified** **cross-posted on NodeSeek** : nodeseek post-968775 with the same title

- Inference **author's bump with updated screenshots drove a second star wave** : the original post includes 2026-11-02 screenshots, and the daily gains of 13–27 from 11-02 line up

- Inference **X / English-speaking world** : x-radar shows 0 posts in the last 40 days

## sun168567/cc-desk-tunnel: why it took off

> Data as of: 2026-11-06. Stars and star growth come from our GitHub repo tables (repo_profile / repo_day) and the data card; download counts and issues are pulled live from the GitHub API; community evidence comes from the original linux.do / nodeseek threads (read via Jina).

### One line

A desktop client plus server (reverse WSS/SSH tunnel) that lets Claude Code run on an overseas VPS while reading and writing files and executing commands on your own Windows PC. It took off because **it rode the Chinese-speaking "Claude anti-ban" wave** : Chinese users feared getting banned for running CC locally, so they moved CC to a VPS. But the dev experience there is poor, and this project fills the gap of "CC on the VPS, project stays local." Nearly all its traffic came from one open-source promo post on linux.do.

### 1. Data

- Stars: repo created 2026-10-07,30 days ago with 364 stars (live from GitHub: 373), 70 forks (fork/star ratio about 19%, far higher than repos of similar size, which suggests many people actually deployed it). The author has only this one repo and 5 followers (GitHub API).

- Curve (data card, daily): 10-17 had 180 stars, so half came in the first 10 days after the post. The single-day peak of 33 stars landed on 10-11 (day 4 after the post). From 10-17 to 10-26 it grew only 0–15 a day; **it re-accelerated from 11-02** : 11-02 +13, 11-03 +27, 11-04 +19, 11-05 +21, 11-06 +17. Last 7 days +106, the 7 days before that +39 (status in the repo table: "accelerating").

- Installer downloads (sum of asset downloads across GitHub Releases, pulled live): about 13k. v0.3.6 (10-22) 3307 downloads, v0.3.7 (10-27) 2621 downloads, v0.3.4 1892 downloads. Downloads run about 35× the star count, so far more people are actually using it than stars suggest.

- Iteration speed: 30 days, more than 20 releases (v0.2.4 → v0.3.13), issue/PR numbers have reached #177, mostly PRs the author opened with AI help. External PRs include Kimi-Bo (#139, external terminal CLI), uiwcvb (#137), and xiaobaifly7 (#164).

### 2. Where users came from (growth tactics)

1. **linux.do open-source promo post (main channel, confirmed)** : "[Open Source] 蹬Claude的新焚决 -- Run Claude Code in the cloud, develop your local project directly (lower ban risk)", published 2026-10-07 08:23 UTC, only 5 hours after the database was built; **371 likes, 160 replies** (https://linux.do/t/topic/2990573). The title uses L-site slang 「焚决」 and 「蹬」, and leads with "lower ban risk". The README and code link back to the community per L-site open-source promo rules. Same day it was picked up by the "10-07 Linux.do AI Frontier & Freebie Evening Digest" (Jina search results).

2. **Author kept updating the original post, driving repeat spread** : the post has new screenshots from 2026-11-02 (GUI, account page, ccdt), showing the author bumped and updated the thread with ccdt and the multi-platform clients around 11-02. This lines up with the second wave of stars from 11-02 (inference; timing matches, no direct click data).

3. **Other users' tutorials treat it as the standard setup (confirmed)** : the linux.do post "[Tutorial/Hands-on] Windows, using Claude Pro in practice, two routes (VM with two-way SSH / strict proxy rules)" (10-31,38 likes, [linux.do/t/topic/3102523](https://linux.do/t/topic/3102523)) lists "CC Desk Tunnel + dual SSH" as Route 1; 11-05's reply in "Asking the bros how to elegantly use a friend's overseas computer for Claude" (https://linux.do/t/topic/3126935) also recommends it; Hai News rewrote the "Windows Claude Pro dual-route tutorial." A separate post, "Sharing two Claude Pro setups," cites the same architecture.

4. **Cross-posted on nodeseek (confirmed)** : same title on nodeseek (https://www.nodeseek.com/post-968775-1). nodeseek is a VPS-enthusiast community, where users already own "小鸡" (cheap VPS boxes).

5. **Passive pickup by aggregator sites** : trendshift, RepoMasters, nicheloom (122 upvotes, from search snippets, unverified).

6. **X / English-speaking community: none** . x-radar results for "cc-desk-tunnel" and "CC Desk Tunnel" over the last 40 days: 0 posts each. It hasn't made trending (repo is under 60 days old).

No sign of ads, influencers, or bought stars: the high fork ratio, large download count, external PRs, and detailed feedback issues (#165) all look like real users.

### 3. Why it took off

- **Demand is real and rising** : Chinese users have made "fear of getting banned for using Claude Code" a theme. Around the same time, a whole cluster of "anti-ban" repos appeared: yacuo/check-cc at 2821 stars (+471 in 7 days), DUNHKpcc/Claude-Guardian at 1761 stars (created 10-15, +487 in 7 days, also covers a VPS approach), Fishason/Claude-anti-ban at 457 stars, sunreview/anti-claude at 85 stars (created 10-22). One of the popular anti-ban "焚决" on L-site is to install CC on an overseas machine and use it remotely.

- **It solves the last pain point of that anti-ban approach** : once CC moves to a VPS, you have to reinstall the toolchain there, buy a high-spec machine, and keep syncing code back and forth. Local intranet, emulators, and desktop software are all unusable; remote desktop lags, and Chinese input is awkward. The original post describes these pain points in detail. It lets "model requests go out from the VPS, commands run locally," and a 2-core 1G VPS is enough, which fits the "小鸡" that linux.do and nodeseek users already own.

- **Timing** : the author wrote that "OAI pro shared-account pooling has been shaky the past month" and "after using opus5.5 I was blown away." That is 2026 year 9–October, when a group of Chinese developers were switching from ChatGPT/Codex to Claude while worrying about bans.

- **Low barrier to entry** : the server deploys with one curl command (prebuilt dual-arch ghcr images from 10-27/11-01 on); the Windows installer bundles OpenSSH and PowerShell 7; the client upgrades both ends in one click. 0.2.10 also dropped frpc, which antivirus software often flagged as a false positive.

- **Stable positioning** : the README repeatedly states "does not modify the official CLI, no adversarial tactics, the server's location is the place of use," and includes account and security notes. That lowers L-site users' wariness of "unknown remote-control tools."

### 4. Competitors

| Name | Where | Launched | Scale | How it differs |
|---|---|---|---|---|
| siteboon/claudecodeui (CloudCLI) | Open source | 2025-06 | 14.4k stars | Remotely operate CC that runs on a given machine from a phone or web page; code and execution stay on the same machine, not split back to local |
| slopus/happy | Open source / app | 2025-07 | 24.5k stars | Remotely control CC/Codex on your local machine from a phone; the direction is reversed: CC runs locally |
| winfunc/opcode (formerly claudia) | Open source | 2025-06 | 22.4k stars | A GUI shell for local CC; no VPS or egress involved |
| farion1231/cc-switch | Open source | 2025-08 | 152K stars | Desktop tool for switching providers and relays, with the largest install base in the Chinese community; does not solve "CC runs overseas" |
| Qiao-920/claude-desktop-cn | Open source | 2026-04 | 270 stars | Chinese-language CC desktop client, runs locally |
| DesktopCommanderMCP | Open source | 2024-12 | 10.2k stars | An MCP that adds local terminal and file capabilities to Claude; the user in #165 wants cc-desk-tunnel to add structured tools in that direction |
| Claude Desktop / Claude Code desktop apps ship with built-in SSH and a self-hosted environment runner | Big-company features | 2026 | Official | Official SSH is "local UI + CC runs remotely + code also remote"; the runner lets claude.ai sessions run on your host. Neither splits it as "CC egress on the VPS, execution local" |
| Remote desktop / VS Code Remote-SSH / Termius connecting to CC on a VPS | Other (tutorial setups) | — | Lots of tutorials on L-site and YouTube | It directly replaces this kind of setup: code has to live on the VPS, and the experience is poor |
| check-cc, Claude-Guardian, Claude-anti-ban, claude-ip-guard, claude-code-relay | Open source (anti-ban theme) | 2025-08 to 2026-10 | 74 to 2.8k stars | Do detection, guides, or relays; none provide a dev workbench |
| Belay | Other | 2026-11 | Post on Linux.do titled "Sharing an elegant, safe tool for using your Claude account: Belay" (now 404 or made private) | Also runs CC on a VPS; details unverified |

Bottom line: the "Claude anti-ban" space has many competitors, but **the only one I've found that specifically splits "CC on the VPS, execution back on local Windows" and ships a polished GUI is this one** .

### 5. Differentiation

- The core difference is **splitting "model egress" and "execution environment" across two machines** : Claude's requests and login state stay on an overseas server you control, and tool calls reverse-SSH back to the local machine to run. Other remote tools let a person operate an agent remotely; this one lets the agent operate the person's computer remotely.

- That difference is exactly why it took off, because it fits the anti-ban need hand in glove: users want a clean egress and local development at the same time. Without the anti-ban motive, putting the agent remote and execution local means little to most people (overseas users can just install CC locally). That also explains why it has had little traction in the English-speaking world.

- Secondary differences: the GUI groups by project, collapses process output, and shows quota; the ccdt terminal client and the GUI share sessions; Windows comes first (most Chinese developers use Windows, while most comparable tools are macOS-first).

### 6. Visibility and copycats

- Visibility: **it's spreading inside small circles** . It's already well known on linux.do (a post with 371 likes, cited by several tutorials) and has traction on nodeseek too, but only 0 posts on X, no media coverage, and it's essentially unknown in the English-speaking world. The project is free and open source, with no revenue.

- Copycats and derivatives: Kimi-Bo/CC-Desk-CLI-Tunnel (10-31 fork that added an external CLI, 7 stars, merged back upstream as PR #139); Belay (a same-theme tool post on L-site, unverified); the proxy vendor ProxyLane proactively approached in issue #156 about a sponsorship slot in the README, precisely because "many people in the linux.do thread asked whether the egress should go through residential proxies." This shows the business side (static ISP proxies and residential IPs) has already set its sights on this user base.

### 7. Takeaways

- Posted an "open-source promo" thread in a highly vertical Chinese community (linux.do) following community rules; the title hit the community's collective anxiety (bans) head-on and used community slang (焚决, 蹬, 小鸡); posted the same day the repo was created, then kept bumping and updating the thread.

- Did not fight existing solutions head-on; instead filled the experience gap in a DIY approach that was already popular (CC on a VPS).

- Spelled out the compliance position (no changes to the official binary, no adversarial tactics, single-user personal use) to lower wariness from both users and the platform.

- Brought installation down to one command, bundled dependencies into the installer, added one-click upgrades, and removed a component that gets flagged as malware.

- Where the user base could be monetized: residential or static ISP egress, and hosted VPS plans (proxy vendors have already come knocking).

### 8. Uncertain

- No click-source data for where the second wave of stars starting on 11-02 came from (author bumps, new tutorial posts, or the ccdt release); the GitHub stargazer timestamp API currently returns nothing with the token I have.

- Account risk: Anthropic's terms restrict third-party products from using subscription logins, and the project itself warns about this. If the official side tightens rules, or users still get banned under the VPS setup, the word of mouth could reverse.

- The nicheloom figure of 122 upvotes comes from a search snippet and is unverified; the Belay post is no longer accessible.

- It's unclear how many of the 13k downloads are duplicates from automatic upgrades.

This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.