Categories: Google+

What Should Google Do About Copyright Violations on G+?

I applaud the convenient availability of a DMCA takedown form for Google sites, but there seems to be little enforcement beyond that.  Does Google do enough in your opinion?  Do the accounts of repeat infringers get taken down fast enough, or ever?  I heard that one of the presenters at the  G+ Photographer's Conference trained attendees on how to right mouse click save and re-upload other peoples' photos!
#copyright   #photography   #copyrightinfringement   #copyrightlaw  

Reshared post from +Daniel Schwabe

Google+, copyright violations and the fight for attention

warning: long rant – if you don't feel like reading all of it, please skip to the proposal at the end!

I’ve been increasingly bothered by the rampant abuse of photo sharing within Google+. By this I mean people who find beautiful images in the Internet, download them, re-upload them to their own photo streams, and share them, most often without any attribution. Google+ assumes that either you took the photo yourself, or you have the right to post such content. When one hovers over the photo, a hover text says “XYZ’s photos”. Some (I believe most) do it out of sheer ignorance, others, not so much – they even go to the length of removing watermarks, or adding their own! .

The recent inclusion of the “views” statistics has made the effects of this behavior even more evident. A typical example  I’ve come across is a poster who has over 8 million views and only slightly more than 2000 followers – without a single photo of his own. There are some communities in Google+, (e.g.  Amazing Places to See, Nature Photography ) that are choke full of this kind of photo sharing, and their moderators don’t seem to make any effort to discourage improper sharing.
 
It is no secret that we are now in an “attention economy” – everybody is, in some sense, trying to get everybody else’s attention. For many, this is directly translated into monetary rewards, for others, the rewards are less tangible – fame, recognition, etc… 

Google+ is no different. It has become very popular with photographers and photo lovers in general, being an important place to share and see beautiful images, for professionals and amateurs alike. Whereas there are several other photo sharing sites (e.g., Flickr, 500px, 1x,  …), the quality of interactions and variety of photography-related subjects being discussed sets it apart. So photo sharing is especially relevant.

There are many so-called “social marketeers” who understand very well the importance of visibility, and resort to this tactic to increase their own visibility. Sometimes they actually include either a reference or a link to the original site in the text of the post, but the shared photo still shows up as if it was their own and not the author's. Some have claimed that it is often difficult or impossible to find the owner, or requires too much work. And, truth be said, the copyright ownership of many photos found on those "free wallpaper" sharing sites (a very common source of photos for reposting and attracting many views) is not so clear – many claim these images a free, although I suspect they free for personal use on one's own machine, not for reposting.

