Sjors Provoost (possibly compromised)

This bridging trick sounds great.

https://fountain.fm/episode/QMpGyNifZM37FW3P1a7x

Lol, I have to zap myself 100 sats to share this episode :-)

https://fountain.fm/episode/CKRxIzMnQXrzl5OFLhV7

"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

Still can't believe X users have their (eye) balls scanned.

https://fountain.fm/episode/rgEmfe8E7ivWuORiUdA1

Whaha, I've been in DC more often than Odell and I'm a foreigner.

https://fountain.fm/episode/0SwABFKl22JmThk9ARlz

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

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).

Loading quoted post…

nostr:nevent1qvzqqqqqqypzpp59a0hkv5ecm45nrckvmu7pnk0sukssvly33u3wwzquy4v037hcqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgewaehxw309ahx7um5wgh8xurjdamx7mmnwshxump0qqsgk9glfs557ye2yljmx5vt7grf8tf9w6ut07gupdsgwvzwy3psdzqnmh4tm

Yippee-Ki-Yay!

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.

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

Classic read.

https://datatracker.ietf.org/doc/html/rfc7282

Well, according to AI - which must be right - this way the best quote from me in the

podcast: https://riverside.fm/guest-page?sessionId=2c859898-b88a-4016-abb6-c0fc6e8cb3c8&clientId=3d897568-30e6-4244-8a6d-59ebb8c8855b&archiveId=sjors-qg14v9s75&t=080a6fc0b5a20ddcd074

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.

Ethiopië is niet eens een voormalige kolonie, maar de Tweede Kamer wil er zich mee bemoeien. Tekst van de motie:

Vragen van de leden Diederik van Dijk, Stoffer en Flach (allen SGP) aan de ministers van Buitenlandse Zaken, van Financiën en voor Buitenlandse Handel en Ontwikkelingshulp over het bericht ‘Cryptomijnen in een land onder hoogspanning’.
  
 • Bent u bekend met het artikel ‘Cryptomijnen in een land onder hoogspanning’?[1]
 • Welke Nederlandse of Europese wet- en regelgeving, dan wel IMVO-normen, zijn van toepassing op Nederlandse ondernemers en bedrijven die actief zijn in het cryptomijnen in derde landen?
 • Wat is precies de toegevoegde waarde van het cryptomijnen in Ethiopië aan de lokale economie en samenleving?
 • In hoeverre profiteert de lokale bevolking van Ethiopië van de praktijken die in het artikel genoemd worden?
 • Kan het kabinet toelichten wat volgens haar de wenselijkheid is van het cryptomijnen in Ethiopië door Nederlandse ondernemers en bedrijven?
 • Hoe ziet de inzet van het kabinet eruit om de beperkte elektriciteit die voorradig is in Ethiopië ten goede te laten komen aan de bevolking zelf?
 • Acht het kabinet het noodzakelijk om met extra regelgeving te komen om de negatieve gevolgen van cryptomijnen in derde landen te verminderen, en zo nee, waarom niet?
 • Wat is het morele oordeel van het kabinet over het artikel, met name met het oog op de schrijnende armoede en grote maatschappelijke problemen die een land als Ethiopië teisteren?
 • Hoe verhoudt de ontwikkeling die in het artikel genoemd wordt zich tot de Nederlandse hulp aan Ethiopië? Werken deze elkaar niet tegen?


https://www.tweedekamer.nl/kamerstukken/kamervragen/detail?id=2025D19807&did=2025D19807

And now for something ... completely different:

Roger Ver 'calm and politely' calling out Bitcoin Core censorship, even of people who've been around since the early days. He calls out their conflicts of interest and corruption, their deviation from the original version of Bitcoin... And they always go off on these super technical tangents. And they're mean on camera. "Won't even answer a single question".

Install Bitcoin ABC, now! (yes, it's still actively maintained)

P.S. wow people were young back then

I don't mean to diss OP here, but free market analogies have often misguided people. Sometimes you need good engineering. It really is what led to Bitcoin Cash.

But that doesn't mean blindly trusting engineers. You should find out if they really know what they're doing. How to find out? That's a hard problem, i.e. they can't all get on a person phone call with you, some have an abrasive communication style, sometimes a problem seems very simple but take a lot of curriculum knowledge to grok. You can't just trust them either when they say "it's complicated", because that what charlatans would say too.

can you add a threshold amount setting below which:

1. You don't send a push notification
2. You don't show the transaction
3. You do collect the zap(s), either in the background or the next online session #spam #zapvertising

Windows is back!

Although Satoshi started out with a Windows client, and apparently many miners still use it, most sane developers and security conscious people use Mac or Linux. Over time this led to increasing neglect of Windows support in #BitcoinCore, to the point where some people joked (?) about just dropping it entirely.

But it seems there's renewed attention.

This seemed worth clarifying, so I did the thing where I ask a question and answer it myself:

https://bitcoin.stackexchange.com/q/126208/4948

It is about time that we stop tolerating nonsense and come back to a place where most of us value (proof of) work, ideas, and selflessness instead of overblown emotional reactions, unbacked wild claims and adhesion to various cults.

Anyway, in the unlikely event I can restrain myself, this will be my last comment on this topic.

https://antoinep.com/posts/relay_policy_drama/

But yes, we need to nice to

and his aggressive cult.

"Life changing" - anonymous person who first learned about this

https://lornajane.net/posts/2011/navigating-bash-history-with-ctrlr

If development were primarily about choice the developers ought to instead just ship a copy of GCC: there tada, you get all the choices, write your own node. :)

/u/nullc

Jokes aside, it's a good post.

https://old.reddit.com/r/Bitcoin/comments/1kab15o/bitcoin_cores_github_mods_have_been_banning_users/mpou6xb/

Dutch hipster bank #Bunq just added support for buying and selling crypto in collaboration with Kraken. There seems to be no way to withdraw coins, which not even their FAQ seems worth mentioning. It says something about the "crypto" market in general that any company thinks they get away with that.

https://together.bunq.com/d/61673-bunq-crypto

My first impression of Bitcoin Core, during the blocksize wars, was also that of arrogance. It's an unfortunate side-effect of people losing patience when having to re-explain something a hundred times. Time they're not spending on writing code, and energy they're losing to remain motivated to write code.

The project is run by volunteers who do not have time, and should not waste time, for maintaining useless functionality. Having people in the project that are (somewhat) comfortable in delivering such bad news is extremely important. I've been on the receiving end of that too internally.

You do not want Bitcoin Core to be a please-everyone kind of project. That's a recipe for unmaintainable code and really bad bugs down the line.

Always great when stuff gets merged after two years, especially after a few months I tend to forget what my code is doing. Shout out to Daniela Brozzoni for the diagram.

Sorry, but it's time to move to bolt12 and BIP352.

Ironically since I replaced my self-custodial BTCPay based zap setup to LNBits, I do still rely on LNURL. Happy to try a bolt12 based self-sovereign setup when there's a spec.

Leuk geprobeerd though: https://www.accountancyvanmorgen.nl/2025/04/29/hoge-raad-bevestigt-cryptovaluta-in-box-3/ #box3