Martin Sustrik [ARCHIVE] on Nostr: š
Original date posted:2013-10-23 š Original message:On 22/10/13 16:08, Jeff ...
š
Original date posted:2013-10-23
š Original message:On 22/10/13 16:08, Jeff Garzik wrote:
> All that is good practice, but we should avoid adding burdensome
> process that might discourage BIP writing.
>
> Consider a distributed approach: if you feel a draft needs more
> sections or better language, submit a pull request yourself and help
> community-edit the document.
I would love to do so.
However, from what Peter Todd said above, my feeling was that spec is
deliberately vague to force compatibility with the reference
implementation rather than with a document.
While that kind of compatibility-via-obscurity won't probably work in a
long run, in short run it can prevent proliferation of implementations
and thus give protocol more space and flexibility to evolve (I've done
the same trick with ZeroMQ myself once).
Anyway, if my impression was wrong I am happy to give it a try.
Martin
Published at
2023-06-07 15:07:46Event JSON
{
"id": "a06217a7a1ee2abc9fd4901fc2c6bd5fdc159e4b82df547879fd352dcfc615ca",
"pubkey": "a07382f2047b309ebb8303d291bbe36556308187afdeaea697a464e7d3a93c53",
"created_at": 1686150466,
"kind": 1,
"tags": [
[
"e",
"7825845c40e7246842c64e1640ea39dcb04d6d8f430fae7ba311b465db0e4d0f",
"",
"root"
],
[
"e",
"dd9bf6c91809d651affb138605d9c89b7abdd931b5cdecef560b2e544efb88ef",
"",
"reply"
],
[
"p",
"b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11"
]
],
"content": "š
Original date posted:2013-10-23\nš Original message:On 22/10/13 16:08, Jeff Garzik wrote:\n\u003e All that is good practice, but we should avoid adding burdensome\n\u003e process that might discourage BIP writing.\n\u003e\n\u003e Consider a distributed approach: if you feel a draft needs more\n\u003e sections or better language, submit a pull request yourself and help\n\u003e community-edit the document.\n\nI would love to do so.\n\nHowever, from what Peter Todd said above, my feeling was that spec is \ndeliberately vague to force compatibility with the reference \nimplementation rather than with a document.\n\nWhile that kind of compatibility-via-obscurity won't probably work in a \nlong run, in short run it can prevent proliferation of implementations \nand thus give protocol more space and flexibility to evolve (I've done \nthe same trick with ZeroMQ myself once).\n\nAnyway, if my impression was wrong I am happy to give it a try.\n\nMartin",
"sig": "f8fbd5dbd65f6693bb116ddafeee7adacebeb7e0582f065f5b8cdf8b4cddd1841912f32b5aed55266546009b5772fa627f1a85c7c51ff517c17bbde28c125831"
}