Demo Spring 2012: The Image Authenticity Problem

In the world of Photoshop and its brethren, can we ever tell if an image is real?

1 min read

Real, or photoshopped? It’s hard to look at any image these days without wondering if it’s been tweaked a bit.

Verifeyed, a company from Prague, presenting at Demo Spring 2012 last week, says they can tell they can tell an original image from one that has been cropped, cleaned up, or otherwise manipulated. Their approach is not typical—it doesn’t use a watermark, or look at individual pixels for odd vagaries. Rather, the company has analyzed 8000 cameras and scanners so far, with more in the pipeline, to determine each type of camera’s “footprint.” By comparing the image against the camera’s footprint, the company says it can quickly and easily spot alterations. The technology can also potentially spot the “fingerprint” of an individual camera, making it useful for enforcing laws against, for example, child pornography.

Verifeyed’s technology came out of government funded research conducted at the Academy of Science in Prague, says company vice president Bill Appleton,  Verifeyed expects to market its software to insurers, banks, dating sites, and other commercial customers, to help them identify fraud.  A boon for those customers, but, for the rest of us, said Jolie O’Dell from VentureBeat in critiquing the technology, “Now we’re going to find out that nothing cool ever happens and everyone is ugly.”


The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
A plate of spaghetti made from code
Shira Inbar

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less