Paul Sztorc [ARCHIVE] on Nostr: 📅 Original date posted:2017-07-11 📝 Original message:Greg, I would summarize ...
📅 Original date posted:2017-07-11
📝 Original message:Greg,
I would summarize your email as stating that: you regret writing the
first email, and regret the fact that it became a roadmap that everyone
signed. And that therefore it is obviously a concept NACK from you.
( That's pretty surprising to me, and I would expect others to find it
surprising as well. And I wonder whether you think we should take the
old one *down*, and why you would allow (?) so many other people to sign
it, etc. But I am not willing to press the issue. Some of your other
comments I also find confusing but there is little to be gained in
clarifying them. )
Generally, I still think that the roadmap was a helpful communication
device, which did more good than harm. And I am interested in hearing
what other people think.
Separately, and very important to me, is that you feel that there are
unresolved objections to drivechain's security model, which you decline
to share with me and/or the list. So I would hope that you instead
choose to share your thoughts (as is, presumably, the purpose of this list).
I will also respond to this:
>>> A fine intention, but I've checked with many of the top contributors
>>> and it sounds like the only regular developer you spoke with was
>>> Luke-Jr. Next time you seek to represent someone you might want to
>>> try talking to them!
>> That is false. I could provide a list of names but I'm really not sure
>> what would be gained as result. You yourself admit that it is an
>> excellent list of research, almost all which you support directly.
>>
>> So I think your only real objection is that I didn't talk to you
>> specifically.
> Come now, this is needlessly insulting. I would have made the same
> comment if you had talked to me because you didn't talk to most/all of
> Matt Corallo, Wladimir, Pieter Wuille, Alex Morcos, etc.... e.g. the
> people doing most of the work of actually building the system. Before
> making that comment I went and checked with people to find out if only
> I was left out. Talking to Adam (who isn't involved in the project)
> and Luke-jr (who is but is well known for frustratingly extreme
> minority positions and also contracts for Blockstream sometimes) isn't
Let me try to explain my point of view. I did speak to several people,
in addition to the two names that I privately volunteered to you when
you asked me in a personal email earlier today. From my point of view
you had done no research (you failed to uncover any additional names),
used the information I volunteered to you against me (in the form of
false characterizations of negligent email writing!), and you also
suggested that, other than yourself and a few others, no one is
qualified even to write a first draft of a summary of present day
activities. This response is typical of the hostile review environment
which has existed in Bitcoin for years (I am more than used to it). If
instead of writing the first draft, I had written nothing, I would be
accused of being the ideas guy and/or "not contributing". You also
(rather rudely), put me in an awkward position, as the people who I
*did* ask now almost certainly prefer that I not reveal their names
(yet, a low name count is held as a strike against my competence).
Such are the perils of posting to bitcoin-dev! Let all be warned! : )
Paul
On 7/11/2017 8:07 PM, Gregory Maxwell wrote:
> On Tue, Jul 11, 2017 at 10:17 PM, Paul Sztorc <truthcoin at gmail.com> wrote:
>> I don't understand this at all. This document attempts to do exactly
>> what its predecessor did -- nothing more or less.
> That might be your impression, then you've misunderstood what I
> intended-- What I wrote was carefully constructed as a personal view
> of how things might work out. It never claimed to be a a project
> roadmap. Though as usual, I work hard to propose things that I believe
> will be successful... and people are free to adopt what they want.
>
> And to the extent that it got taken that way I think it was an error
> and that it has harmed progress in our community; and created more
> confusion about control vs collaboration.
>
> With perfect hindsight I wouldn't have posted it; especially since
> we've learned that the demand for increased capacity from many people
> was potentially less than completely earnest. (The whole, can't double
> capacity until we quadruple it thing...)
>
>> As to your specific complaints, I have addressed both the security model
> and the concept of mining centralization on this list in the recent
> past.
>
> I don't agree that you have; but for the purpose of this thread
> doesn't really matter if I (specifically) do or don't agree. It's an
> objective truth that many people do not yet believe these concerns
> have been addressed.
>
>> I really don't understand what you are disclosing. That Adam asked you
>> for feedback on the draft? And then, in the next sentence, that not
> That Adam asked me to write publish a new "roadmap" for Bitcoin as
> you've done here, with particular features and descriptions, which I
> declined; and explained why I didn't believe that was the right
> approach. And Adam worked with you on the document, and provided
> content for it (which I then recognized in the post).
>
> Set aside what you know to be true for a moment and consider how this
> might look to an outsider who found out about it. It could look a
> like Blockstream was trying to influence the direction of Bitcoin by
> laundering proposals through an apparently unaffiliated third party.
> Doubly so considering who participated in your drafting and who didn't
> (more below).
>
> I don't think in actuality you did anything remotely improper
> (ill-advised, perhaps, since your goal to speak for developers but you
> didn't speak to them, IMO--) but I think transparency is essential to
> avoid any appearance of misconduct.
>
>> But surely you can
>> appreciate how bizarre your position on roadmaps is. What exactly, did
>> you intended to create at [1]? Since it is described explicitly as "the
>> roadmap in Capacity increases for the Bitcoin system", have you been
>> disagreeing with it's characterization as a 'roadmap' this entire time?
>> One wonders why you haven't said anything until now.
> I did--
>
> As Bryan pointed out... with the exception of the intro and end and a
> couple sentences in the middle my entire response to your post, with
> the position on "roadmaps" was written a long time ago, specifically
> to complain about and argue against that particular approach.
>
>> In my first email I list the benefits of having a roadmap. One benefit
>> is that, without one, it is likely that a large majority of outsiders
>> have almost no idea at all what is being worked on, what effect it will
>> have, or when it might be ready, or to whom/what they should turn to for
>> advice on such matters. Do you have a different way of addressing this
>> communication problem?
> I think you may be mistaking a roadmap with "communications"-- people
> taking about research they are exploring is great! and we should have
> more of it. But like with RedHat and kernel features, we can't really
> roadmap things that are unresourced and currently just unimplemented
> exploration or test code-- without seeing things which are more or
> less done the community can't rightfully decide if they'd want to
> support something or not. Perhaps they'll be good things perhaps
> awful-- the devil is in the details, and until an effort is fairly
> mature, you cannot see the details.
>
> There have, for example, been signature aggregation proposals in the
> past that required address reuse (could only aggregate if they're
> reused). I would strongly oppose such a proposal, and I hope everyone
> else here would too. So if I were a third party looking at your
> message, rather than the person who initially proposed the agg sig
> thing you're talking about, I wouldn't know if I could love it or hate
> it yet; and probably couldn't be expected to have much of an opinion
> on it until there is a BIP and/or example implementation.
>
> To the extent that a roadmap differs from communications in general,
> it is in that it also implies things that none of us can promise
> except for our own efforts; Completion of implementations, success of
> experiments, adoption-- basically assuming a level of top down control
> that doesn't exist in a wide public collaboration.
>
> One of the great challenges in our industry is that we don't have
> rings of communication: We don't have much in the way of semi-experts
> to communicate to semi-semi-experts to communicate to media pundits to
> communicate to the unwashed masses-- at each level closing the
> inferential gap and explaining things in terms the audience
> understands. We don't have things like LWN. We'll get there, but it
> it took the Linux world decades to build to what it has now. I think
> various forces in the industry work against us-- e.g. we lose a mot of
> mid tier technical people to the allure of striking it rich printing
> money in their own altcoins.
>
> It might be attractive to try to end-run the slow development
> appropriate web of reliable communications by deploying high authority
> edicts, but it ultimately can't work because it doesn't map to how
> things are accomplished, not in true collaborative open source, and
> certainly not in an effort whos value comes substantially from
> decentralization. Doing so, I fear, creates a false understanding of
> authority.
>
> (It's a common misunderstanding, for example, that people do what I
> want (for example); but in reality, I just try to avoid wasting my
> time advocating things that I don't think other people are already
> going to do; :) otherwise, if _I_ want something done I've got to do
> it myself or horse trade for it, just like anyone else.)
>
> One of the great things about general communications is anyone can do
> it. Of course, unless they're talking about their own work, they
> can't promise any of it will be completely-- but that is always true.
> If someone wants some guarantee about work, they have to be willing
> to get it done themselves (and, of course, if it's a consensus
> feature-- that much is necessary, but still not sufficient to get a
> guarantee).
>
> [from your other reply]
>>> A fine intention, but I've checked with many of the top contributors
>>> and it sounds like the only regular developer you spoke with was
>>> Luke-Jr. Next time you seek to represent someone you might want to
>>> try talking to them!
>> That is false. I could provide a list of names but I'm really not sure
>> what would be gained as result. You yourself admit that it is an
>> excellent list of research, almost all which you support directly.
>>
>> So I think your only real objection is that I didn't talk to you
>> specifically.
> Come now, this is needlessly insulting. I would have made the same
> comment if you had talked to me because you didn't talk to most/all of
> Matt Corallo, Wladimir, Pieter Wuille, Alex Morcos, etc.... e.g. the
> people doing most of the work of actually building the system. Before
> making that comment I went and checked with people to find out if only
> I was left out. Talking to Adam (who isn't involved in the project)
> and Luke-jr (who is but is well known for frustratingly extreme
> minority positions and also contracts for Blockstream sometimes) isn't
> a great approach for the stated goal of speaking for developers!
Published at
2023-06-07 18:04:21Event JSON
{
"id": "0c42902ad5a6d8c824c4205d2bd7af06e2b98db43fe195a24611c6fcf100d1ee",
"pubkey": "7ac0bd39b854f24cbf067103758f3a9d398c23832d6d75824d190ae35c6c23be",
"created_at": 1686161061,
"kind": 1,
"tags": [
[
"e",
"0dbbb3b4fffe9287047e58a8fa04c4b6c95589f2269ea5553f7cb2691feb3b03",
"",
"root"
],
[
"e",
"a05b9b5575c03f35ce52af2c6fc2c2f9696caab34cb884b53f25f97e46fbe7fe",
"",
"reply"
],
[
"p",
"4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73"
]
],
"content": "📅 Original date posted:2017-07-11\n📝 Original message:Greg,\n\nI would summarize your email as stating that: you regret writing the\nfirst email, and regret the fact that it became a roadmap that everyone\nsigned. And that therefore it is obviously a concept NACK from you.\n\n( That's pretty surprising to me, and I would expect others to find it\nsurprising as well. And I wonder whether you think we should take the\nold one *down*, and why you would allow (?) so many other people to sign\nit, etc. But I am not willing to press the issue. Some of your other\ncomments I also find confusing but there is little to be gained in\nclarifying them. )\n\nGenerally, I still think that the roadmap was a helpful communication\ndevice, which did more good than harm. And I am interested in hearing\nwhat other people think.\n\nSeparately, and very important to me, is that you feel that there are\nunresolved objections to drivechain's security model, which you decline\nto share with me and/or the list. So I would hope that you instead\nchoose to share your thoughts (as is, presumably, the purpose of this list).\n\nI will also respond to this:\n\n\u003e\u003e\u003e A fine intention, but I've checked with many of the top contributors\n\u003e\u003e\u003e and it sounds like the only regular developer you spoke with was\n\u003e\u003e\u003e Luke-Jr. Next time you seek to represent someone you might want to\n\u003e\u003e\u003e try talking to them!\n\u003e\u003e That is false. I could provide a list of names but I'm really not sure\n\u003e\u003e what would be gained as result. You yourself admit that it is an\n\u003e\u003e excellent list of research, almost all which you support directly.\n\u003e\u003e\n\u003e\u003e So I think your only real objection is that I didn't talk to you\n\u003e\u003e specifically.\n\u003e Come now, this is needlessly insulting. I would have made the same\n\u003e comment if you had talked to me because you didn't talk to most/all of\n\u003e Matt Corallo, Wladimir, Pieter Wuille, Alex Morcos, etc.... e.g. the\n\u003e people doing most of the work of actually building the system. Before\n\u003e making that comment I went and checked with people to find out if only\n\u003e I was left out. Talking to Adam (who isn't involved in the project)\n\u003e and Luke-jr (who is but is well known for frustratingly extreme\n\u003e minority positions and also contracts for Blockstream sometimes) isn't\n\nLet me try to explain my point of view. I did speak to several people,\nin addition to the two names that I privately volunteered to you when\nyou asked me in a personal email earlier today. From my point of view\nyou had done no research (you failed to uncover any additional names),\nused the information I volunteered to you against me (in the form of\nfalse characterizations of negligent email writing!), and you also\nsuggested that, other than yourself and a few others, no one is\nqualified even to write a first draft of a summary of present day\nactivities. This response is typical of the hostile review environment\nwhich has existed in Bitcoin for years (I am more than used to it). If\ninstead of writing the first draft, I had written nothing, I would be\naccused of being the ideas guy and/or \"not contributing\". You also\n(rather rudely), put me in an awkward position, as the people who I\n*did* ask now almost certainly prefer that I not reveal their names\n(yet, a low name count is held as a strike against my competence).\n\nSuch are the perils of posting to bitcoin-dev! Let all be warned! : )\n\nPaul\n\n\n\n\nOn 7/11/2017 8:07 PM, Gregory Maxwell wrote:\n\u003e On Tue, Jul 11, 2017 at 10:17 PM, Paul Sztorc \u003ctruthcoin at gmail.com\u003e wrote:\n\u003e\u003e I don't understand this at all. This document attempts to do exactly\n\u003e\u003e what its predecessor did -- nothing more or less.\n\u003e That might be your impression, then you've misunderstood what I\n\u003e intended-- What I wrote was carefully constructed as a personal view\n\u003e of how things might work out. It never claimed to be a a project\n\u003e roadmap. Though as usual, I work hard to propose things that I believe\n\u003e will be successful... and people are free to adopt what they want.\n\u003e\n\u003e And to the extent that it got taken that way I think it was an error\n\u003e and that it has harmed progress in our community; and created more\n\u003e confusion about control vs collaboration.\n\u003e\n\u003e With perfect hindsight I wouldn't have posted it; especially since\n\u003e we've learned that the demand for increased capacity from many people\n\u003e was potentially less than completely earnest. (The whole, can't double\n\u003e capacity until we quadruple it thing...)\n\u003e\n\u003e\u003e As to your specific complaints, I have addressed both the security model\n\u003e and the concept of mining centralization on this list in the recent\n\u003e past.\n\u003e\n\u003e I don't agree that you have; but for the purpose of this thread\n\u003e doesn't really matter if I (specifically) do or don't agree. It's an\n\u003e objective truth that many people do not yet believe these concerns\n\u003e have been addressed.\n\u003e\n\u003e\u003e I really don't understand what you are disclosing. That Adam asked you\n\u003e\u003e for feedback on the draft? And then, in the next sentence, that not\n\u003e That Adam asked me to write publish a new \"roadmap\" for Bitcoin as\n\u003e you've done here, with particular features and descriptions, which I\n\u003e declined; and explained why I didn't believe that was the right\n\u003e approach. And Adam worked with you on the document, and provided\n\u003e content for it (which I then recognized in the post).\n\u003e\n\u003e Set aside what you know to be true for a moment and consider how this\n\u003e might look to an outsider who found out about it. It could look a\n\u003e like Blockstream was trying to influence the direction of Bitcoin by\n\u003e laundering proposals through an apparently unaffiliated third party.\n\u003e Doubly so considering who participated in your drafting and who didn't\n\u003e (more below).\n\u003e\n\u003e I don't think in actuality you did anything remotely improper\n\u003e (ill-advised, perhaps, since your goal to speak for developers but you\n\u003e didn't speak to them, IMO--) but I think transparency is essential to\n\u003e avoid any appearance of misconduct.\n\u003e\n\u003e\u003e But surely you can\n\u003e\u003e appreciate how bizarre your position on roadmaps is. What exactly, did\n\u003e\u003e you intended to create at [1]? Since it is described explicitly as \"the\n\u003e\u003e roadmap in Capacity increases for the Bitcoin system\", have you been\n\u003e\u003e disagreeing with it's characterization as a 'roadmap' this entire time?\n\u003e\u003e One wonders why you haven't said anything until now.\n\u003e I did--\n\u003e\n\u003e As Bryan pointed out... with the exception of the intro and end and a\n\u003e couple sentences in the middle my entire response to your post, with\n\u003e the position on \"roadmaps\" was written a long time ago, specifically\n\u003e to complain about and argue against that particular approach.\n\u003e\n\u003e\u003e In my first email I list the benefits of having a roadmap. One benefit\n\u003e\u003e is that, without one, it is likely that a large majority of outsiders\n\u003e\u003e have almost no idea at all what is being worked on, what effect it will\n\u003e\u003e have, or when it might be ready, or to whom/what they should turn to for\n\u003e\u003e advice on such matters. Do you have a different way of addressing this\n\u003e\u003e communication problem?\n\u003e I think you may be mistaking a roadmap with \"communications\"-- people\n\u003e taking about research they are exploring is great! and we should have\n\u003e more of it. But like with RedHat and kernel features, we can't really\n\u003e roadmap things that are unresourced and currently just unimplemented\n\u003e exploration or test code-- without seeing things which are more or\n\u003e less done the community can't rightfully decide if they'd want to\n\u003e support something or not. Perhaps they'll be good things perhaps\n\u003e awful-- the devil is in the details, and until an effort is fairly\n\u003e mature, you cannot see the details.\n\u003e\n\u003e There have, for example, been signature aggregation proposals in the\n\u003e past that required address reuse (could only aggregate if they're\n\u003e reused). I would strongly oppose such a proposal, and I hope everyone\n\u003e else here would too. So if I were a third party looking at your\n\u003e message, rather than the person who initially proposed the agg sig\n\u003e thing you're talking about, I wouldn't know if I could love it or hate\n\u003e it yet; and probably couldn't be expected to have much of an opinion\n\u003e on it until there is a BIP and/or example implementation.\n\u003e\n\u003e To the extent that a roadmap differs from communications in general,\n\u003e it is in that it also implies things that none of us can promise\n\u003e except for our own efforts; Completion of implementations, success of\n\u003e experiments, adoption-- basically assuming a level of top down control\n\u003e that doesn't exist in a wide public collaboration.\n\u003e\n\u003e One of the great challenges in our industry is that we don't have\n\u003e rings of communication: We don't have much in the way of semi-experts\n\u003e to communicate to semi-semi-experts to communicate to media pundits to\n\u003e communicate to the unwashed masses-- at each level closing the\n\u003e inferential gap and explaining things in terms the audience\n\u003e understands. We don't have things like LWN. We'll get there, but it\n\u003e it took the Linux world decades to build to what it has now. I think\n\u003e various forces in the industry work against us-- e.g. we lose a mot of\n\u003e mid tier technical people to the allure of striking it rich printing\n\u003e money in their own altcoins.\n\u003e\n\u003e It might be attractive to try to end-run the slow development\n\u003e appropriate web of reliable communications by deploying high authority\n\u003e edicts, but it ultimately can't work because it doesn't map to how\n\u003e things are accomplished, not in true collaborative open source, and\n\u003e certainly not in an effort whos value comes substantially from\n\u003e decentralization. Doing so, I fear, creates a false understanding of\n\u003e authority.\n\u003e\n\u003e (It's a common misunderstanding, for example, that people do what I\n\u003e want (for example); but in reality, I just try to avoid wasting my\n\u003e time advocating things that I don't think other people are already\n\u003e going to do; :) otherwise, if _I_ want something done I've got to do\n\u003e it myself or horse trade for it, just like anyone else.)\n\u003e\n\u003e One of the great things about general communications is anyone can do\n\u003e it. Of course, unless they're talking about their own work, they\n\u003e can't promise any of it will be completely-- but that is always true.\n\u003e If someone wants some guarantee about work, they have to be willing\n\u003e to get it done themselves (and, of course, if it's a consensus\n\u003e feature-- that much is necessary, but still not sufficient to get a\n\u003e guarantee).\n\u003e\n\u003e [from your other reply]\n\u003e\u003e\u003e A fine intention, but I've checked with many of the top contributors\n\u003e\u003e\u003e and it sounds like the only regular developer you spoke with was\n\u003e\u003e\u003e Luke-Jr. Next time you seek to represent someone you might want to\n\u003e\u003e\u003e try talking to them!\n\u003e\u003e That is false. I could provide a list of names but I'm really not sure\n\u003e\u003e what would be gained as result. You yourself admit that it is an\n\u003e\u003e excellent list of research, almost all which you support directly.\n\u003e\u003e\n\u003e\u003e So I think your only real objection is that I didn't talk to you\n\u003e\u003e specifically.\n\u003e Come now, this is needlessly insulting. I would have made the same\n\u003e comment if you had talked to me because you didn't talk to most/all of\n\u003e Matt Corallo, Wladimir, Pieter Wuille, Alex Morcos, etc.... e.g. the\n\u003e people doing most of the work of actually building the system. Before\n\u003e making that comment I went and checked with people to find out if only\n\u003e I was left out. Talking to Adam (who isn't involved in the project)\n\u003e and Luke-jr (who is but is well known for frustratingly extreme\n\u003e minority positions and also contracts for Blockstream sometimes) isn't\n\u003e a great approach for the stated goal of speaking for developers!",
"sig": "71f4914c25ac35408a0e77f532b8660eca6dcab2262bc9f3106ba642059a4e9a8903cdf6032f02876bfcc2e9c901a11a60790729e1f2fada5da67c2ec443acc7"
}