BitcoinSV ‘feature’ exploited to store child abuse imagery on the blockchain https://t.co/iJELq6aHr1 I wonder what the Minister for Digital Things is going to do about this one? A code of conduct for the blockchain cannot be far away...
You and your little "drama" buddies are too busy staring at men's bussies to know an attractive woman if she swam up to you in anthropomorphic-shark form and let you fuck her on a cold, windy cape cod beach.
This is my only concern about raising OP_RETURN data size. You could argue that several small transactions that can be stitched together to form such imagry doesn't count since you would need special software to put it together, but that's basically just an opinion
The problem is *storing* those images. Bad people do that now. TOR doesn't require you store CP for it to function, although you may *unknowingly* be transmitting it. With BSV, by having a copy of the blockchain, you are *knowingly storing and transmitting it.* I think we need to fight to make it impossible for such things to be stored on a public blockchain, for the good of our movement.
Edit: wait can't we just prune that shit? It's OP_RETURN anyway
Not to mention, the problem is ultimately intractable. Binary data can be encoded in any medium that allows modulation. It could be made _impractical_ or _expensive_ to store arbitrary data, but only by sacrificing usability of the chain.
_Somebody_ has to store it (or multiple somebodies have to each store parts of it) and others have to be able to request it if you want the chain to be publicly verifiable. Large OP_RETURNs are the most straightforward way to store files, but they are far from the only way to encode data on the chain. They tend to be preferable because they can be pruned, but if someone really wants their content to remain available and is willing to pay for it, there are many harder to detect approaches that do not lend themselves to easy pruning.