I have also heard the claim they are actually doing the photographer a favor by exposing the photo to a much larger audience than the one they have, and that many photographers are even grateful to them for doing this. In one case, there was a photo where the photographer's page in 500px had 13k views, and the sharer's had 73k views (which never went to the photographer's site or account) – and one comment on the G+ post even inquired whether he (the poster) sold that and other photos!  To me it is evidence that many readers, if not most, do not realize the photo is not from the poster, in spite of the credit text at the top of the post itself.

So, in spite of what they claim, in my view they are benefiting, ultimately for commercial purposes, from other people’s work, without providing any return to the original author. Some may disagree with this perception, but in absence of more concrete data supporting this claim (that they are concretely benefitting the photographer), I take it as a rationalization to explain inadequate behavior. It seems to me to the equivalent of those requests one gets to allow the use of one's photos for free, in exchange for "recognition".

I can understand that it no so simple for Google+ to deal with this, for legal reasons. Currently, only the copyright owner can report violations. And it is nearly impossible to completely eradicate such behavior.
But Google+ could at least discourage it, in at least two ways It could put a visible reminder when one is uploading content, emphasizing that sharing other people's work without their consent is a copyright violation. In addition, it could include a link to some tutorial/clarification (there are many available, in layman terms), as a way to educate those who don’t have any knowledge about copyrights and proper posting etiquette.

A second initiative would be to use the tools they already have and use them to detect "suspicious" material. It would be easy to put up a warning, when an image is uploaded, if the same image was found elsewhere, along the lines of  "we have detected this material exists somewhere else in the Internet. Please make sure you have the right to post it, you may be violating its copyright".

Both measures would have a more "educational", rather than coercive, approach, and I believe could help improve the general sharing culture within Google+.
Your thoughts?
(I'm tagging a few people who I believe could contribute to the discussion –
+Thomas Hawk +Jeff Sullivan +Joe Azure +Jay Patel +Varina Patel +Mike Spinak +Colby Brown +Elia Locardi +Barry Blanchard +Lori Hibbett +Patrick Smith +RC Concepcion +Gideon Rosenblatt +Mark Traphagen +Robert Scoble +Yonatan Zunger +Brian Matiash +Victor Bezrukov 
+Karen Hutton +Alan Shapiro +John Paul Caponigro +Jim Goldstein +Ron Clifford +Sean Bagshaw +Toby Harriman +Martin Rak +Jim Patterson +Vincent Mo +Trey Ratcliff  +Google+ Photos +Google )

Embedded Link

Facebook Software Engineer Teaches You How to Steal Copyrighted Images
According to his bio, Jesse Chen is a software engineer at Facebook and recent graduate of UC Berkeley. Jesse has a personal blog which we recently stumbled across that includes a blog post from 2012 that detailed how to go about stealing copyrighted images and removing watermarks. The…

Google+: Reshared 5 times
Google+: View post on Google+

Jeff Sullivan

Jeff Sullivan leads landscape photography workshops in national parks and public lands throughout California and the American West.

View Comments

  • Just because we like it and want some one else see it, dosen't mean were wanting to sell it. If it has a water mark, then what could we do with it, other then look at it. If you don't want people to view your work, then don't show it.

  • The question begs answering why are you putting legitimate version of your intellectual property, copyright product on the Internet?

  • "Jesse wouldn’t be cool with someone stealing some of his code for use in their own website, even though it can be done just as easily" ....but, then FB was started by pirates, yes?

  • +Jasper Hanks +Leddyn Rhulund many businesses these days are internet based.  I sell much of my photography by putting it online - it is the best way for people to see it.  I only use relatively low resolution photos online though.  Would you go on a website and buy a photographic print you had never seen?

  • +Michael Russell watermark images, low resolution as you have done and if client is interested, full registration to view high resolution images. Tracking any attempt to copy or screen capture. Then charge the account. you would need to run your own server for this.

  • +Leddyn Rhulund I agree in that paying clients are the only ones that get my full resolution images in the form of a file or a print.   I don't need to track these people much as they have already paid when they get the file.  I do check up to make sure people are using a licensed image correctly though.  Still, I do get a lot of people taking the low resolution images for various reasons.  Many of those people wind up writing me a cheque after I find them.  :)

  • +Michael Russell your trying to make a living and I understand why you protect your works so ardently. At lot of time and skill goes into any art form.
    I would personally become familiar with Google own copyright rules and how they may effect you. You don't want to be publishing on a google site to find out you have wavered your intellectual property and copyright rights.

  • +Leddyn Rhulund I have read the Google TOS many times, and am comfortable with it.  I did stop posting to Facebook last year though, as I was not as comfortable with their TOS language or the general attitude of the company in these matters.  Your point is a good one though - everyone who shares their content on social media platforms of all kinds should be aware of the terms of service for those sites.

  • Yes, I would buy, and have bought photos i fell in love with off the internet. How else am I going to get them 11by 16 or bigger

Recent Posts

Photographic Composition: Conception and Fine Tuning

This was one of those "stop the car" moments. Snowy Telescope Peak had nice side…

10 months ago

Geminid Meteor Shower 2023

The Geminids are the most active meteor shower of the year, and in recent years…

12 months ago

When Is The Best Time To Visit Bodie State Historic Park?

I was asked this question earlier today, and the more I thought of it, the…

1 year ago

Death Valley Wildflowers, Rainfall and Super Blooms

So called "super bloom" years make it easy to find wildflowers in Death Valley, but…

2 years ago

Night and Landscape Photography Workshops 2022-2023

We've reached a major milestone on our workshop program: we celebrated completing ten years of…

2 years ago

Death Valley “Adventure Series” Trip March/April 2022

Spring 2022 is shaping up to be a very busy year in Death Valley, like…

3 years ago

This website uses cookies.