PSA:
Just got a weird XSS attack as a 0 sats zap (not sure how that even works).
Seems a good thing I was on Wisp on iOS when it happened, and it didn’t seem to execute. If I was to be on Primal on browser it might have worked.
But may be having to start a new nsec soon anyway.
Here’s what my AI thinks it did:
“This looks like a deliberate XSS (cross-site scripting) attack attempt targeting Nostr clients, likely Primal.
Here's a breakdown of what's happening and what it means:
What the payload is doing
The zap description isn't a normal message. It's an injection attempt containing:
<div> <div> <div> — Nested HTML elements designed to bypass naive sanitizers or exploit rendering quirks in a client that displays zap descriptions as HTML rather than plain text.
A webhook[dot]site URL — Webhook[dot]site is a legitimate tool, but here it's being used as an exfiltration endpoint. Any data sent to that URL goes directly to the attacker. They're using it as a quick, anonymous way to capture stolen data without hosting their own server.
localStorage.getItem('primalSec') — This is the smoking gun. primalSec appears to be a localStorage key used by Primal (a Nostr client) to store sensitive session data. The attacker is trying to steal this credential via XSS and send it to their webhook.
In short: the attacker is sending 0-sat zaps with malicious descriptions hoping your client will render the description as HTML/JavaScript, which would then silently steal your session secrets and beam them to webhook[dot]site.”
You guys are disappointed about the Cold Card thefts.
I’m disappointed you guys are still defending the perpetrators, and virtue signaling instead of dissecting the perpetrators’ possible motives and associations.
Wanting to update to the new StartOS0.4.0…
but I hate the thought of pausing my node for >8hrs and especially seems like a bad time with BIP110 activating soon
The Playbook: Gradual Capture of a Decentralized Project
Phase 1 — Establish credibility.
Contribute high-quality code, reviews, and technical analysis. Become indispensable on non-controversial improvements. Your reputation compounds quietly. Nobody perceives you as political because you haven't taken a stance yet.
Phase 2 — Recruit quietly.
Identify talented developers who feel under-recognized, ideologically aligned, or frustrated with current leadership. Mentor them. Get them merged as contributors with increasing responsibilities. You're not building a faction — you're "helping the project grow."
Phase 3 — Shape the narrative.
Once your network holds meaningful review authority, you collectively influence which proposals are taken seriously, which are framed as "reckless" or "responsible," who gets invited to core meetings, who gets media access. You don't need to block things overtly — you just create friction for dissenters and lubrication for allies.
Phase 4 — Control the chokepoints.
The key positions aren't "lead maintainer" — they're things like: release PR review authority, BIP editorial control, communication channels (mailing list moderation, IRC/Twitter presence), conference organizing, and funding allocation (grant recommendations, sponsorships). These soft-power levers determine whose voice is amplified.
Phase 5 — Normalize your positions as "the consensus."
Once enough reviewers and contributors share your framing, your preferences stop looking like opinions and start looking like "obvious technical defaults." Dissenters increasingly self-censor because arguing feels futile or socially costly.
Phase 6 — Attrition of opposition.
People who disagree leave — not because they're expelled, but because the environment becomes exhausting and unrewarding for them. Each departure creates a vacuum your network fills.
The end state isn't formal control — it's a situation where every meaningful decision passes through people who share your worldview, and alternatives feel impossible to advance. The organization still looks decentralized on paper.
This is essentially how regulatory capture, corporate board capture, and even political party entryism work in practice. The Bitcoin ecosystem's relatively small set of core contributors makes it theoretically more vulnerable to this than most people assume — but its high public scrutiny and the ease of forking (Knots is literally an example) serve as meaningful structural counterbalances.
So I returned a power couch I bought from Costco a few months ago. It had electrical issues. I think the switch was smashed in transit and eventually shorted, but I digress.
So I returned it and then bought the same couch which was cheaper since I wasn’t buying it online this time.
Pleasant surprise when I came home:
Though it is the same model couch, this one is much more plush, the back is a couple inches taller, and it has an additional small footrest that flips out too. Overall, much more comfortable 😊🙏