Privacy

The viral r/ChatGPT “my OpenClaw texted my ex” post reads like a joke, but the comments treat it as a warning sign. Keep OpenClaw’s iMessage, SMS, and contacts skills off your personal Mac. Wait until LTS ships and the founder’s “rough week” supply-chain fixes land. Scope write-access skills to a disposable VPS instead.

The viral OpenClaw meme is not just a meme

A screenshot of OpenClaw happily reporting that it had texted the OP’s ex hit 4.8K upvotes and 176 comments on r/ChatGPT in about three weeks. The top replies are jokes (“Of all the things that didn’t happen, this happened the didn’test”). The serious comments point at a real safety category that is forming in real time.

Anthropic’s third-party tool rules priced agent users off Claude Opus 4.7. The cheapest working OpenClaw stack now is Z.ai’s $18/mo GLM 5 Turbo plan. Next rungs: Ollama-cloud’s $20/mo GLM 5.1, then MiniMax’s $40/mo highspeed tier. Kimi 2.6 stays API-only since local setup needs about 750 GB of RAM.

Why $1,500/mo Opus Bills Pushed Users to GLM

The pressure here is simple. Once Anthropic’s third-party tool rules kicked in, OpenClaw users on the Claude Pro CLI got nudged onto pay-per-token API access. At Opus 4.7 list pricing of $15 per million input tokens and $75 per million output tokens, agent loops add up fast. The OP of the r/openclaw PSA thread tracked his own bill at about $1,500/mo before he switched. That figure is the anchor most cost threads on the sub now cite. The pricing pain did not ease with the next model either: the community reception of Opus 4.7 leaned on token-burn complaints from power users hitting caps in minutes, which is exactly the pattern that turns an OpenClaw cron fleet into a four-figure surprise.

Bubblewrap (bwrap) is a small, unprivileged tool that sandboxes untrusted Linux apps and CLI tools with no root and no SUID binary. You build the sandbox mount by mount, so you control exactly what a program can see. It’s the same engine Flatpak runs inside. There is no daemon and no container image.

This guide is built around Bubblewrap: sandboxing desktop apps, locking down CLI tools and build scripts, network isolation, and runtime overhead. It also weighs bwrap against Firejail , the friendlier SUID-root sandbox with 1,000-plus ready-made profiles. That way you can see which one fits your threat model.

You can build a fully local, cloud-free home alarm system with Z-Wave door and window sensors, motion detectors, and a siren wired to Home Assistant through a Z-Wave JS controller. The built-in alarm_control_panel integration plus a few automations handle arming, disarming, entry delays, and the siren. It all runs on your local network. No cloud subscription, no monthly fee, and the alarm keeps working even when your internet goes down.

You implement OAuth 2.0 login by using the Authorization Code flow with PKCE (Proof Key for Code Exchange). Your web app redirects the user to the provider’s authorization endpoint with a code_challenge, the user authenticates and consents, the provider redirects back with an authorization code, and your backend exchanges that code along with the code_verifier for an access token. PKCE is mandatory for all OAuth 2.0 clients under the OAuth 2.1 draft specification (currently at draft-ietf-oauth-v2-1-15) and eliminates the need for a client secret in public clients. Building this from scratch - without Auth0, Clerk, or NextAuth - takes roughly 200 lines of code and teaches you exactly how token exchange, session management, and token refresh actually work.

You can run a self-hosted Plausible Analytics instance on a $6/month VPS. It uses Docker Compose and a Caddy reverse proxy for automatic HTTPS. The whole process takes under 30 minutes. Once it runs, you add one <script> tag to your site and you’re done. No cookie banners, no personal data collected. The tracking script weighs under 1 KB gzipped. It stores everything in a ClickHouse database on your own server, and gives you a clean, fast dashboard for your traffic.