This bridging trick sounds great. https://fountain.fm/episode/QMpGyNifZM37FW3P1a7x View quoted note →

Lol, I have to zap myself 100 sats to share this episode :-) https://fountain.fm/episode/CKRxIzMnQXrzl5OFLhV7 View quoted note →

"The dollar is king, we're gonna keep it that way. Just saying, if people wanna challenge it, they can, but they're going to pay a big price. And I don't think any of them are willing to pay that price." - Donald Trump Now you know. To be fair, it was in reference to BRICS and you can't accuse the man of consistency. https://fountain.fm/episode/gzfxBKiY94NTCUKySPQ2 View quoted note →

Still can't believe X users have their (eye) balls scanned. https://fountain.fm/episode/rgEmfe8E7ivWuORiUdA1 View quoted note →

Whaha, I've been in DC more often than Odell and I'm a foreigner. https://fountain.fm/episode/0SwABFKl22JmThk9ARlz View quoted note →

Removals after removal are my favorite type of removal. And I have a PR on top of this that removes even more :-) #MakeBitcoinCoreMaintainableAgain View quoted note →

There seems to be genuine confusion about how open source works. In particular some people believe that Bitcoin Core developers have a fiduciary duty, either towards them personally or towards some general notion of the Bitcoin network. They are surprised that I and some others respond to this rather aggressively. Remember that this is the argument Craig Wright tried to make. He failed, but not after millions of dollars were burnt on defending these developers. And not after several quit because of the stress. Don't go down this path. To put it as a catchy phrase: open source means you can do whatever you want with the code, not with the people who write it. Open source lets you fork code, and modify it to your liking. That's pretty much what I do every day, which isn't to say that I don't also try to make sure other people like it. I get paid in Bitcoin and OpenSats keeps their whole treasury in it, so the idea that I want destroy potential future income is rather retarded. Part of CSW's demands was that Bitcoin Core wrote specific (confiscation) code for him. Eventually he just hired people to write it for him, as one should, but somehow that still wasn't enough for him. I get a very similar vibe from people who run Knots but yet don't find that enough. Should we worry about a new round of lawsuits?

Someone, probably a US based catholic young male, subscribed my email to a bunch of lists in order to spam me. I can't be bothered to trace the IP they used for this. But Luke, control your herd.

Guess who's back? https://bitcoinexplainedpodcast.com/@nado/episodes/episode-98-return-of-the-op-return

> this will be my last comment on this topic Well, that aged like a Higgs boson... Bitcoin Explained episode 98 coming soon(tm). View quoted note →

Yippee-Ki-Yay! View quoted note →

Excellent take by me! :-) The fact that many Bitcoin Core developers are paid by someone, when that someone is NOT YOU, does not make YOU a customer that gets to demand things. You need to hire developers directly if you want to work on your behalf. View quoted note →

On Consensus and Humming in the IETF (Internet Engineering Task Force) Classic read.

IETF Datatracker

RFC 7282: On Consensus and Humming in the IETF

The IETF has had a long tradition of doing its technical work through a consensus process, taking into account the different views among IETF parti...

Well, according to AI - which must be right - this way the best quote from me in the @Bitcoin Optech podcast:

Riverside — Highlights.

People seem to be confused about the fact that although Bitcoin Core is open source software, the bitcoin/bitcoin Github repository is a private space, not a public square. As a private space it has rules. Very few, and there's not much enforcement, but they're there. And those rules are not decided by users (in fact, ultimately Microsoft controls the domain). People are free to fork the code and create an alternative space to work on that code. There they can have whatever rules they want. You can make it completely private. The MIT license is very permissive, you don't even have to share the resulting code. You could also allow anyone to comment and sell viagra pills. Up to you! Such code forks are not ideal though. It could create confusion around where to download the "real" Bitcoin Core. Slightly different codebases make things difficult to audit. When implementations diverge too much, it will make future soft forks hard to coordinate. But if contributors to Bitcoin Core can't get any work done when doing so in public, they'll have to find another way to get work done. So as a user, you should not be happy when brigading happens on the repo. Those are precious developer days being wasted, in which actual bugs are not being fixed - or even introduced because tired developers make mistakes. Even if you disagree with a specific change, you have an interest in that being communicated in a non-disruptive manner. View quoted note →