jeff18

Was it a critical security flaw?

Pretty sure it meant to go with http://news.ycombinator.com/item?id=1531004... pretty surreal.

So that you don't have to convince a customer to download and install an untrusted binary from your website -- the website is the product itself.

That's interesting that a piece of tape does indeed fix the problem. On last week's TWiT, one of the antenna engineers they had on kept saying how tape doesn't solve it.

I believe stylesheets must be downloaded first before any further rendering can be done. Therefore you block rendering until all images have finished downloading, while a traditional external image sprite can be downloaded asynchronously.

I may be naive, but how about this?

a) Escape everything 100%.

b) Look for <a> tags, grab their href attribute, escape it, and insert them as <a href='$1'>$2</a>.

c) Do the same for <b>, <p>, etc.

How would that be vulnerable to XSS? A small whitelist of HTML would be replaced safely, and any script tags and so on would be escaped and displayed as is.

Strong disagree. Chrome is the only major browser that doesn't have native support for RSS. Even Internet Explorer does! Hell, it doesn't even understand RSS -- it simply shows the raw XML source.

Because of this, many blogs have links to their RSS/Atom feed with a fat "Subscribe" logo -- on Chrome, when you click that, you get a massive page of unparsed XML.

Whether a given grandma knows what RSS is or not is beside the point, it's lame of Google not to follow a defacto standard that many sites rely upon when there is no technical reason not to.

It seems weird the Chrome works so hard to integrate PDF / Flash / etc. so the users don't have to think about it and really push the envelope with their browser... yet they refuse to even honor RSS.

Chrome doesn't even have an RSS icon at all!

I think Posterous took 5 steps forward and 1 step backward with their campaign. Their diction was a small blemish, not a mortal wound.

It seems like the only meat of the article is the following:

> I think there are economies of scale that will fail to materialize for a company targeting to move 20,000 of its sedans annually in a couple of years. Drivers who may be drawn to the novelty may begin to fret over service and parts.

That is a neat opinion, but it would be more interesting to explain in detail why he believes this. Is there any evidence that this is not possible or is it just a gut feeling without any due diligence? Basically, I think Toyota's massive investment in TSLA carries a little more weight than this article and I'd like to see some actual research before "throwing it away".

> most of Posterous users are starting fresh

Posterous heavily promotes migrating your blog from other services.

> Not moving because of urls seems like not switching to a Mac because you have all the Windows keyboard shortcuts memorized.

In the spirit of the recent "raw unsolicited advice" to Posterous trend, here are my thoughts: I was impressed when you guys responded saying you were going to add this feature soon. However, playing it down with car, phone, and operating system analogies feels sort of patronizing and makes me worry that you guys might not understand the full scope of the issue:

a) You will lose all of your page rank

b) Anyone who has linked to you (including yourself) will have a broken link

Sure, for some number of users this doesn't matter. For the people who care about it, it is, by definition, very important. What's the point of trying to play down their concern?

That would be really interesting if Tumblr and other sites create a posterous importer and everyone is a good 302 redirect citizen. Then you could switch to any service at any point, seamlessly.

What's really interesting about this is that he doesn't actually have the disease. Due to genetic testing, he may have an increased probability of getting it.

>Many philanthropists have funded research into diseases they themselves have been diagnosed with. But Brin is likely the first who, based on a genetic test, began funding scientific research in the hope of escaping a disease in the first place.

Kudos for that link! When I was originally implementing it, I couldn't find a good cross-browser hash history implementation, but this one looks really promising -- and jQuery to boot!

Not sure if you read Rework or subscribe to 37signals' philosophy, but according to them, you never, never want to hire someone under duress. Hiring poorly is far, far worse than not hiring at all (according to their philosophy) so there should never be a case where you need to hire someone so quickly, you have to toss out resumes based on where they went to school.

Nice. I made something pretty similar here: http://www.wolfire.com/comic

CloudFront is actually cheaper than S3 for data transfer. You should almost always use it for static assets instead of raw S3.

It's 1 GB free per day. After that it is 0.12 cents per GB.

Disagree, I found FPS to be the most playable games on the service. You should definitely try it out. Also what makes you say that serious game companies aren't commenting on it? Their games are already there.

There is none. It's like a console in that regard.

This is actually easy to solve -- most VNC applications already implement the solution, which is to have a local, lag-free cursor that is shown to the user, and hide the laggy cursor on the other machine.

One thing I forgot to mention in the post is that there is apparently an OnLive API that some games are using that replaces the cursor in the game with a local cursor. Not all games can use it (for example, World of Goo's cursor is blocked by walls and such which is critical to gameplay), but Unreal Tournament, and OnLive itself, use it in the UI.

Edit: of course this wouldn't solve the case where you are actually doing something in Photoshop that might require real-time feedback like the airbrush tool!

There was a story the other day that Google is investigating exactly that for supporting legacy applications. If OnLive can successfully stream a AAA video game at playable latencies, then they have pretty much proven that any application is doable.

FYI, I tried to respond to your email but it bounced, hope you read this comment!

This looks really, really awesome -- App Engine users have been needing something like this for a very long time. Unfortunately, Google is about to roll out their own version for free:

http://code.google.com/apis/feed/push/

and a native App Engine solution called the Channel API: http://code.google.com/events/io/2010/sessions/building-real...

Is it just me or does Gmail only show you the past 24 hours of activity?

  "Read in bed until I feel sleep coming on"

I have been doing this since I can remember and it works great for me too, but I have heard one theory that it is not optimal since you may start to associate bed with reading instead of sleeping. Theoretically you should read in a chair or something and then move to your bed when you are getting drowsy.

Not sure if there is any merit to that, but it may help.

Ironically, I am trying to go to your site to see what you do and am getting the following error:

  Error

  Request-URI Too Large

  The requested URL /... is too large to process.

Sorry, I accidentally downvoted you when clicking over to this browser window.

He clearly defines the characteristics that make a good french fry and then explains how to match that consistently. He concludes that almost all of McDonald's practices (freezing the fries) are not simply economically important, but essential to the taste as he defines them.