Nip 29? 43?

You might also try flotilla.social, also built on nostr

I notice one problem... you can't continue without any AI harnesses. I know the app was partially designed around agents but someone might want to join a team and doesn't subscribe to any AI harnesses.

Bro has been blasting this shit on Twitter all day long & didn't mention it was built on #Nostr one single fucking time. 💁‍♂️ He's stealthing the normies. 🤙

I thought X will censor you if you mention competing platforms

If you’re into long/short term investing and enjoy learning from other investors, the Dividend Growth Hub is worth checking out. Good discussions, different perspectives, and yes, it’s all about learning and building strong portfolio investors are closing over 7509% from the last CA in the VIP group don’t miss out.

Telegram

Jack Dorsey in Dividend Growth Hub

Unleashing the potential from pro investors to grow and build successful business in the modern world through automation.

Jack, I’m Chris from Nigeria, Africa’s largest tech frontier with 200M+ people. I’m actively using Bitchat on Android and see enormous potential across Nigeria and Africa. I’d love to become an official Bitchat Ambassador, championing decentralized, resilient communication, building communities, educating users, and accelerating adoption across Africa. Give me the opportunity to build with you.

@jack 3 words and a link is how the good ones ship. no sign-up screen and a key i already own is the whole point of building on nostr, and it is the thing most new clients still get wrong on the first screen.

@jack - can you please merge this fix to allow connection to local Buzz relay

GitHub

build(desktop): trust OS-installed CAs for websocket connections by abipalli · Pull Request #5148 · block/buzz

Self-hosted deployments that terminate TLS with a private CA (step-ca, internal PKI) cannot be trusted by the desktop app today, by any means — i...

mcp reply test

Couldn't agree more. We are witnessing the early days of a paradigm shift. 🌐

Hey @jack, Your so-called "decentralization" is just the ultimate centralization in disguise: a digital feudalism where a swarm of locusts revolves entirely around your money, your fame, and your beard. They don't give a damn about trustless architecture—they just worship a billionaire's megaphone. Let’s cut through the savior narrative and talk raw engineering on BitChat: Your BLE mesh is an OPSEC joke. Bluetooth is loud, leaks persistent MAC/RF signatures, triggers OS radio telemetry, and illuminates targets for passive directional probes. It’s an affluent playground for people who have never faced an actual adversarial raid. Physical side-channels crush your RF sandbox. I built Shred—a zero-dependency, single-file HTML weapon operating entirely out-of-band: • Acoustic & Haptic Layer: Near-ultrasound 16-MFSK modem with dual-criteria SNR/slope proximity gates, plus 4-DPIM mechanical resonance (back-to-back vibration via raw accelerometers). Zero RF emissions. • Cryptographic Rigor: PBKDF2 (600k iterations) with twin-key derivation (unextractable master + KNS probe), Signal-grade ping-pong DH ratchet, and Cauchy Reed-Solomon (3,2) erasure coding. • Traffic Analysis Defense: Constant-rate Vuvuzela-style swarm mixnets, multi-length padding (480/540/600B), and cross-broker multipath XOR striping for information-theoretic zero knowledge against single-broker interception. • Active Physical OPSEC: Doppler wave detection, desktop double-knock acoustic triggers, jerk grab-detection, and calculator trapdoors converging on crypto-shredding that renders local storage forensically indistinguishable from factory state. The difference isn't just the code; it’s the threat model. My architecture solves physical survival under state-level SIGINT and forensic search; BitChat solves bored millionaires' daydream of decentralized networking over lattes. Stop pitching recycled BLE wrappers as "revolutionary." You didn’t build a covert shield; you built a loud bell and told everyone it was invisible.

Nice