You made me look this up. *Is it "concision" or "conciseness" - http://raymondpward.typepad.com/rainman2/2005/11/is_it_conci...

I prefer the relative concision of "concision" (9 chars vs. 11).

Eh, that's my cute answer. I really just think "conciseness" sounds awkward.

Should be "Scheme -> C compiler".

I'm no security expert, but I don't think you even need an out-of-band key exchange mechanism. Just use public key cryptography [1], as used in SSH/TLS/PGP/GPG.

[1] http://en.wikipedia.org/wiki/Public-key_cryptography

I was about to write this response, but I see that it is more clearly written in the wikipedia article already:

Another potential security vulnerability in using asymmetric keys is the possibility of a man-in-the-middle attack, in which communication of public keys is intercepted by a third party and modified to provide different public keys instead. Encrypted messages and responses must also be intercepted, decrypted and re-encrypted by the attacker using the correct public keys for different communication segments in all instances to avoid suspicion. This attack may seem to be difficult to implement in practice, but it's not impossible when using insecure media (e.g. public networks such as the Internet or wireless communications). A malicious staff member at Alice or Bob's ISP might find it quite easy to carry out. In the earlier postal analogy, Alice would have to have a way to make sure that the lock on the returned packet really belongs to Bob before she removes her lock and sends the packet back. Otherwise the lock could have been put on the packet by a corrupt postal worker pretending to be Bob to Alice.

The workaround is to either exchange the public keys out of band, or distribute a certificate which can be used to verify public keys out of band.

This could be very painful for the likes of Mahalo. I remember Jason Calcanis mentioning, perhaps when he first noted a change of direction for Mahalo to high-quality content, that he'll make sure Mahalo is the number one Google result for "how to cook a turkey" and similar queries, where they've spent hundreds of dollars (maybe more) on quality content, notably videos. I just Googled "how to cook a turkey", without quotes, and Mahalo is nowhere to be seen! Not sure if tha t's a good thing or a bad thing, but the guys at Mahalo might just be freaking out right now.

One of Mahalo's "pride and joy" results was "How to Play Guitar". They were #2 for a while, now they're 5-6.

Their "How to Play Guitar" page is actually pretty good. It should easily be 3 or 4, ahead of wikiHow, guitarreference, and about.com.

Mahalo is the top result here. Brazilian Google, but with language set as English. Removing the .br from the url takes Mahalo to the second place.

http://www.google.com.br/search?client=opera&rls=en&...

Yeah, it's overlooked by many that the Chrome isn't all that extensible compared to what you can do in Firefox with addons. Chrome's developer tools are built in because they must be, whereas Firebug should be able to do anything that Firefox does natively (though I think it may be mostly Javascript now).

Maybe you'd like Mirah?

http://www.mirah.org/

I've been listening to those talks.

They're only about an hour to 1.5 hours long, and there's only 6 of them. They are supposed to be spread over a 6 week period. So every week for six weeks, you need to find an hour to spend listening to the talk for that week.

You will be meditating during part of the talk. Other days, you will meditate 20-30 minutes. This is not a large time commitment, and since you're on HN, I'm guessing you'd be able to manage.

Good luck! The first two talks have been pretty nice so far.

Is it similar to self-hypnosis CDs?

With bezier curves (it's prettier) in Canvas/Coffeescript (assuming an existing global canvas context 'ctx'):

    heart = (scale,x,y)->
      ctx.beginPath()
      ctx.moveTo(x,y)
      p1 = [x-75*scale,y+20*scale]
      ctx.bezierCurveTo(x-20*scale,y-55*scale,p1[0]-50*scale,p1[1]-55*scale,p1...)
      p2 = [x,p1[1]+60*scale]
      ctx.bezierCurveTo(p1[0]+25*scale,p1[1]+22.5*scale,p2[0]-35*scale,p2[1]-40*scale,p2...)

      ctx.moveTo(x,y)
      p1 = [x+75*scale,y+20*scale]
      ctx.bezierCurveTo(x+20*scale,y-55*scale,p1[0]+50*scale,p1[1]-55*scale,p1...)
      p2 = [x,p1[1]+60*scale]
      ctx.bezierCurveTo(p1[0]-25*scale,p1[1]+22.5*scale,p2[0]+35*scale,p2[1]-40*scale,p2...)

      ctx.strokeStyle = 'rgba(255,40,20,0.7)'
      ctx.stroke()
    
    heart(1.0, 450, 250)

Also would be interesting to see how HN points are correlated to page views.

And raganwald was referring to the '#!' hack, since it's really just the '#' hack. He wasn't addressing the history api.