A post about an architectural error I helped make and the strategy I am now building around to avoid repeating it. The short version is that the parts of Wasabi we built protocol-first survived the regulatory pressure that killed our coordinator company, and the parts we ran as a single operator did not. The longer version is below, written for anyone building freedom technology who would prefer to learn the lesson from someone else's scar tissue.
View quoted note β
Login to reply
Replies (10)
"Mentioned event not found"
I am seeing this text quite often nowadays. Is it because of my client? I am not going to say which client I am using so that the people working for npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg do not get angry.Check again now π
I've had the same problem for the past few weeks
βFreedom technology has always been a contest between architectures and adversaries, and the architectures that survive are the ones an adversary cannot find a person to call about. The order of operations is protocol first, library second, application third. That order produces systems that outlive their founders.β
View quoted note β
I think the issue is that primal doesnt show long form edits? Not sure...
You can see this note now, right? Made a fix.
Yes, thank you π
Stillβ¦


This user she reposted is marked as spam by primal and many users.
Thanks! π