However, the founders of Picuous saw a problem, or at least a limitation, with almost all of these services. The company cites the story of James Duncan, the TED photographer who took the now-famous photo of Bill Gates releasing (supposedly) malaria-infected mosquitos loose in the conference, as an example of a photographer whose photo was infringed widely because there was no easy way to share images on the Web.

Picuous, however, aims to fix that and it seeks to do so by being the “Scribd” or the “Vimeo” of image hosting, making it easy to share and embed images without actually transferring the file. Along the way, it hopes to offer both better analytics and better copyright enforcement.

But how well does Picuous work? I decided to give the service a test and find out.

How Picuous Works

The big idea behind Picuous is that other media types, including audio and video, have an embed feature that make them easy to share on other websites while ensuring the original author gets credit and, sometimes, revenue. However, images are usually just saved and reuploaded or hotlinked to get them on other sites. Along the way, both attribution and revenue opportunities are lost.

To fix this, what Picuous does is offer a simple HTML5-based means of embedding the mage on the other site. Though Picuous doesn’t use Flash, it’s a very Flash-like experience and one that users of Scribd and YouTube should be very familiar with.

The big idea is that others, if they see an image they want, they will be more likely to use this embed code than they will copy the image or hotlink it as this is easier, faster and more reliable.

So how does Picuous stack up? My experience was, in a word, mixed.

My Experiment with Picuous

by jonathan on picuous

In order to try Picuous, I attempted to upload and share a photo of my dog, Calico, deciding that he wanted to drive the park. To do that, I created an account, uploaded the image and pasted the embed code as-is in the first part of this section.

The registration and account setup process went very smoothly. It took only a few moments to sign up, get my beta invite and then log in. Uploading the image was easy as well as I was able to simply drag and drop the image from my computer and have it upload automatically.

However, I quickly found out that Picuous is fairly limited as an image host. Though it’s very simple to use, other than setting the license for your images, editing their names and embedding them, there strangely isn’t much else you can do with them. There are no folders you can put them in, no tags to organize them and no additional sharing tools. In fact, the embedded image actually has more features in that it integrates with Twitter, Facebook and Posterous, things that the backend of Picuous doesn’t do.

Still, the embed code was easy to grab though I learned quickly, as you can see above, that there is no easy way to make it flush left or right, thus forcing the image to sit awkwardly on a new line. There is also no way to resize the image should the default size be wrong.

Once again though, you can at least edit the size of the image when re-embedding the embedded version, though there is still no easy way to align it.

All in all, Picuous was extremely easy to use and worked great, but it has a limited feature set, at least at this time. Still, what it does, it does well and most of the limitations can be overcome easily with a bit of work, such as the (quick and dirty) fix I made below.

Is Picuous Worthwhile?

To be clear, Picuous isn’t going to stop infringement. Though it prevents people from being able to save your image directly, I can still screenshot images that Picuous stores or get around the protection by simply looking at the HTML code. However, it does make it more difficult and, at the same time, it provides a path of lower resistance, one that those who are interested in being even remotely legitimate with their use will likely take.

While I think that using Picuous would not be right for PT or similar sites where most of the images are either stock photos or screenshots, it might be appropriate for those who run photo blogs or post a large number of professional or semi-professional images.

That being said, Picuous is far from a Flickr or a Smugmug replacement. You’ll still likely need to use another photo sharing service as your “home base” as there are too few features and no social elements to Picuous (other than an RSS feed for the stream). Still, it might be a good way for getting photos into your blog if you want to encourage sharing without having the file itself passed around.

In short, it won’t stop infringement, but it will encourage healthier uses of your work and that may be worthwhile for some.

Bottom Line

At the end of the day, Picuous is still very much a beta service. This means that the service is limited at this time but that, possibly, many of the issues will be addressed before the final release.

Still, the big idea behind Picuous is a neat one and has a lot of potential. It’s similar to what Picapp has been doing for professional stock images but making the process available for smaller photographers and artists.

There’s definitely a lot of potential here and it’s a site photographers and artists should definitely both try out and keep an eye on. It may not be everything one needs right now, but it certainly has a lot of potential and can provide a useful, if somewhat limited, service already.

photo credit: Keyser_ Soze

It happens about once per month. I get an email a software programmer who believes that he or she has developed the perfect DRM solution. They send me the usual promotional copy about how great their product is and why I should promote it on this site.

