HN user
" Levon Arakelyan pulled out an estimated 450 truckloads of rubble, exclusively by metal bucket. He gave it all to a local company which used it in various construction projects."
Sounds like he didn't profit from it during his lifetime but his wife now runs it as a tourist attraction. Perhaps would have been appropriate for the construction company to have contributed something along the way.
If nerve agents can be spawned in secrecy, then the ability of police to detect will always lag behind. Nations inherently need to get involved to efficientize resources.
ICO's will likely continue as long as the incentives to create a new token outweigh basing an idea off an existing chain. The old "better to have a small piece of a big pie than a large piece of a small pie" apply less here - if investors want in, they'll buy either way.
How carefully have you analyzed the MITM proxy you are using? Many have security holes and you may be opening yourself up to attacks. Modern browsers have placed a lot of effort into security, you may be undoing a lot of the transport security.
right, so the coin toss example is not related to all the outcomes but rather just the most recent. In contrast, the OP seems to show that a prime is related to a previous prime - and that previous prime is related to a previous - so by extent, they are all related.
"If Alice tosses a coin until she sees a head followed by a tail, and Bob tosses a coin until he sees two heads in a row, then on average, Alice will require four tosses while Bob will require six tosses (try this at home!), even though head-tail and head-head have an equal chance of appearing after two coin tosses."
Counter-intuitive at first but makes sense - the outcomes as a whole converge towards the average (50% heads, 50% tails). Nonetheless, it shows that each toss is related to the others. One can expect that primes are even more related - or at least to the primes that came before.
in some case, if you're able to switch libraries, you might also be able to switch languages and therefore skip on future issues inherent to C. Consider for example: https://golang.org/pkg/crypto/tls/
There must be a worthwhile reason - the added complexity of certs is non-trivial [1]. Perhaps certs are deemed less easily transferable compared to API keys (simple strings)?
[1] https://developer.apple.com/library/ios/documentation/IDEs/C...
"example client that I wrote in Go for a client that doesn't have access to an HTTP/2 library"
on line 62 you do specify HTTP/2: Transport: &http2.Transport
"Since it uses HTTP/2, you can just use an existing HTTP library (which should handle reusing the connection for multiple notifications, too)."
I doubt many non-HTTP/2 implementations will keep connections open and continually check for more data - why wait and read for Response(s) if no Requests were sent? Let alone an HTTP version sent they do not understand.