HNHacker News
TopNewBestAskShowJobs

anfedorov

365 karma · joined October 2, 2011

(currently) andrey@sig.ma

(formerly) andrey@heapanalytics.com andrey@desmos.com andrey@humblebundle.com anfedorov@google.com andrey@invitemedia.com andrey@gamechanger.io andrey@conductor.com

submissionscomments
anfedorov··on HTTPS Everywhere Version 5: Sixteen New Languages and Thousands of New Rules
And that's not the only problem:

https://github.com/EFForg/https-everywhere/issues/144

https://github.com/EFForg/https-everywhere/issues/849

anfedorov··on Truecrypt report
It's the third paragraph, not right on top.
anfedorov··on Google pulling China CNNIC CA from its products
It's just an organizational decision. CNNIC is super trustworthy to a lot of people. It's so many people, in fact, that they can't possibly verify all of the sites these people want to visit. So instead of burdening CNNIC with verifying the identity of every single site that wants a cert that their users will trust, CNNIC will just verify some other CAs as being trustworthy enough to do the job.

Personally, I think I should trust the hardware or OS manufacturer to pick exactly who is trustworthy enough to certify websites, since I'm trusting them that my computer is doing what it looks like it's doing anyway.

anfedorov··on React Native is now open source
OK, so I can legally use React-Native in my app while suing Facebook for unrelated patent infringement. I also can claim the patent they are suing me for infringing is invalid while continuing to use React-Native.

Would it be practically advisable to do so?

anfedorov··on React Native is now open source
Are you nitpicking legal semantics (including something in one agreement or another), or saying it's possible to legally use React-Native while suing Facebook for completely unrelated patent infringement?
anfedorov··on React Native is now open source
I am not a lawyer, but perhaps they could just skip the second paragraph? I understand the motivation behind discouraging people from suing you, but putting "you will not sue us for patent infringement" into a software license is a bit weird.
anfedorov··on Elsevier sold me a Creative Commons non-commercial licensed article
It's possible that Wiley received one license while Elsevier received another. Just because one publisher got CC CN ND doesn't mean that's the only license that was ever granted.
anfedorov··on Ask HN: Can A give permission to C to access B, without B talking to A?
You certainly could. If you want to add something more complicated like an expiration time to prevent replay attacks, it might be a good use case for JSON Web Tokens: http://jwt.io/
anfedorov··on Is it really 'Complex'? Or did we just make it 'Complicated'? [video]
Only familiar with one of them, but "teachers are taught science as a religion" seems spot-on.
anfedorov··on Update on Sony Investigation
The US gains literally nothing pointing the finger at North Korea.

It also loses nothing, which might be the case if Russia or China were behind the attacks.

anfedorov··on How to program computers (kOS)
Not to be confused with kOS [1]?

1. http://ksp-kos.github.io/KOS_DOC/

anfedorov··on Heartbleed disclosure timeline: who knew what and when
I believe standard procedure would be for IRS to report it to US-CERT who are part of the Department of Homeland Security.

At which point (I imagine), decisions would be made along the same lines as I described, the key questions being "can we keep it secret?" and "who has this capability?".

I tried to be nation-agnostic, as I imagine there may be a bit of difference in how a given nations' intelligence agency weighs the value of their offensive capabilities and the public defensive capabilities in light of who knows about the bug.

