Thread

Replies (77)

At least I embrace my retardation. We are all of us profoundly retarded in various ways. Limited in our abilities and our ascertainment of knowledge. But you still won't own up to your intellectual dishonesty, and to YOUR blind spots. Your limitations. You think you know well enough to think on behalf of everyone who runs Core. That is socialism. One of us is honest, the other willfully ignorant and subversive. So GFY.
By lying about, remaining willfully ignorant of, or silencing debate about, how the Bitcoin software works in order to push a change to the software that some users, by means of the dishonesty, no longer give informed consent to. That is exactly what LARP here and his buddies have been doing. The change in direction Core gas taken is specifically aimed at eroding Core users' control over their mempool over the course of the next few updates, and the public discussion has been misrepresented by them over and over again so that only the most in tune bitcoiners have been able to understand the dishonesty, regardless of their stance on spam. I am not philosophically anti-spam as a primary. I am anti-aggression and anti-dishonesty before I am anti-spam. And that is why even if you don't think NFTs on the timechain are spam, you should take note. This isn't about spam. It's an attack on individual control.
For the record I increased my datacarrier size in Knots a bit to accommodate larger hash data structures. It's trivial to find a good solution among those who care about these things I laid out. The top Core devs are just dishonest to a frankly pathetic level. I don't want people to fall for their bullshit, 'tis why I'm posting. You should be absolutely fucking ashamed of yourself, @Jameson Lopp
As a node runner, you should be happy to verify your incoming transactions as valid. That's why you're running the node, right? My red line is economic transactions, I consider almost all other transactions as spam and waste, but I really don't get to say what others want to do with their bitcoin. If Bitcoin continues to work, then in the end, block space will be so valuable that only economic transactions will be rational.
Clarify which dictatorship you want. Because if it's not dictatorship of me over only my mempool and nobody else's, then as a matter of fact I am not running your idea of Bitcoin. I have control over my node. I have a mind and I use it to tailor my settings. What you want is a dictatorship of developers, ironically, just your preferred flavor of it.
Everyone running a node has control over their mempool. Some node runner wants to see the whole picture and all available valid transactions so they can clearly see what's going on in the network, some wants to filter some transactions out and see the network only partly and some want to see only specific transactions in the mempool. One noteworthy thing I noticed when playing with the filters was that, we have to download twice the transactions we try to filter. Once when we see them first time and reject it and second time when they enter in the block. It's not that bad but if one wants to optimize bandwidth usage they should not use any filters.
You have control over your node but not over what valid transactions are included in the blocks, except if you work and mine them by yourself. Mempools can be full of various transactions but only transactions that pay enough fee to be included in block are relevant in the end. I want developers to not dictate anything about transaction types. Bitcoin transaction is a digital message and I want everybody to be free to sign any kind of message they want as a transaction even if I and 99% of other users consider it spam/waste. We know that free market is the only way to filter transactions without dictatorship and I would like to have as many people as possible to understand that so we can continue with more productive discussions like Bitcoin privacy and censorship resistance.
Mempool sovereignty isn't a thing. Sure, you can do whatever you want with your mempool. Hell, you can completely turn it off with the "blocksonly" config! But eventually your node is going to download and validate transactions that you don't like if you're a spam hating Puritan. Thinking it makes a difference if the impure transactions touch your mempool is delusional.
You expect people to take that non-argument seriously? I have demonstrated repeatedly that my stance does not rest on any spam absolutist premise. And this disregards the reality that filters have an effect, which you implicitly agree with by your own actions. Which warrants, to any reasonable person, a response to the many legitimate arguments coming from the Knots side, which you always ignore. This really is a lackluster attempt at distorting the facts, Mr. Slop. I'm not very impressed by you. What's it like to be a professional grifter? Rewarding? It has no appeal to me, personally.
🛡️
Not much money to be made in snuff films. Who would be paying to upload this gabage? Doubt they could do much of this longterm. Unlawful acts like murder, filming murder, paying to upload it to a blockchain would obviously agressively prosecuted at the source. My node validating a transaction that contains a provably upspendable UTXO with questionable content, that I can then drop forever.......doubt this will be a problem
🛡️
I love the narrative of "I competed for and won that hat fair and square!" when it's a grown adult who bullied it out of the hands of the child. Soooo I guess that kid should have ... (checks notes) ... donned a Mech suit to fight back...?
testing zaps for this note… we made six attempts to⚡zap this note, at donal@speed.app, over a period of about 8 hours. Six of the zaps were successfully paid... please check for 6 satoshis received. problem: we found that your lightning address server **did not* properly produce zap receipts, and/or didn't send the zap receipts to the relays specified in the zap. (the zap spec requires that the zap receipts be sent to the relays specified in the zap.) this means a nostr user who zaps you might not see a number appearing next to the ⚡ icon after zapping.... if you wanted to fix this... you could try getting a free rizful lightning address -- ... if u get it set up, pls reply here so we can do this ⚡zap test again.