Kevin's Bacon on Nostr: Peter Todd is right, OP_RETURN is a better spot for arbitrary data and the limit ...
Peter Todd is right, OP_RETURN is a better spot for arbitrary data and the limit should be higher. I have mine at 160 on Knots (but at a high price if my mempool starts to get full). He's also wrong that there's no solution. The solution is #FixTheFilters for all other arbitrary data and let users choose which filters to use with enough information to understand.
Knots takes filters and user choice seriously. Many of the Core devs don't. Further, Core devs don't even entertain the other side of the debate, which makes it more difficult for users to have sufficient information to make an informed choice.
Published at
2025-05-09 02:38:29Event JSON
{
"id": "a294f41c6cdd33c5a3a804c1bb8493eecd6526768f18320d49f3c6a57178f386",
"pubkey": "3dda45008a0391d7933e1ae7cc3b844bfd91c92ddefd0f55ce6afd025776f2db",
"created_at": 1746758309,
"kind": 1,
"tags": [
[
"t",
"FixTheFilters"
],
[
"t",
"fixthefilters"
]
],
"content": "Peter Todd is right, OP_RETURN is a better spot for arbitrary data and the limit should be higher. I have mine at 160 on Knots (but at a high price if my mempool starts to get full). He's also wrong that there's no solution. The solution is #FixTheFilters for all other arbitrary data and let users choose which filters to use with enough information to understand.\n\nKnots takes filters and user choice seriously. Many of the Core devs don't. Further, Core devs don't even entertain the other side of the debate, which makes it more difficult for users to have sufficient information to make an informed choice.",
"sig": "750f5406a869b6233a0c716f3f112055a357ed63f57879fae78a20a79d647794fd48d86a74250d55ef903461007654173c5bd12829597e58aeeae7d6bf0bfe7d"
}
