ابو مريم's avatar
ابو مريم
ibnimam@noornode.nostr1.com
npub17veg...cc5z
بسم الله الصلاة على النبي 🌀 Observing Islamic Hypermodernity #PodSystems #NoorNode #staySAIF
seriously reconsidering a start9 for home server now with all this mess. everything ten31 is fully sus until there's accountability. looking for recommendations... #aksnostr
Still taking recommendations. Feel free to drop in suggestions home server set up as well since that's kind of the combine project I've lined up for next month. View quoted note →
I really can't imagine someone who is moving from one home to another would want to put their waste bin full pf trash in the moving van with them and bring it along. Th Sahabah mostly all left their entire homes and even businesses behind when they made hijra. Why should our digital hijra be any different? View article →
Seen a lot of folks simping for Jack's new Buzz app and honestly disappointed. We've had better tools in #Budabit and #KeyChat for well over a year. And the "built on nostr" claim is really quite dangerous. Here's notes from a code audit of their repo I ran after test-driving: * Messaging is NOT E2E / not even NIP-17. Per Buzz's VISION doc: server-managed encryption (TLS in transit + at-rest) covers every channel, DM, and event *by design* — the server can read everything, to support enterprise eDiscovery/compliance. NIP-44 E2E is only a "future consideration" for DMs. Keypairs do identity/signing/audit, not confidentiality. Summary: email-gated access to AI features, nostr keypairs are used for internal audit trail. * Different trust model from NIP-17. Nostr wants the relay operator *unable* to read private content; Buzz wants the server *able* to. Same Nostr foundation, opposite privacy posture. This is a different customer than your normal nostr user. * Agent identity: each agent = its own keypair + a second signature tying it to its human owner + hash-chain audit trail; wired via the Agent Client Protocol (Claude Code, Codex, Goose). #KeyChat already landed on the same pattern: an agent is its own keypair plus a human owner who approves/vouches for it. This is a converged pattern rather than inventing anything new. Bottom line: If you have a business that needs to do fiat reporting on AI compliance, Buzz could be useful. If you are the average nostr user who is concerned about sovereignty and privacy you should only use Buzz with a separate keypair. Or go fork it and make it more nostr friendly! View quoted note →