Still easy to filter for the F word hidden in first letters, start by looking for sentences that start with an F. Helps reduce compute vs having the filter check every combination for you. Increaded productivity, you can code a filter for that in a sec. This will work for sure, no one will think of a path around because it would be too whack.
Faster that you could finish the code for the F word at the beginning of sentences I just snuck another F bomb and a new profanity in.
You underestimate my pattern detection! I'm onto you.
I'm too lazy to encode a reply back, but yeah, I get the whole encoding being arbitrary thing. I guess this topic heated up the past day for some reason.
Someone made it a think of the children thing.
Authoritarians always do.
Authoritarian stems from a central control, please remind me of the central control mechanism in bitcoin.
Knots is trying to make its filters a central control.
Please go on, explain. I would love to see how you equate options to force.
Failing to get where you wanted to go doesn't mean you weren't trying.
They want to take away options for transaction types.
Transaction types like what? Are you referring to OP_RETURN because that is an entirely unspendable output so THAT can't be a transaction. Unless you think 40 bytes isn't enough for a 32 byte imprinted hash anchor.
It isn't enough for whirlpool. Do we believe users deserve privacy or not?
Because one implementation of coinjoining needs 4 more bytes of data (which you can set in your node BTW unless you suddenly think filters work) that's why OP_RETURN needs 100KB?
Do you want everyone to run knots filters?
If not you don't want anything about bitcoin to change you are just selfish and externalizing costs and risks demanding I do it for you.
If so, you would ban whirlpool.
What I want is irrelevant. What I do is the matter. Also, nothing about whirlpool REQUIRES 46 bytes. They are just not good at using metadata hashes efficiently.
