It's incredibly sad to see such low effort click bait on nostr - and some zapping this "car crash".
No, @Luke Dashjr is not a bad actor (except for blocking me on Twitter, which he can't do here on nostr. Muahahaha). He's a bit special but was often right on things where my initial impulse told me that he was wrong and most definitely wants Bitcoin to succeed more than most anything else, so I would vouch for him not being a bad actor 100%.
Is Luke being abused by a bad actor in this case? Is Mechanic a bad actor? I don't know. The debate about CSAM on the blockchain feels a bit like that. We had that debate many years ago, apparently nasty stuff is in the blockchain but my bitcoin tools don't show it to me and I wouldn't download tools that would parse the blockchain for images. The argument that you would need special software for the prior cases but not for the future cases is stupid as - guess what - you will always need "special software" to view images in something that's not purpose built for images. A "blk04169.dat" won't accidentally get opened with image software and with "special software" you can even find images in actual transactions that nobody put images in in the first place.
To discuss filters in the context of what is legal in your jurisdiction is a slippery slope and can only harm Bitcoin.
So do I stand with Core in this debate? Actually no, not yet at least. But luckily it's not that binary neither. I won't run knots but I won't update my full nodes any soon neither. Policy filters are a 🖕 to people abusing or attacking Bitcoin and node operators should not get policy filters taken away precisely to avoid this heated debate. Policy filters are an escape valve for things that some would like to see as consensus rules but can't quite convince all to go that route. Let people filter out big OP_RETURNs if they want to. Set the default to 100kB and see what happens. Welding close this escape valve was Core's error and now they get the heat.
Yes, filters don't work but they send a message. Your dick pics are not wanted here. If Core wants them, let the individual miners at least send that statement clearly.
It's incredibly sad to see such low effort click bait on nostr - and some zapping this "car crash".
No, @Luke Dashjr is not a bad actor (except for blocking me on Twitter, which he can't do here on nostr. Muahahaha). He's a bit special but was often right on things where my initial impulse told me that he was wrong and most definitely wants Bitcoin to succeed more than most anything else, so I would vouch for him not being a bad actor 100%.
Is Luke being abused by a bad actor in this case? Is Mechanic a bad actor? I don't know. The debate about CSAM on the blockchain feels a bit like that. We had that debate many years ago, apparently nasty stuff is in the blockchain but my bitcoin tools don't show it to me and I wouldn't download tools that would parse the blockchain for images. The argument that you would need special software for the prior cases but not for the future cases is stupid as - guess what - you will always need "special software" to view images in something that's not purpose built for images. A "blk04169.dat" won't accidentally get opened with image software and with "special software" you can even find images in actual transactions that nobody put images in in the first place.
To discuss filters in the context of what is legal in your jurisdiction is a slippery slope and can only harm Bitcoin.
So do I stand with Core in this debate? Actually no, not yet at least. But luckily it's not that binary neither. I won't run knots but I won't update my full nodes any soon neither. Policy filters are a 🖕 to people abusing or attacking Bitcoin and node operators should not get policy filters taken away precisely to avoid this heated debate. Policy filters are an escape valve for things that some would like to see as consensus rules but can't quite convince all to go that route. Let people filter out big OP_RETURNs if they want to. Set the default to 100kB and see what happens. Welding close this escape valve was Core's error and now they get the heat.
Yes, filters don't work but they send a message. Your dick pics are not wanted here. If Core wants them, let the individual miners at least send that statement clearly.
Login to reply
Replies (11)
the CSAM part of the debate is about which players in this game have an incentive to degrade the reputation of bitcoin. those are obviously competitors to bitcoin, and the number one competitor to bitcoin is the JPM/Consensys backed Ethereum project.
it is true that the content requires special tools to decode, but all binary data requires special tools to decode, even text requires a mapping between ascii/unicode and the glyphs to render text to a screen, but this doesn't change the fact that such data is displacing legitimate transaction content of private individuals making payments and managing their L2 systems, so filtering helps lower the clearance time of legitimate transaction content. transactions themselves also need "special software" to decode, so this whole line of reasoning is a dead end, and does not clear the spammers of their indictments.
and it's a very good reason to oppose anyone promoting non-monetary transactions on bitcoin, because they are going to use it to scam and defraud users with their fraudulent proof of stake and mutable governance of protocols that is the base nature of all shitcoin chains, trying to dress scams in the legitimacy of registered financial operations that are themselves also, in fact, fraudulent and malicious to most people stupid enough to participate in these "markets" of manipulated, endlessly debased tokens (stocks, bonds, smart contracts, all the same if you ask me).
"Policy filters are an escape valve for things that some would like to see as consensus rules but can't quite convince all to go that route"
Unfortunately these large OP_RETURN transactions are within consensus, as everyone knows already. I'm with you in that I'm not switching to Knots nor am I upgrading to anything above 28.x for the moment, not until we see what actually happens with 30.
Drop this nonsense, and get to work on quantum resistant address migrations now.
Mechanic a bad actor? You asking that question and sitting on a spam fence is telling. It's like you're trying to be this easy going friendly observer who doesn't want to piss anyone off but in the end says "let's set the default to 100kb and see what happens". Are you the bad actor I wonder?
So you're saying increasing the default is 100% the same as removing control?
No, no, no...not sure where you got that from. I was suggesting that you may be a bad actor.
Yep...
He admits he doesnt understand Cores argument. Like you said, friendly observing fence sitter, which is probabaly where you should be. Next step though if to listen to both arguments and make an informed decision on who is correct or how they might be both wrong. Instead he is virtue signalling unfortunately
GM🤙👍
Fence sitting never suited me I'm afraid, and to sit on the fence is one thing, but to lean over and touch the grass because you really don't belong on the fence but are too afraid to jump, that's just being a pussie.