An amusing aspect of the latest twist in the filters drama is that these folks have been complaining for years about jpegs in the blockchain and apparently only just realized that jpegs could contain horrific content like child porn.
Filteroos are already a decade behind on this debate and I doubt they'll ever catch up at this rate.
Again being disingenuous. It's never been contiguous data, and you know that is the distinction, obviously.
That's irrelevant, but I welcome anyone who disagrees to hire legal counsel and have them publish an actual legal opinion. I'm not interested in the opinion of folks LARPing as lawyers.
I don't give a fuck about the law, I don't want VLC playable contiguous bytes on my goddamn server. You aren't arguing on twitter here Lopp, people know shit here. You think nerds can't see through your perverse incentive bullshit?
Oh good, then we agree it's not an actual threat.
I have bad news for you, however: Bitcoin doesn't care about your feelings.
Yeah, that's why I use implementations that don't pass along your smut. Also, why does it even matter Citrea uses fake keys for your Rollup Vitalik wannabe bullshit, OP_RETURN doesn't even affect your bottom line. (Unless you are a fed that is)
You're coping with ridiculous pretzel logic. Your node will still download and share said smut after it arrives in a block. Even if you run Knots.
Then I and others will expose the Miner responsible for distributing CSAM. Irreparable reputational damage. You are the pretzel here, filters don't work, that's why you have to disable them on the policy level... Yeah, real sound logic there.
Go for it.
Bitcoin as a system doesn't give a shit about reputation, it pays whoever mints a valid block.
Damn, that Ivory tower really detatches people from reality. People are still made of flesh. A reputation of what you're describing, you would be far more paranoid than you already are. Bitcoin is only money not a force-field.
state secrets and illegal pictures are already embedded in the blockchain using much older protocols like stamps. the data is unprunable. no matter which node software you use to synchronize you are already dirtying your hands with this stuff and you can't prevent it.
there are probably illegal samples of data embedded in the trading history of low volume penny stocks on the stock market. it's not possible to prevent people from embedding and propagating arbitrary data in a public append-only database system. you are trying to have your cake and eat it too. if you are so disturbed by the possibility, you need to put bitcoin down and find a different computer hobby. you clearly don't understand how any of this stuff works.
Did you not read the first comment? Contiguous data is different. You should put nostr down, you clearly can't read.
>contiguous data is different
Since you won't read my citation anyway I'll just suffice it to say, take your favorite CSAM, that I'm sure you have, convert the MP4 to bytes and then have a program like VLC read it. Then chop the file into several chunks with OP code identifiers, data signal and length bytes and see if VLC does the same thing. Later tard.
did you actually suggest illegal files become legal when they are segmented
Are you really unable to read, I was kind of joking but I think you may need help.
A quote from me, literally in this thread: "I don't give a fuck about the law"
I hope you are able to read this 🙏
There is a distinction here: whether it is fragmented or whole. Legally whole likely makes you more complicit than fragmented. I doubt it’ll stand up in court, but the case could be made. And that’s a risk. Surprised core does not wargame these types of scenarios with their updates …
Bitcoin doesn't care about your feelings, too.
Or your conflicts of interest with citrea.
It is a threat though and it’s odd that you wouldn’t know it. Having your data directly visible vs fragmented is flying it close to the sun legally speaking. You could argue you didn’t know about it - but all that it takes to negate this is someone tweeting then going CP in an op return. At least fragmenting gives you some plausible deniability regarding the “knowing” aspect.
Again, disingenuous. Bitcoin doesn't care about any of our feelings, but you just said you care about lawyers feelings.
Legally you’re probably right - even data in chunks can be turned into a visual. But why would you want to make it easier for anyone to abuse?
GFY you liar. We've been vocally pissed off about spam for years. Its not new.
Your reading comprehension is terrible. Read his post again slowly and you will discover your comment is dumb.
nostr:naddr1qqxnzde4xcurqv3e8yunvdfsqythwumn8ghj7un9d3shjtnp0faxzmt09ehx2ap0qgs9zs7rw003k4y2wltea360yuj46y5md9d4yt0mt06rfx96fdgpm7grqsqqqa28m608ea
What? I thought ppl have been saying that for years
An amusing aspect and something to think about is people like you having the need to come out with public disingenuous statements about something that is supposed that have no effect.
I enjoy posting controversial opinions that I expect will age well over the long term.
Lmao
Youre a shit stirrer that causes division for your own ends. Youre a disgrace to this movement
Bitcoin is for shit stirrers 👌
It gives me the feeling that you are desperately looking for attention and your only way to get it is this, you seem very lonely
Go outside, touch the grass and look for friends.
Har har, you are so superior
Is MARA going to put CP into blocks? Are you telling me that's an actual risk?
Always has been...
A slight risk sure. But a much smaller risk than just anyone, unvetted by a regulated company with a brand image to uphold, putting whatever they want onchain. Mechanic has a very good point there. And once again you are ignoring all arguments. You take 0 responsibility in your position at Core.
Because they’re paid off to support the changes by the VCs with alterior motives to support their business endeavors
That, plus he's evil. Perfectly willing to lie to everyone to achieve parasitic goals.
A lot of Core are philosophically illiterate too. They don't really understand what makes Bitcoin work on a fundamental level. And that is private property.
And they don't know how to reason in reality. They don't see the whole picture. They can't do the logical calculus of so many moving parts and they just assume, which is itself a kind of evil.
This is beside the fact that Knots is not an anti-spam implementation. It's a highly configurable implementation, and you lie about that too to hide the fact that you are being intellectually dishonest to take away configuration options and to arbitrate the majority of mempool policies to the way you see fit, as if you think for everyone else. It is fraud of a sort, once you silence discussion and misrepresent the facts like you have been.
nostr:nprofile1qqs0w2xeumnsfq6cuuynpaw2vjcfwacdnzwvmp59flnp3mdfez3czpsprpmhxue69uhkummnw3ezumr0wpczuum0vd5kzmp0ksxxx2 from a purely selfish point of view, is it better or worse for me as a pleb node runner to have to store more arbitrary data on my node. I just can’t see how it’s better for me. It definitely feels worse that the option to filter has been removed.
From a resources standpoint you're basically talking about the block size limit, which remains unchanged. With regard to OP_RETURN data like what's currently being discussed, it actually imposes less resource costs upon your node in terms of CPU usage, bandwidth usage, and hard disk usage.
That's because OP_RETURN data does not receive a discount like witness data.
This only works if you also filter out non-OP_RETURN arbitrary data, which you are against, ya jackass.
I have higher data carrier limits than typical, at 160, because that's what I reasoned was the best policy. 83 bytes might actually be better as it is the standing tradition, and projects can optimize for that. Either way, I DON'T GET TO DICTATE THE SETTING FOR OTHER PEOPLE. So the fact that most people relay only up to 83 bytes or less, is a check against my assessment that 160 bytes is fine.
This is all besides the fact that your stated goals regarding miner centralization, like many other BS arguments you and your team put out, are a lie, as these goals would be better served by (A) engaging in an intellectually honest way and (B) embracing DATUM and advocating the use of or creation of competitors to OCEAN.
I would not ask Jameson LARP for insight into my concerns, personally. His entire persona is a facade.
Your Casa Nodes were complete crap.
You are not an Authority on Nodes, or over them.
So they have lowered themselves to the level of the European Union - ChatControl
Why is the default filter at v30 so large... Essentially removed, it was not always like that... Fix the filters at v30
They find this amusing. Not surprised.
A noteworthy difference tho.
Pre-nuked OP_RETURN: you need specialised tools and expertise to reconstruct dozens if not hundreds of fake pubkey utxos to reconstruct and see a CP file from the blockchain. Plausible deniability.
Post-nuked OP_RETURN: you get the CP file in its bare state. No excuses will gonna cut it. GG
Do you know you can earn daily from mining?, send me a dm
this post shows your clear lack of understanding of the attack, exploit, and how this all started and came here years ago.
but based on people you hangout with i can even say that, you might be trying to corrupt bitcoin on purpose because of your hatred of it.
and idk if your followers will ever catch up to see the lack of logic in your deceitful arguments.
you had time to change but since you showed no signs of growth, at this point its clearly you are destructive on purpose. you are a threat to bitcoin, and you should get what you deserve.
I think it's because nobody was talking about child porn until suddenly some anti knots people brought it up for some bizarre reason, kinda shooting themselves in the foot by trying to argue that core is better because it allows this and allowing horrible shit somehow makes it less edgy to share it
I do remember in the past, years ago, when the main issue about spammers was that it would bloat things so much normal people wouldn't be able to afford big enough hard drives to run nodes.
I remember back then that preventing child porn being put on the blockchain was also part of the discussion, back then.
But the problem seemed solved until core Devs decided to go against the community recently.
Like if you are having trouble understanding I can break it down right now right.
So allowing spam will make it more expensive for people to run nodes, that is the main argument against spam.
Allowing child porn will make it ILLEGAL FOR PEOPLE TO RUN NODES.
now this is the crazy part right, allowing spam also means allowing child porn.
Nice post showing how dumb the core side is. Small tiny shit pictures of a couple of bytes are just annoying and retarded on a monetry blockchain, but with the upcoming 100kb pictures it will be possible to post pics of much higher ress, making real bad stuf possible.
Fuck you.
any public record can be turned into a store for arbitrary jpegs. You just need to XOR it to the pic and make the result available
