My interim conclusion is that core's governance is great, but knots' principal-driven approach is also great, so I'm hesitant if fork. that is, pending conclusion.
That's nice! That's the only way to counter "Washington". WHO IS JOHN GALT?

I frequently delete and repost posts because my brain structure is uneven, high for logical and creative, but low for working memory and quantity. That's the excuse I use.
I used to use iterm, but before I knew it, I had settled on vs code. Vertical integration is "high convenient".
I think this is truly a problem that will continue forever and cannot be solved. In the end, where should the "root of trust" be? One solution would be to root and provision a hardware wallet. Another solution would be to use biometric authentication. Or maybe social recovery with shared multisig. But either way, I think that anything you put online requires a certain kind of "giving up".
I'm not focusing on MoE, more narrowly, it's on just "spending online"🫡
BDKはそうでも、WASMにするときの通信モジュールの問題でダメらしいです🤔 まあelectrum相当の"API"路線の開発は十分に考えられるかな、と。メタマスク(& infura)だけに。
Network access is limited to http(s)
This essentially means the library only supports Esplora as blockchain client. Both RPC and Electrum clients require sockets and will not work for BDK in a WASM environment out of the box.
:shakingeyes_sm:
Satoshi Nakamoto was building an imaginary future. That embraced the right fundamental principles but was sketchy on the details. This is true for everyone and natural for how to build an imaginary future.
A typical pros and cons was not sticking to a pure monetary protocol. It gave creative room and was representative of the romanticism like inscribed in the first block, which contributed to early adoption and susequent evolution, but as it grew, problems grew.
This was a inevitable progression. That is, the 0 to 1 phase was over, and we are moving to the 10 to 100 phase.
IMO it's natural for how to build an imaginary future.
"The Big Block is in all of our hearts"
(english to japanese translation to english re-translation)
me seeing discourse denying UASF and celebrating BSV architecture
https://x.com/Rob1Ham/status/1918474387453280349
https://media.tenor.com/8dGugqxC4sAAAAAx/shocked-surprised.webp
Honestly, i can't understand what it says at all
"how many coins are being secured by a node, “economic nodes” is what matters."
me seeing discourse denying UASF and celebrating BSV architecture
https://x.com/Rob1Ham/status/1918474387453280349
https://media.tenor.com/8dGugqxC4sAAAAAx/shocked-surprised.webp
I understand that OP_RETURN is a garbage dump, but the question is whether to remove the "limitation" of OP_RETURN, and are you saying that we should give up on full nodes like Ethereum and use pruned nodes instead?
Surely, I also think that if the network can be resilient from a pruned node that is left *only one* in the world, that would be one direction of "evolution". And that might be already possible if we gave up on past history and continued only with future payments.
well, I have to say that they went a bit too far though.
Seemingly Bitcoin github account has a strong opinion. That's nice! dev is not a tool for biz and users. Just one of humarns. What do you think motivates us?
Thank you for letting me know. And now when logging in yakihonne, a popup has introduced me gossip model setting. yes, my relay setting is the gossip type. i've toggled on it!
huge thanks for your rapid developing🙏
"Remove the OP_RETURN restriction to match taproot" is retarded. If taproot is brought up, the necessary question is "was taproot a failure?".
Any discussion that leaves out "what bitcoin is" is generally futile.
nostr:npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q
I used yakihonne to port a few articles from another blog service to nostr. I'll give you some feedback.
- I don't know if I'm successful when I press the publish button.
I was often kicked with 401. But I couldn't see anything on the screen. I had to open the dev tool console to check.
- Drafts aren't displayed for each article.
Even if I press "Edit article" for each article, the last saved article continues to be displayed.
- The editor doesn't work in firefox.
The focus shifts and I can't enter or delete as I want.
- The first request when logging in doesn't seem to await decrypt, so the signer request is displayed all at once.
The first two were both solved by super reloading. But when it worked, yakihonne was a good service. I hope this helps.
Thanks.
※本記事は別サービスで2023年2月10日に公開した記事の移植です。