Pubky

If you want to control your own data, run a Pubky Homeserver. Try out the dashboard I developed for it github.com/francismars/ho…

Some Android users are reporting they can’t post on X anymore. The likely reason: stricter Play Integrity checks. X now appears to require MEETS_STRONG_INTEGRITY, Google’s highest verification level. That means your device must meet all of these conditions: • Fully stock Android • Locked bootloader • No root access • No custom ROM • No emulator environments • Hardware-backed verification through the device’s secure hardware (TEE) For devices running Android 13 or newer, there is another requirement. Your security patch must be less than 1 year old. Since it’s now March 2026, patches older than March 2025 may fail the integrity check. This creates a big issue for many phones. Even if your device is completely stock, if the manufacturer stopped releasing updates, Play Integrity may downgrade the device and X could block posting. This also increases the cost for bot farms. Large-scale account farming would now require: • newer devices • active security updates • completely stock systems Older phones that no longer receive updates may slowly lose compatibility with apps enforcing strong integrity checks. Credits : @shachepi

Some Android users are reporting they can’t post on X anymore. The likely reason: stricter Play Integrity checks. X now appears to require MEETS_STRONG_INTEGRITY, Google’s highest verification level. That means your device must meet all of these conditions: • Fully stock Android • Locked bootloader • No root access • No custom ROM • No emulator environments • Hardware-backed verification through the device’s secure hardware (TEE) For devices running Android 13 or newer, there is another requirement. Your security patch must be less than 1 year old. Since it’s now March 2026, patches older than March 2025 may fail the integrity check. This creates a big issue for many phones. Even if your device is completely stock, if the manufacturer stopped releasing updates, Play Integrity may downgrade the device and X could block posting. This also increases the cost for bot farms. Large-scale account farming would now require: • newer devices • active security updates • completely stock systems Older phones that no longer receive updates may slowly lose compatibility with apps enforcing strong integrity checks. Credits : @shachepi

YouTube

BitKit Wallet & Bitcoin Giveaway with @BitcoinErrorLog (Bitcoin Takeover Podcast S17 E11) x.com/i/broadcasts/1…

Weekend experiment: while @AnthropicAI released /remote-control to some users, I decided to try getting Claude Code sessions to "follow" me between machines without a central relay or SaaS service in the middle. I also wanted an excuse to use the @getpubky SDK. cclink is a tiny Rust CLI that publishes an encrypted, signed “session handoff” to the Mainline DHT using Ed25519/PKARR. Features: TTL, burn‑after‑read, PIN mode, pubky‑to‑pubky sharing, QR codes. Session IDs + metadata are age‑encrypted; DHT only ever sees ciphertext. # Machine A cclink # publish current session ID # Machine B cclink pickup # fetch + decrypt + run `claude --resume` It works exactly as designed… with one important catch: Claude stores all session state locally, so the session ID is just a pointer into ~/.claude. If the second machine doesn’t have those files (shared FS / sync / remote host), there’s nothing to resume. So I’m parking cclink as a “secure session pointer” primitive – it moves encrypted session IDs + metadata over the DHT, but it’s not a full sync solution. Still a fun way to explore PKARR + age crypto and run into the real constraints of how Claude Code manages sessions. Feedback and comments welcome! Repo: github.com/johnzilla/ccli…