How Your Photos on Google May Be Used
How Your Photos on Google May Be Used
I'm not going to offer any opinion on whether this is good or bad, just let you know so you can decide whether or not to share things to "Public", and whether or not to participate in these scripts.
Your photos may be offered by the Google API to other sites. What would be interesting to research is whether those sites may be commercial (Flickr bans commercial use of its community's images, but a lot of the use of Google's community photos on Panoramio does seem to be commercial... might be worth looking in the G+ Terms and Conditions).
Originally shared by Brian White
Photo Themes from Friday, October 28th.
There is important information here. Please re-share!
Public images posted on Google+ can be displayed in any context. Any webmaster can use the "img src" tag to embed the images in their own pages and have that content served by Google. I recommend that people "send feedback" suggesting that Google have a way to limit the viewing of photos to the context of Google+, either always or by user choice.
My "collection" pages below are doing this exact thing. All of the images on those pages are being served by Google who has a license to do so. I'm somewhat surprised they allow this but they do. I'm not trying to rip anyone off. All these photos are public and my generating script supports a few tags to allow contributor control. Adding "#g+only" to the post will cause my script to ignore the post. Also, some curators have requested that submitted images not be collected by default. In that case, you can add "#share" to request my script include it in the collection.
Note that me including or not-including your public images in my collection is not the real issue. I give full attribution to both the original post and the contributor. I could easily stop creating the collections but that would only hide the issue while others can continue to abuse your rights. I believe that you as the artist is better off being informed about the issue so you can make the appropriate choices. Limited distribution (i.e. not "public") is currently your best defense.
Lastly, I'm still debugging my script. If you posted something that wasn't found, please send me a link to the original post.
#FallFriday by Karin Nelson :
http://www.backgroundexposure.com/blog/gplus-themes/fall-friday/2011-10-28/
233 photos found.
#FloralFriday by Tamara Pruessner:
http://www.backgroundexposure.com/blog/gplus-themes/floral-friday/2011-10-28/
268 photos found.
#FoodFriday by Karin Nelson & Charles Lupica:
http://www.backgroundexposure.com/blog/gplus-themes/food-friday/2011-10-28/
54 photos found.
#FourWheeledFriday by Matthew Costabile:
http://www.backgroundexposure.com/blog/gplus-themes/four-wheeled-friday/2011-10-28/
61 photos found.
#FilmFriday by Richard Call:
http://www.backgroundexposure.com/blog/gplus-themes/film-friday/2011-10-28/
29 photos found.
#FungusFriday by Chris Sullivan:
http://www.backgroundexposure.com/blog/gplus-themes/fungus-friday/2011-10-28/
71 photos found.
#FrighteningFriday by Alexis Coram:
http://www.backgroundexposure.com/blog/gplus-themes/frightening-friday/2011-10-28/
48 photos found.
#FireFriday by Grayson Hartman:
http://www.backgroundexposure.com/blog/gplus-themes/fire-friday/2011-10-28/
40 photos found.
#FidoFriday by Shane Raynard & Wes Lum:
http://www.backgroundexposure.com/blog/gplus-themes/fido-friday/2011-10-28/
102 photos found.
#FrogFriday by Christina Rollo & Candace Hansen:
http://www.backgroundexposure.com/blog/gplus-themes/frog-friday/2011-10-28/
34 photos found.
I'm not going to offer any opinion on whether this is good or bad, just let you know so you can decide whether or not to share things to "Public", and whether or not to participate in these scripts.
Your photos may be offered by the Google API to other sites. What would be interesting to research is whether those sites may be commercial (Flickr bans commercial use of its community's images, but a lot of the use of Google's community photos on Panoramio does seem to be commercial... might be worth looking in the G+ Terms and Conditions).
Originally shared by Brian White
Photo Themes from Friday, October 28th.
There is important information here. Please re-share!
Public images posted on Google+ can be displayed in any context. Any webmaster can use the "img src" tag to embed the images in their own pages and have that content served by Google. I recommend that people "send feedback" suggesting that Google have a way to limit the viewing of photos to the context of Google+, either always or by user choice.
My "collection" pages below are doing this exact thing. All of the images on those pages are being served by Google who has a license to do so. I'm somewhat surprised they allow this but they do. I'm not trying to rip anyone off. All these photos are public and my generating script supports a few tags to allow contributor control. Adding "#g+only" to the post will cause my script to ignore the post. Also, some curators have requested that submitted images not be collected by default. In that case, you can add "#share" to request my script include it in the collection.
Note that me including or not-including your public images in my collection is not the real issue. I give full attribution to both the original post and the contributor. I could easily stop creating the collections but that would only hide the issue while others can continue to abuse your rights. I believe that you as the artist is better off being informed about the issue so you can make the appropriate choices. Limited distribution (i.e. not "public") is currently your best defense.
Lastly, I'm still debugging my script. If you posted something that wasn't found, please send me a link to the original post.
#FallFriday by Karin Nelson :
http://www.backgroundexposure.com/blog/gplus-themes/fall-friday/2011-10-28/
233 photos found.
#FloralFriday by Tamara Pruessner:
http://www.backgroundexposure.com/blog/gplus-themes/floral-friday/2011-10-28/
268 photos found.
#FoodFriday by Karin Nelson & Charles Lupica:
http://www.backgroundexposure.com/blog/gplus-themes/food-friday/2011-10-28/
54 photos found.
#FourWheeledFriday by Matthew Costabile:
http://www.backgroundexposure.com/blog/gplus-themes/four-wheeled-friday/2011-10-28/
61 photos found.
#FilmFriday by Richard Call:
http://www.backgroundexposure.com/blog/gplus-themes/film-friday/2011-10-28/
29 photos found.
#FungusFriday by Chris Sullivan:
http://www.backgroundexposure.com/blog/gplus-themes/fungus-friday/2011-10-28/
71 photos found.
#FrighteningFriday by Alexis Coram:
http://www.backgroundexposure.com/blog/gplus-themes/frightening-friday/2011-10-28/
48 photos found.
#FireFriday by Grayson Hartman:
http://www.backgroundexposure.com/blog/gplus-themes/fire-friday/2011-10-28/
40 photos found.
#FidoFriday by Shane Raynard & Wes Lum:
http://www.backgroundexposure.com/blog/gplus-themes/fido-friday/2011-10-28/
102 photos found.
#FrogFriday by Christina Rollo & Candace Hansen:
http://www.backgroundexposure.com/blog/gplus-themes/frog-friday/2011-10-28/
34 photos found.
flickr bans if its a link to the site, also there was a huge story with an app using photos uploaded from hipstamatic app. All that flickr had to say the man is using the API therefor nothing to do about it. The guy on app store still selling that app with peoples photos in it to demonstrate the film effects of Hipstamatic (to which he is not affiliated at all). All he did under the pressure was changing the app's name. I may precise 90% of the photos he using with the API are all rights reserved.
ReplyDeleteSharing to Public has always meant the image is shared with the entire world wide web. I don't think this is anything new. With the release of the API, it opens alot of doors for work to be shared and spread around. More eyes on my work is always a plus in my book. Personally am I worried about my work being "stolen", not one bit.
ReplyDeleteEven if a photo is shared to public, that does not mean that anyone can do whatever they want with the image. Copyright protection still holds, the question is only one of enforcement of the law.
ReplyDeleteIf anyone is at all concerned that a posted image might be pirated and used without permission, your first defense is to watermark the image. It is a U.S. federal crime to remove a copyright mark from a photo.
ReplyDeleteSecond, consider what professional photographer David Middleton has said, if you post it on the internet, just assume that someone is going to steal it.
Kevin Davis - I would add one more to that. If you do ever have to deal with copyright infringement and you have not registered all your work with the US Copyright Office (assuming you live in the US), then all the rest don't really matter all that much. 95% of those that I hear worrying about image theft in the US (both Pros and Amateurs) do not register anything then don't have any legs to stand on if they had to go to court.
ReplyDeleteI'm sticking with flickr.
ReplyDelete