New, Higher-Resolution Image of Boston Marathon Suspect
thelede.blogs.nytimes.com
thelede.blogs.nytimes.com
And perhaps most importantly...why? If it was a hoax it is surely one of the most boring hoaxes of all time, showing the suspect vaguely with no new interesting details except that he has no bag in the photo.
Edit: I just saw this Tweet from a digital manager at the New York Times. He's since admitted his mistake but this should be preserved for posterity as an example of how NOT to do digital forensics...it's as if he's never zoomed into a JPG before in his entire life https://mobile.twitter.com/jeremyzilar/status/32504129646716...
http://www.eliteraspberries.com/images/suspect-number-2-749.... (17MB)
Besides, server side he has access to powerful smart resizing programs and algorithms. Client size, not so much.
But I don't see why client-side can't do "powerful resizing". Not since <canvas> appeared, anyway.
You'd still have to move the 5-6 MB original, and then it would hog a lot of people's browsers to work on the image in the canvas (depending on client CPU/memory).
>But I don't see why client-side can't do "powerful resizing". Not since <canvas> appeared, anyway.
Who said it cannot do? I said the options aren't available. The guy did a simple resize. Should he also spend hours coding smart interpolation on javascript instead of just putting the image up?
For most connections, a 17MB download is eaten for breakfast, anyway.
http://code.google.com/p/fftresize/source/browse/fftresize.p...
Like so (edit: note that you'll have to edit the image first to make it grayscale, and even then this uses a lot of memory...):
$ python fftresize.py suspect-number-2.JPG 2.0
I just uploaded the image to S3 to share. The script isn't great (grayscale only) because it was written for a blog post to demonstrate the interpolation method, but I might as well work on it this weekend.It's not looking good for whoever this guy is and if he's innocent, it would be in his best interests now we have a high resolution photo to turn himself in before a member of the public or worse members of the public find this guy and potentially harm an innocent person out of irrational anger. Another incriminating fact is Jeff Bauman the guy who lost both legs in the blast woke up heavily drugged in the hospital and said he had looked into the eyes of a bomber (which is no doubt what helped the feds narrow down the search). Lets keep level-headed about this and assist the authorities the best we can and let them do the investigating. If we all start jumping to conclusions and taking the law into our own hands we could do more harm than good. They'll find the culprit, it's only a matter of time.
Or somebody would have stolen it. There was even looting in the area just after the bombings.
(Personally I very rarely take the bother to declare something being lost with the authorities).
Bottom left corner.
Edit: Higher Res
http://robertgawron.blogspot.com/2011/01/super-resolution-al... More details on it here: https://github.com/RobertGawron/supper-resolution/wiki
Just because someone's willing to be a indiscrimate murderer doesn't mean that they're geniuses or well put-together
How far are we from having sufficient facial recognition technology that we could clip a photo like this, drop it into Facebook image search (or whatever), and the person would come up? Is that feasible with today's technology?
One problem is the databases of tagged faces typically have passport style photos and not sides. It would be easier with 3d type data of faces, like when we start using depth cameras at the DMV too. Or, we will develop sufficient methodology to figure it out well enough from the existing photos... depth from a single image.
It sounds sort of disturbing to me. Google reverse image search for faces... that team has done it or could do it easily. But privacy.
You have lots of other information, so you don't need to check every human on the planet.
HN needn't fear, though. Reddit's on it.
Ref: http://graphics8.nytimes.com/images/blogs/thelede/posts/susp...