Yet with knots you can't run a dojo or use #Ashigaru, the best privacy focused wallet. Or BIP47 a static, private payment option.
Discussion
Better, since as I demonstrated, Whirpool was completely buggy, and Ashigaru also has serious privacy issues.
Well we will have to agree to disagree. If you only use BIP 47 then you're privacy is increased massively. Knots sounds, on the surface, like a good ideavbut in reality is a tool for censorship. Which in reality is easily bypassed. Miners will do anything for money and as it is the miners that discover the blocks, all knots will do is produce broken nodes. What percentage are they at now, 15%? If the miners don't run it, its dead in the water and I'm not going to slag of it's designer, who "lost" all his btc to a hacker and asked the world how????
Let's see, up until version 25 of Core, the filters worked fine, version 25 broke them, and going back to version 24 is censorship?
That argument doesn't hold water. Before version 25, we all agreed on what spam was.
Knots is simply a form of protest and a wake-up call to core developers.
what privacy issues does ashigaru have?
I’ve heard Luke say that dojo is poorly designed. Could be re-worked to be able to fit inside the datacareiersize limit. He even said he could do this for them, but since all they did was to attack and insult him, he didn’t want to do it. Can’t blame him.
This from the man who got hacked. Even if that was opsec, he is hardly someone to follow. I believe in a lot of what is being said here but too many are blindly following an idiot. Has the core team overstepped their remit? Possibly. Has the knots team fixed a perceived problem? Definitely knot! As stated earlier, it is miners that decide, not nodes. If 85% of nodes ran knots, then you may have a say, until then knots is just going to create problems.
That “idiot” gave you Lightning and practically won us the Blocksize war. He could be weird, but he’s not an idiot. He got hacked because to some extent he’s suffering from the same issue other devs do: engineering syndrome. He got overconfident about his opsec/skills and got rekt. Core devs are evidently going down the same road today: introducing “fixes” without any regard for second and third order effects. They’ll end up rekt someday in a similar fashion. The question is will they drag us along with them.
Knots would not work with those by default. One of the great things about knots is you can configure it however you want. You can set your OP_RETURN limit to 83 or whatever you need and still filter out other types of spam.
The biggest problem with core is they are trying to dictate to the network what node policy should be by default and taking away the ability to configure it.
The problem with the changes they are making are a seperate issue but just as important. nostr:nprofile1qqs8fl79rnpsz5x00xmvkvtd8g2u7ve2k2dr3lkfadyy4v24r4k3s4spz9mhxue69uhkummnw3ezuamfdejj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uqsuamnwvaz7tmwdaejumr0dshsu0ur8h has some great videos on this subject. Even if you disagree with him, at least hear his arguments.
You could even set it to core's defaults if you wanted to, the whole point of knots is it should be YOUR choice. That and the defaults should be what they always have been.