drgo on Nostr: As the reference implementation, core should have “the best” policies from a ...
As the reference implementation, core should have “the best” policies from a genuine comp sci and networking perspective, not a commercial one.
Any major policy decisions should be handled at the fork level. Want more data carrier size? Fork it! The thought that this should be debated on github is laughable.
Published at
2025-05-02 06:21:46Event JSON
{
"id": "3cc2b1202cafb10a0b096555dd98385be5a2ef9406c85296a7a3a250d15c8e2b",
"pubkey": "4f4f82846698ff66ae5fa9fad4c0c4eb7823afb07fa9f54ea9d15f1217ae96cc",
"created_at": 1746166906,
"kind": 1,
"tags": [
[
"e",
"ee08de00b4bdedf07b6c69acec00567c2068422cc0dda5ac6676949272fcfe7e",
"",
"root"
],
[
"e",
"77a99dadbc7fdd3ea006b12ecb5d943e0f09cce55a428de3287e232cfc8a86db",
"",
"reply"
],
[
"p",
"675b84fe75e216ab947c7438ee519ca7775376ddf05dadfba6278bd012e1d728"
],
[
"p",
"8685ebef665338dd6931e2ccdf3c19d9f0e5a1067c918f22e7081c2558f8faf8"
]
],
"content": "As the reference implementation, core should have “the best” policies from a genuine comp sci and networking perspective, not a commercial one. \n\nAny major policy decisions should be handled at the fork level. Want more data carrier size? Fork it! The thought that this should be debated on github is laughable.",
"sig": "10be79da92dfc8efd29634e40d6ea346be93ec760c12bf2e8f3a1dc4515867564868e2046d9ab1458037a668bc1395799eeb4d12f2ac1da5f33414f32721a14a"
}
