-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Topics: November update and new topics #286
Conversation
harding
commented
Dec 2, 2019
- Topic updates
- Four new topics (one per newsletter published in November)
- A one-line bugfix and a one-line template tweak
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this @harding!
How long did it take you to prepare this PR? It took me a little under an hour to review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great stuff. A few comments follow.
_topics/en/bech32.md
Outdated
url: /en/newsletters/2019/11/27/#how-does-the-bech32-length-extension-mutation-weakness-work | ||
date: 2019-11-27 | ||
|
||
- title: Impact of bech32 length-change mutablity on v1 segwit script length |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/mutablity/mutability
mobile devices with limited bandwidth and so chose low false-positive | ||
rates to minimize their bandwidth use. This meant that they | ||
essentially gave their list of addresses to any node they contacted. | ||
Higher false positive rates may have partially mitigated this privacy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: above, "false positive" was hyphenated twice, then here and twice more without the hyphen
|
||
Additionally, BIP37 filtering is performed independently for each | ||
client by nodes and it's possible for filters to be created in a way | ||
that requires nodes perform an extensive amount of CPU to filter each |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/perform/to perform/? and /CPU/CPU processing/?
rates to minimize their bandwidth use. This meant that they | ||
essentially gave their list of addresses to any node they contacted. | ||
Higher false positive rates may have partially mitigated this privacy | ||
leak but false positives would be created at random from the set of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Careful of shifting verb tense, previously was in the past, here it is conditional, and in the following paragraph shifts again to present, then shifts in the last sentence "This resulted..." back to past tense.
that requires nodes perform an extensive amount of CPU to filter each | ||
block. This resulted in a set of known DoS vectors against nodes. | ||
|
||
Although in practice, BIP37 allowed clients to use a fairly small |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/practice,/practice/ (remove the comma, I believe, or restructure)
bb2573e
to
b1bb07e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tACK
- Reviewed new topics (content, linking)
- Reviewed 'updates for November' text
- Tested 'updates for November' links
make production
for site successful
It was expected that privacy-focused users could mitigate this privacy | ||
loss by setting a higher false positive rate, but research suggests | ||
that the rate needs to be quite high in order to provide plausible | ||
deniability. The problem is a consequence of the different types of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a source we can link to that explains this? Everything from "The problem is a consequence of..." is perhaps a bit too low-level for a summary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, Jonas Nick's article already linked in the see also section. https://jonasnick.github.io/blog/2015/02/12/privacy-in-bitcoinj/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still think that this topic summary would be snappier with everything from "The problem is a consequence of..." onward removed. Do you think it needs to stay?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @harding . You've resolved all my previous review comments. I have a couple more for you :)
ping @harding . I think this is ready for merge after the last round of review comments from bitschmidty and me are addressed. |
Sorry, I haven't forgotten, just juggling several other things. I expect to get back to this Thursday. |
No rush. Just wanted to make sure you weren't waiting on something from me. |
b1bb07e
to
7c2e892
Compare
_topics/en/cpfp.md
Outdated
url: /en/newsletters/2019/06/19/#lnd-3140 | ||
date: 2019-06-19 | ||
|
||
- title: "Refactory preparing for ancestor relay" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/Refactory/Refactor/
It was expected that privacy-focused users could mitigate this privacy | ||
loss by setting a higher false positive rate, but research suggests | ||
that the rate needs to be quite high in order to provide plausible | ||
deniability. The problem is a consequence of the different types of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still think that this topic summary would be snappier with everything from "The problem is a consequence of..." onward removed. Do you think it needs to stay?
7c2e892
to
9d2a972
Compare