Codex talks to the ChatGPT backend over WebSocket by default. If your network path involves Clash, a corporate proxy, cross-border transit, or Cloudflare challenge pages, that long-lived WebSocket gets killed easily — and you end up staring at Reconnecting... 1/5 over and over. Turn off WebSocket and switch to plain HTTP streaming requests, and the problem mostly disappears.

Why WebSocket Breaks Behind Proxies

The WebSocket protocol starts with an HTTP Upgrade request; only after the server returns 101 does it switch to the long-lived connection. That long-lived connection is exactly where the problem sits — proxy servers, firewalls, and CDN nodes all run timeout policies on idle connections, and Cloudflare’s challenge mechanism can inject an interstitial page mid-path. Any link in that chain kills the connection, and the Codex client starts Reconnecting.

Conclusion first: there are a lot of third-party Telegram clients, quality varies wildly, and you should avoid the closed-source ones as a rule. Since 2021, Telegram has required first-time registration to receive its verification code on the official mobile client — desktop and third-party clients can’t register directly. That’s already a signal.

This post is a curated list. The source is a roundup post by Telegram’s @LCGFX; I’ve reorganized it by platform and added open-source status and risk judgments.

Registering an Apple ID for another region shouldn’t be hard, but Apple keeps changing the flow. Most tutorials online record only a single path, and the comments are full of people saying it no longer works. More annoying: after registering, your first App Store login has a chance of being bumped straight back to the China store.

Here I’ve put together all four methods I could find, plus a complete plan to avoid being sent back to the China store. Not just the US store — the same applies to Turkey, Japan, and Nigeria.

Signing up for services like GPT, Claude, or Telegram needs a number that can receive verification codes — but you may not want to hand over your own phone number. That demand spawned a batch of SMS verification platforms: some free, some paid, some aimed at developers. Here are four I’ve actually used; as of May 20, 2026, all were still accessible. Platform status changes at any time, so open the site and check yourself before using one.

Conclusion first: multi-agent collaboration is not “spinning up a few more model instances.” It has to solve task scheduling, context isolation, permission control, state management, and result merging — every one of which is an engineering problem, not a prompt problem.

The multi-agent stories on TikTok and Xiaohongshu usually go like this: one agent researches, one agent writes code, one agent runs tests, one agent does review, and the main agent collects results like a project manager. The comments: “Whoa, that’s insane.”

I have a strong intuition: some companies in the tech industry right now are going through a full-blown AI psychosis, and inside those companies, rational conversation is simply impossible. I’m not talking about strangers — I’m talking about personal friends I deeply respect. That leaves me worried about how this ends.

This fear has a specific source. I lived through the great MTBF (mean time between failures) vs MTTR (mean time to recovery) debate when infrastructure moved from traditional ops to cloud and cloud automation. Now those exact same arguments are resurfacing in a new costume — only the scope has widened from infrastructure to the entire software industry, and possibly to the whole world.