📅 Original date posted:2013-06-20
📝 Original message:Hi Mike,
The issue with the current parser is that those fields are conditionally optional on that there will be no subsequent fields added.
If there will be further fields they will become manadory.
Why not bump the version and parse the fields as mandatory from then on? This would be backward compatible and cleaner
going forward.
Tamas Blummer
http://bitsofproof.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130620/3b03828f/attachment.html>;
Tamas Blummer [ARCHIVE] /
npub1cc…ex8m8
2023-06-07 15:03:45
in reply to nevent1q…p3vq
Author Public Key
npub1ccegg9n9lnx6huppxg43m95488yur7pfemkn3pz0agjws5ffvtts0ex8m8Published at
2023-06-07 15:03:45Event JSON
{
"id": "6e4354aebeb6e86d491321a789eb8ef0dbbbb5b038ebc0ad6066d0e66d58f909",
"pubkey": "c632841665fccdabf021322b1d969539c9c1f829ceed38844fea24e8512962d7",
"created_at": 1686150225,
"kind": 1,
"tags": [
[
"e",
"e9b1d9a1ddf5c8677e9abe0f134ce38b3c249cc7d3052122574b8fda5672d89b",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2013-06-20\n📝 Original message:Hi Mike,\n\nThe issue with the current parser is that those fields are conditionally optional on that there will be no subsequent fields added.\nIf there will be further fields they will become manadory. \n \nWhy not bump the version and parse the fields as mandatory from then on? This would be backward compatible and cleaner\ngoing forward.\n\nTamas Blummer\nhttp://bitsofproof.com\n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130620/3b03828f/attachment.html\u003e",
"sig": "a9bdf40dfc2bab331a63e7274b7659bd4a6742619a1f9e5641803da1701e15dbbfad6fee23726f2b07652bcbf6d8ade6701b7b257af8980e7a76502e25c12575"
}