anfedorov··on Heartbleed disclosure timeline: who knew what and when
In a pre and post-Snowden world, I would imagine if a government discovers a bug like Heartbleed and has no evidence of anyone else knowing about it, they will classify it and use it offensively. They will then collect evidence and construct a model of who else knows of the vulnerability and weigh the costs (to their offensive capabilities) and benefits (to everyone's defensive capabilities) of disclosing it publicly.

Once there is reason to believe that the benefits outweigh the costs, they will disclose it in a way that doesn't expose their knowing about it beforehand.

anfedorov··on OpenSSL is written by monkeys (2009)
Date on the article might belong in the title: 2009-08-24
anfedorov··on Ethereum, Bitcoin’s most ambitious successor
How does this work as the network scales? If I understand it correctly, every node needs to execute every contract. This means that for some large enough number of nodes, it must either cost more for the network to perform the computation than any constant cost of execution, or the cost of contracts must vary by the size of the network executing them. Could someone more knowledgeable about the project explain more?
anfedorov··on Moto 360
I think that it wouldn't be a problem with a plastic laptop, so specifying that it was a MBP makes sense. "Aluminum laptop" might have sufficed, as well, but that sounds a little weird.
anfedorov··on Show HN: Real-time server monitoring in your browser
Error:

  [2014-03-10 15:38:12] ERROR TypeError: nil can't be coerced into Fixnum
	/usr/local/Cellar/ruby/2.1.1/lib/ruby/gems/2.1.0/gems/server_metrics-1.2.0/lib/server_metrics/collectors/memory.rb:81:in `+'
Here's the output:

  [~] top -l1 -n0 -u
  Processes: 268 total, 3 running, 5 stuck, 260 sleeping, 2070 threads
  2014/03/10 15:36:26
  Load Avg: 1.92, 2.05, 2.08
  CPU usage: 4.46% user, 12.50% sys, 83.3% idle
  SharedLibs: 60M resident, 0B data, 4156K linkedit.
  MemRegions: 73352 total, 3529M resident, 83M private, 892M shared.
  PhysMem: 6726M used (1812M wired), 199M unused.
  VM: 570G vsize, 1312M framework vsize, 1570984(0) swapins, 1861805(0) swapouts.
  Networks: packets: 2441317/1583M in, 1428870/324M out.
  Disks: 3446592/122G read, 1578215/101G written.
anfedorov··on Behind the stick of the SR-71
Related: http://www.econrates.com/reality/schul.html
anfedorov··on Apple Explains How Secure iMessage Is
After the slides detailing how easy it is for NSA to break into Apple phones I'd be simply shocked if they hadn't inserted such a vulnerability.

The slides pertained to physical access to an iOS 6 device, which was publicly known as insecure before the NSA revelations:

http://apple.slashdot.org/story/13/08/01/2024212/iphone-hack...

anfedorov··on If You Used TorMail, the FBI Has Your Inbox
?
anfedorov··on If You Used TorMail, the FBI Has Your Inbox
> The FBI in particular has a pattern of getting indicted for re-selling sensitive data

Source?

anfedorov··on Google Video Quality Report
I'm pretty sure he meant "email" and misspoke. The overall point that the people regulating things often don't know as much about them as a specialist would, but it seems rude to laugh at a small mistake like that.
anfedorov··on Watsi x Goldbely Holiday Gift Package
If you inspect the source, you'll see that the form where you enter your credit card is an https site in an iframe. That will protect you against a passive MITM attack, which is what most people worry about when submitting credit cards to a website.
anfedorov··on Facebook Warns Users After Adobe Breach
Curious... that's not the first I've heard of this happening recently.
anfedorov··on Media for Thinking the Unthinkable
Jargon and specialized notation is sometimes cryptic as an unintentional side effect of communicating efficiently between specialists. To suggest they should communicate findings in a less efficient way that's understandable by laymen who haven't put in the effort to learn the jargon / notation is silly.

But I think Bret's point isn't that every research paper should be as verbose as an introductory textbook, but rather that interactive widgets can express ideas which text and static images in published papers can't.

anfedorov··on Media for Thinking the Unthinkable
I'm a big fan of Bret Victor's thinking, but this part struck me as indicative of the criticisms he'll receive:

"here, they are discussing some relationships: the regular latice, L grows linearly with n, we see L growing linearly with n, and we see C is staying constant. In the random network, L grows logarithmically, and we see L growing logarithmically, we see C going as a reciprocal relationship. When we read the word "logarithmic", we don't need to reconstruct that relationship in our head, you can just see it"

Does the average reader of Nature need to be shown a graph of what a linear, constant, logarithmic, and inverse relationship looks like? I don't think so.

That said, I imagine there are highly terse and technical ideas that cannot be simply represented in the current mediums of publication and which could benefit greatly using a presentation using an interactive widgets, making more complex ideas more easily communicable.

anfedorov··on Painless Decorators in Python
Great library! I wrote something similar once [1] and thought two special cases might be useful to optimize for: a predecoration that modifies the arguments to a function and a postdecoration that modifies the return value.

1. https://github.com/anfedorov/decorations

anfedorov··on "BadBIOS" features explained
I think the point is that anyone with an ounce of technical competence knows that the claim of formerly a normal computer being infected via sound is patently absurd, so even bringing it up is unnecessarily distracting from the discussion at hand.
anfedorov··on Contrary to public claims, Apple can read your iMessages
They didn't use dodgy language: "conversations which take place over iMessage and FaceTime are protected by end-to-end encryption so no one but the sender and receiver can see or read them. Apple cannot decrypt that data." [1].

1. https://www.apple.com/apples-commitment-to-customer-privacy/

anfedorov··on Contrary to public claims, Apple can read your iMessages
AFAIK, the Lavabit case is not legally decided yet:

  http://www.volokh.com/2013/10/11/lavabit-challenges-contempt-order/
I imagine Apple would put up quite a strong legal fight if they were issued the same order, especially considering their public stance.

A NSL can force Apple to not disclose it, but they can't force them to publically lie about it. And lying about that would be ridiculously stupid.

← PreviousPage 4 of 5Next →