I mean, there is probably a transcription in the video, but my understanding is that spam filters do work sufficiently (without a hardfork) if core would accept the pull request of the spam filter. It doesn't catch everything, but it creates an environment where only the most sophisticated spammers can get through. The fact that this option is being ignored, and then stating because we can't stop it we must do x, is an attack on bitcoin. It's a form of gas lighting by disregarding solutions that address the spam directly. He addresses what I think is core's central point: The proposed spam filter won't stop x so we won't merge it (back in 2023). Mechanic relates it to essentially x being at the tail end of a normal distribution, meaning it doesn't work 100% of the time. Now fast forward to now and the proposed change by core is: Because we can't stop the spam then why should we have one. Which can be rephrased to: Because we can't stop 100% of the spam then why should we have one.
It's the fallacy of composition and division: https://www.logicalfallacies.org/fallacy-of-composition-and-division.html
Here is the video:
https://www.youtube.com/watch?v=15biQH1H140
twofish
npub1nc…e29r0
2025-05-01 23:24:38
in reply to nevent1q…ecv0
Author Public Key
npub1ncxn5tzmmackrdhjfrj94ayq5026my3esntsefpp0x6jtcnu42uqye29r0Published at
2025-05-01 23:24:38Event JSON
{
"id": "0d19228e7f630531d2250564f4a2fb4553937ec1bd7d09a5f8addbd5db43f4ba",
"pubkey": "9e0d3a2c5bdf7161b6f248e45af480a3d5ad923984d70ca42179b525e27caab8",
"created_at": 1746141878,
"kind": 1,
"tags": [
[
"e",
"885e3f4d2f4f06cb726ac4a0eb667c427560eb4b6407a99ae9ad4dc56f1ae943",
"",
"root"
],
[
"e",
"bfb8260e6bf852fe78a34cf6429014379fb3ba2e04b462c8068763229a8a7e16"
],
[
"e",
"0c75b15a76041ff05a0c919318012bb13b0d43ed5ff0b2fa71f6dea578e18141",
"",
"reply"
],
[
"p",
"e83b66a8ed2d37c07d1abea6e1b000a15549c69508fa4c5875556d52b0526c2b"
],
[
"p",
"390b5334739c171d82c84fe7c853462d7607537187f2a0695ede3b297a5b988c"
],
[
"p",
"9e0d3a2c5bdf7161b6f248e45af480a3d5ad923984d70ca42179b525e27caab8"
],
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
],
[
"r",
"https://www.logicalfallacies.org/fallacy-of-composition-and-division.html"
],
[
"r",
"https://www.youtube.com/watch?v=15biQH1H140"
]
],
"content": "I mean, there is probably a transcription in the video, but my understanding is that spam filters do work sufficiently (without a hardfork) if core would accept the pull request of the spam filter. It doesn't catch everything, but it creates an environment where only the most sophisticated spammers can get through. The fact that this option is being ignored, and then stating because we can't stop it we must do x, is an attack on bitcoin. It's a form of gas lighting by disregarding solutions that address the spam directly. He addresses what I think is core's central point: The proposed spam filter won't stop x so we won't merge it (back in 2023). Mechanic relates it to essentially x being at the tail end of a normal distribution, meaning it doesn't work 100% of the time. Now fast forward to now and the proposed change by core is: Because we can't stop the spam then why should we have one. Which can be rephrased to: Because we can't stop 100% of the spam then why should we have one.\n\nIt's the fallacy of composition and division: https://www.logicalfallacies.org/fallacy-of-composition-and-division.html\n\n\nHere is the video: \n\nhttps://www.youtube.com/watch?v=15biQH1H140",
"sig": "56f69ddc22b9fcd9c6a5bbb0a036e3e117d61b45028c3b1ae5e11912d2822cabcb0d22187cece7416827f7cddffe943ee83b9ad1052b1f0741d7c7ea002596a7"
}