HN user

jgershen

737 karma

Co-founder of GazeHawk (YC S10). website: jgershen.dev

Currently at assembled.com

Posts15
Comments56
View on HN

Actually, the probability that all decks ever shuffled are unique is also very high. We can approximate the probability that any two of the n decks shuffled in human history were identical as p=1-n^2/52!

Using the same estimate as the OP for n (1.56x10^23) gives p=3.02x10^-22. Still fantastically low.

Thanks for submitting this. After seeing the article that claimed the design of the iCloud icon was brilliant because it included Fibonacci ratios, I desperately wanted to nail this article to the (other) author's monitor.

Whenever I see that kind of unjustifiable Fibonacci-worship, I get the same feeling I do when I read creation myths or just-so stories. It honestly hurt the first time I read the truth, and realized I was taught many of the outlandish claims this author points out as fact in grade school math classes.

While the resolution of the webcam is (obviously) important when discerning accuracy, I feel like you may be conflating two terms here. Specifically, going from the resolution of the webcam to an estimate of so many pixels of accuracy using basic trigonometry will necessarily depend on the method you're using to convert the webcam input into eye-tracking data.

The <70 pixel figure for GazeHawk's accuracy is based on testing against real, labeled training data. That is the distance, on the screen, by which our calculated gazepoint differs from the true location at which the user's gaze was directed. It is only loosely correlated with webcam resolution, in that a higher webcam resolution corresponds to a larger pipeline - more input pixels being dumped into the eye tracking algorithm. I could be wrong, but it sounds like you're discussing the size of the eyes in the input image.

Also, at this point a discussion of accuracy vs. precision becomes germane. The use of higher resolution video as an input can often impact one but not the other.

Alpha Geek 15 years ago

Well, I wrote my thesis about cellular automata, and I promise I've considered Wolfram's set of ideas and perspectives. So while I can't prove anything about the popularity of Aaronson's review in general, your hypothesis is demonstrably false in at least n=1 instance.

That being said, I took a look at your website and GitHub (not to mention your employer, Wolfram Research) and it's obvious you know what you're talking about - I don't think you should be being downvoted as heavily in this thread as you are. Plus you made a Futurama reference, so you're obviously a cool dude.

My point is, let's all avoid implying that people who don't agree with us aren't qualified to discuss this subject. I think both of us are, and Wolfram is a pretty polarizing subject - one that all sides need to keep civil about sometimes.

Could you explain in more detail how these trigger a reboot? From writing a 32-bit kernel I understand how the triple fault method is supposed to work, for example, but would love to know a little more about these methods.

I had to reread the article to confirm that that sentence is actually in there. I honestly can't believe that a program which focuses on launching successful companies prioritizes "building your actual product" below meetings and finding mentorship.

I can't remember who said it, but I read somewhere that "the goal of every startup should be to stop being a startup" (the moral was that a startup is a fledgling business, and you should be trying to mature that business rather than staying in the beginning stages forever). If you're more interested in meeting people and talking about startups than you are in actually working on your startup, something is probably wrong. Not that this is a bad thing, but you should reevaluate whether being a startup founder is right for you.

[dead] 15 years ago

TL;DR - "Tu quoque."

Additionally, when I read Kara Swisher's article in AllThingsSD, the next thing I read was her own disclosure (http://allthingsd.com/about/kara-swisher/). It left me with the impression that she takes journalistic integrity very, very seriously (maybe even too seriously, honestly). Arrington's self-righteous, dismissive diatribe here leaves me with exactly the opposite impression about him.

If anyone wants to work on "artificial intelligence," then, GazeHawk is hiring!

(sorry for the spammy post, but I'm really impressed by the level of computer vision experience and talent showing up in this thread, and wanted to reach out to you all. We are a startup which is also actually solving hard CV problems)

Sorry for being unclear. I wasn't saying he - or anyone - is perfect. What I meant by that last part was that the moral of the story, to me, seems to be summed up pretty well in the two blog posts tptacek wrote and links to at the bottom of his profile page. (And maybe also Schneier's oft-repeated comments about how a system is only as strong as its weakest link.)

Very well written article - it does a terrific job of explaining things like rainbow tables for a non-technical (or at least, technically-but-not-security-minded) audience. The only part that seems off is the theme that /all/ of the exploited vulnerabilities were necessary to render HBGary vulnerable:

"Even with the flawed usage of MD5, HBGary could have been safe..."

They homebrewed their own password system. Can someone switch on the tptacek bat-signal?

Nice article; it reminds me of taking OS at CMU. There's something incredible about learning what happens all the way down when you call, say, printf. Suddenly the computer transforms from an incomprehensible black box into an fascinating marvel of engineering - but unlike a magician's act, the magic only gets better when you see how it works.