Even though my faith in DRM as a solution to content theft issues has been completely shattered, it is hard for me to not get my hopes up a little bit. However, they are almost immediately dashed every time as I test the solution.

Usually within a few minutes I’m breaking the DRM scheme and emailing back the person their “protected” sample image. Though I offer a detailed analysis of how I was able to perform the feat and offer suggestions on how to improve the product, I never hear back from them.

This is in stark contrast to detection and licensing companies, such as Copyscape that have listened to my issues and made changes to fix them. In fact, many of these companies go on to become paid clients to take even further advantage of my beta testing and trouble shooting.

The DRM guys, however, disappear, They almost always resist even a simple email exchange and never defend their product against the flaws that I find.

This is not to say that all DRM schemes are unscrupulous, just that I have serious questions about the ones who have approached me. If there is a DRM solution out there that works, I want to find it and I want to give a chance to the legitimate DRM problem solvers to get their products reviewed.

However, to ensure that the playing field is fair, I’ve created a simple DRM challenge. A format by which any image DRM solution provider can submit their product, have it reviewed on this site and, potentially, win the prize of free advertising.

The rules are below.

The Big Idea

The big idea of this challenge is fairly simple. If there is a magic DRM solution out there, I want to feature it on this site. I haven’t found it yet and, currently, do not believe it exists, but I would love nothing more than to be proved wrong.

So, I wanted to give every DRM producer a chance to have their technology tested and reviewed on this site under a standard set of rules. If anyone can meet my criteria and beat all of my efforts to break your DRM, then I am offering a month of free advertising on this site (delivered in the form of a 200×200 button near the top of the sidebar), bearing in mind this site does not currently show ads, as well as a text link at the footer in the RSS feed for a week.

To get the prize though, you must meet the following rules.

How It Works

The premise of the challenge is easy. If you are a DRM solution creator and would like to take me up on the challenge, what you first need to do is email me with the following things:

1. General information about your DRM solution, including name, how it works and any promotional information you wish to include
2. A logo or other graphic to include in my review (if applicable)
3. A link to an image that is protected using your technology

Please bear in mind that, right now, this is ONLY for image DRM solutions for simplicity reasons.

Once I have that email, when I am able to, I will attempt to break your DRM and email you either your image or the critical parts of it. To do this, I will bring a series of tools to bear including, but not limited to, the following:

1. Source code snooping
2. Browser tricks
3. Screen capture tools
4. Decompiler programs
5. File extractors

If I am unable to break the DRM in a reasonable amount of time, approximately one hour of work (Note: the work may actually be over a period of many hours due to my schedule) I will then turn the system over to a friend that is even more savvy about breaking DRM and give them the same chance.

(Note: If you are interested in helping to break image DRM schemes, send me an email to jonathan@plagiarismtoday.com and let me know. I have some people in mind but if there are a lot of applicants I may need more people to keep the line moving.)

If the DRM system survives both attempts to break it and meets my other criteria, then it wins the challenge.

It is that simple.

Usability Criteria

However, since it is easy to lock down an image so that no one can get to it, including a legitimate viewer, I’m also laying out a series of usability criteria any such system must meet.

1. No software install to view
2. Must work on Mac, Windows and Linux
3. Must work in at least IE, Firefox, Safari, Chrome and Opera
4. Ideally, legitimate users should not even be aware of the DRM in place but the DRM should definitely not hinder normal viewing in any significant way
5. It can not incorporate watermark as the goal of DRM is to prevent copying, not reduce effectiveness of any copies made

Please bear in mind that these are not absolutely all of the guidelines in this area and that any DRM that greatly hinders regular viewing of a file could be disqualified from the ultimate prize.

It will be up to me and readers that I poll whether or not a DRM system hinders viewing too greatly.

(Note: I am on the fence about slideshow systems such as Slideroll. Though these systems are relatively secure, they do hinder viewing of the images and have other vulnerabilities. I am seeking artist feedback on whether to allow such systems into the challenge.)

Other Rules

Before we go any further, here are a few miscellaneous rules to the challenge.

1. You must be the creator or a representative of an image DRM system to apply. Users can not nominate a system for the challenge (but can suggest them to me informally for outreach).
2. Once I have completed my testing of your system, I will email you with the results. You will have a 48 hour period to respond. If you don’t reply in that time, I will publish my article without your commentary.
3. All systems submitted, whether they complete the challenge or not will be reviewed on this site, possibly including a screencast. By submitting your service, you agree to allow me to do so.

