ploum

If Satoshi has at least half a brain (which we know he has), he knows that moving even one coin from this historical stack could crash the whole Bitcoin economy. So, no, he doesn’t have trillions of dollars.

(It is so basic, I’m still confused by people asking how could he not sell those coins. Because the answer is simple: to whom?)

My theory is that Satoshi is a persona created by Adam Back and Hal Finney.

They probably devised something where both needed to agree and sign something for Satoshi to act. This also allowed them to say "I’m not Satoshi Nakamoto".

They also probably ensured that anything that belongs to Satoshi required both of them. The death of Hal Finney ensure that Satoshi died definitely.

But they may have "killed" him before by burning the keys because, when Bitcoin started to become a success, they probably anticipated the need to "kill" satoshi (few remember but Bitcoin passing 1$ was considered as a crazy bubble at the time! Some become millionnaires and exited when BTC did the 30$ bubble. Satoshi’s stack was already closely observed, bright mind of that time would have anticipated the need to kill it). Or it was just that "satoshi" was not needed or they accidentaly deleted some keys.

try gemini://bbs.geminispace.org

is it because I was young? I still believe phpbb forums were the best!

Your example is completely stupid: I’m talking about writing a website.

Would you go to rural Spain without knowing a word of Spanish and handle flyers with a Spanish text you had no way to check? Seriously?

Exactly!

If you can use GrapheneOS, good for you but what /e/OS offers is:

- Usable Android with your usual Android app (banking, etc) - No data sent to Google by default - Easier interface with nearly no bloatware - Available easily on many smartphones, including older ones - Extending the life of some smartphones

The price to pay is:

- Some Murena cloud bloatware - Android security patches are sometimes delayed - Security is not on par with GrapheneOS

If your main concern is protecting your privacy from Google and extending the life of your smartphone without breaking a sweat, /e/OS is probably the best option.

If your main concern is protecting against state actors attacks or very specific threats, then GrapheneOS might be better.

/e/OS works really great for non-techie users. I’ve done it in my family.

"One of my coworkers is EXTREMELY capable but functionally almost illiterate."

I cannot imagine what it means. To me it reads like "I know someone who can run very fast but has no legs."

nope, let the user does the translation, with his own choice of tool and being thus perfectly aware of the shortcomings.

I know that some people translate my French posts to read them. That’s really cool. But I would never post something I didn’t write myself (but I use spellcheking tools. I even sometimes disagree with them)

Yet another text blog that doesn’t work without Javascript.

What kind of sick mind does it take to ensure a straight blog post requires Javascript?

Me too but I’m OP. Really happy to see I’m not alone!

the "open" open outside.

So you go to a site. If the site is not complete, try "v full" (for "view full").

The reason is that there was no unmerdify rule for your site and that readability mistakenly assumes that lot of your site is spam/ads (readability doing that is the reason why we push for unmerdify)

well, indeed. If you use mutt and use the "reply" feature in Offpunk, you will see how well emails and blog/gemini posts merge well ;-) (this will be the subject of another post later)

I tried to add kiwix support to Offpunk in the early days but kiwix do not support incremental update of the wikipedia database, which makes it a huge pain point.

The cache is pure and straight files-in-folders. This makes it trivial to browse the cache by hand:

cd .cache/offpunk/https/news.ycombinator.com/item cat "id=46943752"

So it could be trivially shared.

The "netcache" tool gives you the cached content or, with --path, returns the path were to find the contentd.

The only point is to preserve the file-modification attribute, which serves to know the age of a cached ressource.