Next up: find out which .bit domains I had registered using those keys, while rescuing some old photos to the NAS.
Booted up an old MacBook Air from 2014 using an external drive bay for the SSD chip, because that part of the mainboard had died. It still has bitcoin-qt, dogecoin-qt and namecoin-qt installed. And I found a glorious 2 NMC on there. 😂
BUT WHO WILL BUILD THE ROADS
Anyone else here going to HCPP next week? Finally got all the things booked (except for onward travel, naturally).
Fortunately, Thunderbird indeed makes it very easy to re-send with just the subject encryption turned off. Good job, Thunderbird devs! 👏
This is what happens when you send a PGP-encrypted email with Memory Hole encryption for the subject line/header to Werner Koch (of GnuPG fame):
😂
That's great!
Would also be fantastic if one could dismiss the red warning about LNDHub accounts being custodial once the risk has been acknowledged. It can and should explain the risk, but we're adults who can also agree to that and then don't want to be bothered about it every time we look at our wallet. Maybe it could move over to the account settings once explicitly acknowledged by the user?
To my surprise, someone had actually registered the NIP-05 well-known URI with IANA. It was just missing on the Wikipedia page, so I just added it there, too.
https://en.wikipedia.org/wiki/Well-known_URI#List_of_well-known_URIs
Actually, since they're not spending BTC, I guess it's still a form of dollar cost averaging. Maybe this is what some people call unit cost averaging? Financial experts, please enlighten me!
It's kind of crazy that the El Salvador government is bitcoin-cost averaging instead of dollar-cost averaging. Next-level stacking either way.
Not to get overly excited here, but I'm overly excited.
Just sent from my lightning node on my nostr:npub126ntw5mnermmj0znhjhgdk8lh2af72sm8qfzq48umdlnhaj9kuns3le9ll using nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm hub & their new Alby Go app - to the nostr:npub1uq70uqgas9pyhds2zt57kr9se8rg3s68ztphjnq82ts8rzeknmeql7u0c2 app with a mint that the Bitcoin Mentor team set up ourselves for testing. Bullish.
Nice!
However, the Fedi devs need to fix the currency display. SATS are a shitcoin: https://www.okx.com/learn/what-is-sats-bitcoin-brc20-token
Even worse, the current Prime Minister of the UK also wants a hot war:
https://consortiumnews.com/2024/09/20/the-madness-of-antony-blinken/
MLS is a good idea: https://socialwebfoundation.org/program-protocol-e2ee/
Again, it's only about deletion *requests*, i.e. showing intent. Why are you painting it as if anyone claims proper deletions are possible? My very post that you replied to explicitly says "requests", and I haven't seen anyone saying anything else about the feature.
It already works like this on other decentralized protocols, with no demonstrable bad side effects that would outweigh the usefulness. If you want to insist that it's such a big problem, then please point us to good examples of that on other decentralized protocols, or concede that it's pure speculation. Also, you should not use any clients implementing NIP-09 (or not letting you turn it off), since that's your personal choice anyway.
Also very simple, and implemented like this in many XMPP clients: only allow edits if they happen shortly after the original message. Later, just show it as a separate new message, and discourage doing it in the first place with client-side UI preventing you from editing too late.
You can choose a client that only indicates that an author wants to retract a post, and they can also provide a reason for the deletion. This is not about owning up to posts or mistakes, but about fixing typos, removing tracking params in links, and stuff like that. Since, as you say, you cannot actually delete a post that has been published and synced outside of your control, the fear about people hiding things is unwarranted really.
With email, I re-read drafts twice before sending. But with social media I'm used to proper delete handling by almost the entire fediverse (which is all HTTP), and it's difficult to override that muscle memory for Nostr.
Embarrassing typos are the worst on a protocol, where a lot of clients don't properly deal with delete requests. :/
