📅 Original date posted:2014-06-17
📝 Original message:On Tue, Jun 17, 2014 at 10:08 AM, Wladimir <laanwj at gmail.com> wrote:
> On Tue, Jun 17, 2014 at 10:02 AM, Matt Whitlock <bip at mattwhitlock.name> wrote:
>> On Tuesday, 17 June 2014, at 9:57 am, Wladimir wrote:
>>> Yes, as I said in the github topic
>>> (https://github.com/bitcoin/bitcoin/pull/4351) I suggest we adapt a
>>> string-based name space for extensions.
>>
>> Why use textual strings? These fields are not for human consumption. Why not use UUIDs, which are fixed length and will not waste as much bandwidth in the protocol? Or if you'd prefer a hierarchical namespace, you could use OIDs, a la ASN.1.
Also it IS useful for these fields to be human readable for
statistics, peer list views and such. When encountering a new, unknown
extension when connecting to a node it's much more useful to get a
google-able string to find out what it is about, than some long
hexadecimal or dotted-number identifier.
Wladimir
Wladimir [ARCHIVE] /
npub1xq…ymc2p
2023-06-07 15:22:58
in reply to nevent1q…hk5m
Author Public Key
npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2pPublished at
2023-06-07 15:22:58Event JSON
{
"id": "08efc1f5cfac912b58617dba3c40b776b5be6ad889aba8f3002dbb4b4371f0e6",
"pubkey": "30217b018a47b99ed4c20399b44b02f70ec4f58ed77a2814a563fa28322ef722",
"created_at": 1686151378,
"kind": 1,
"tags": [
[
"e",
"51755e520e5fac5e694b75add8f1aed031a6d31795ec0eb481e5e52e0d57e975",
"",
"root"
],
[
"e",
"cf2ebbcdb51de4bf3785c2162c372de615c30f34955e4e8943ac3601ec023181",
"",
"reply"
],
[
"p",
"30217b018a47b99ed4c20399b44b02f70ec4f58ed77a2814a563fa28322ef722"
]
],
"content": "📅 Original date posted:2014-06-17\n📝 Original message:On Tue, Jun 17, 2014 at 10:08 AM, Wladimir \u003claanwj at gmail.com\u003e wrote:\n\u003e On Tue, Jun 17, 2014 at 10:02 AM, Matt Whitlock \u003cbip at mattwhitlock.name\u003e wrote:\n\u003e\u003e On Tuesday, 17 June 2014, at 9:57 am, Wladimir wrote:\n\u003e\u003e\u003e Yes, as I said in the github topic\n\u003e\u003e\u003e (https://github.com/bitcoin/bitcoin/pull/4351) I suggest we adapt a\n\u003e\u003e\u003e string-based name space for extensions.\n\u003e\u003e\n\u003e\u003e Why use textual strings? These fields are not for human consumption. Why not use UUIDs, which are fixed length and will not waste as much bandwidth in the protocol? Or if you'd prefer a hierarchical namespace, you could use OIDs, a la ASN.1.\n\nAlso it IS useful for these fields to be human readable for\nstatistics, peer list views and such. When encountering a new, unknown\nextension when connecting to a node it's much more useful to get a\ngoogle-able string to find out what it is about, than some long\nhexadecimal or dotted-number identifier.\n\nWladimir",
"sig": "eadf3e58772c3f1777c035f3ea10ce6673adfa6f7d718192939f8036e50ee751888a4b727b1e2aad85a65f481e80d5dfe4b01231f7d44c98b3857faaecbafc64"
}