In short, if you submit a DRM system for this challenge and it is trivially broken or creates a horrible user experience, the world will know about it.

Objections and Questions

Finally, here are the answers to some of the more common questions/concerns many will have regarding this challenge.

This is impossible! No system can do this!

I’m on record saying that I agree. No image DRM system I have seen has been able to balance usability and provide good protection. Please bear in mind that I am not some kind of elite hacker or tech guru, I’m just a computer-savvy Webmaster with a lot of experience testing image DRM.

If your system can not survive my test then there is no way it will survive on the Web. The image only has to be jailbroken once for it to be all over the Web.

The inclusion of screenshots as a means to break DRM is unfair, those are low-resolution images.

This argument is suspect to me for many reasons.

First, there is no reason to post high-resolution images on the Web unless they are intended for printing. Posting extremely high-resolution images is, usually, a waste of bandwidth.

Second, as was shown during the first round of concern with Photobucket, low resolution images can still be used very successfully in prints.

Third, screen shot tools are almost universal now, built into every major operating system. It is the first way many amateur image plagiarists obtain an image.

Finally, the most common use for an illegally-copied image is on another Web site, for that, a screenshot is more than adequate.

Do you have to get the whole image?

No. I look at it from the artist’s perspective. If I can get the bulk of the image, enough to virtually replace the original work, then I will consider that a failure.

Though such omissions might help prove which image is the original, it doesn’t help the artist keep their work from spreading. However, there will be a note in my review that I was not able to get the full image.

What if my system doesn’t meet your usability criteria?

You can still apply to be reviewed, just understand that even if I can not break your DRM, you will not win the challenge. I realize that there may be works and artists that find such a trade off rewarding so I will not bar such products from this site, though I will be honest about any such issues.

What if my system doesn’t prevent copying but tracks it?

Those systems are not designed for this challenge. If you have such a system you wish me to look at, let me know. However, it is not eligible right now for this challenge. More on this later.

What if my system is commercial?

That is not an issue, I will mention the price in my review but so long as there is no charge for me to test it, I will not object. Such systems are still eligible to win.

When is the deadline?

There is none. This is an open-ended challenge until either someone wins or I decide to close it down. If I receive too many entries at once I may put a temporary halt on new submissions.

I will announce changes/closures on this page.

A Word About Rule Changes

I am writing these rules a bit by the seat of my pants. Remember this, the spirit of the competition is to create a DRM system for images that is both user-friendly to legitimate viewers but also difficult to impossible for a prepared computer-savvy user to break.

Please keep your submissions in the spirit of the competition.

I will likely be posting minor rule changes to this page over the coming days. If I have to change a rule between the time you submit an entry and when I test it, I will email you to let you know of the changes and make sure you agree.

I don’t expect anything drastic to change.

Ask Questions

I encourage people to post questions about the contest in the comments form below so that I can give public answers. If you have a question that is specific to your system email it to jonathan at plagiarismtoday dot com.

Enter

If you want to enter the challenge and agree to all of the mess above, send me an email with the required elements to jonathan at plagiarismtoday dot com and I will let you know when to expect met to start work.

Thank you very much for your time and patience with this. I sincerely hope that there is a holy grail of image DRM out there and would love nothing more than to be proved wrong.

Bear in mind that, if such a system has been created, this challenge would not even be the beginning of what the creator could do. With so many artists clamoring for a means to control their images, such a system would almost certainly lead to much greater things.

On that note, I look forward to being challenged and to seeing what creative solutions the programmers of the world have come up with.

It has been yet another fully week for copyright news including updates from three continents and a special, perhaps unwanted, “appearance” by Gene Simmons of KISS fame.

All in all, it was a somewhat slower week and it lacked a good core theme, but there were a lot of important updates and easily one of the wildest “strange” stories we have ever reported on.

So, as always I sat down with Chris Matthieu from Numly to discuss those stories and more with our usual mix of news, views and abuse.

This week’s stories include.

• Barack Obama Finds Himself in a Controversy
• Adobe Talks DRM in Flash Files
• Yahoo! “Censors” The Pirate Bay
• RIAA Racketeering Lawsuit Suffers Setback
• The RIAA Links Terrorism and Murder to Piracy
• And Many more…

You can download the MP3 file here (direct download). Those interested in subscribing to the show can do so via this feed.

Show Notes

[audio:http://boxstr.com/files/1153723_apjr5/copyrigh20eps47.mp3]