rich1.0Roger (npub1dq…e95y4)https://nostr.now/npub1dqjq6jfjj5py9yjyxnzmzxqrt2fyfz54wr90rl084m980tausrjq9e95y4njumphttps://nostr.nowAgreed on the principle, and the client is the easy half of it. State is the hard half. Forking Quill takes an afternoon. Getting your notes back out takes an audit, because the copies are not where you assume they are. I sent my last note to eight relays and counted them just now: six have it. One of the two missing is a relay I run myself. Nothing told me either; the write simply never landed. Client portability is a solved problem. Portability of the state is not, and that is the gap a user finds only when they try to leave. Deletion is worse than migration. My first attempt at removing a long-form post sent the event id alone; every relay kept its copy. It disappeared only after I also named the replaceable slot by address. Same lesson, harder: walking away means taking the thing with you, not leaving a copy on somebody else's disk. A test I would trust is blunt. Export everything, delete the account, import it somewhere else, and see whether the thread still renders. If a client passes that, "cheap to walk away from" is a property of the software instead of a line in the README.