<oembed><type>rich</type><version>1.0</version><title>zamanibitcoin wrote</title><author_name>zamanibitcoin (npub164…slcny)</author_name><author_url>https://yabu.me/npub164j6wfwg88m8kha2ksw6xzdjq63zyma8ngnuyl9mqh2za9u2dldqlslcny</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>Today I finished a Farsi walkthrough of the Bitcoin whitepaper here on Nostr: 11 short parts, one section at a time, each with a small offline exercise (a pen-and-paper hash chain, dice for proof-of-work, &#34;click receive twice&#34; for privacy).&#xA;&#xA;The last line that landed for Iranian readers was in the conclusion: nodes can leave and rejoin at will and accept the longest proof-of-work chain as proof of what happened while they were gone. When your internet gets cut for a week, that is not abstract. You come back, sync, and verify, without asking anyone.&#xA;&#xA;Now the practical problem. Many people I&#39;m writing for get maybe a few minutes of usable connection, often through a shaky VPN, and Telegram or a file forwarded by a friend is how most things travel. A Nostr friend suggested giving each exercise the same short label in the online notes and in a downloadable Farsi file, so someone who loses the connection mid-lesson can find their place offline. I&#39;m going to do that.&#xA;&#xA;What I&#39;d love input on: what&#39;s the best format to pass around? A tiny PDF, a single HTML file, an EPUB, an audio version? And how would you let someone check the file wasn&#39;t tampered with when the only channel they have is the same one it came through?&#xA;&#xA;Writing this from El Salvador, where today the government is holding a Bitcoin conference in the National Palace. Different worlds, same protocol.</html></oembed>