{"id":4165,"date":"2011-06-15T06:32:10","date_gmt":"2011-06-15T10:32:10","guid":{"rendered":"http:\/\/www.baileybegood.com\/home\/?p=4165"},"modified":"2013-08-19T03:45:57","modified_gmt":"2013-08-19T07:45:57","slug":"mad-words-wednesday","status":"publish","type":"post","link":"https:\/\/www.baileybegood.com\/home\/2011\/06\/15\/mad-words-wednesday\/","title":{"rendered":"Mad Words Wednesday"},"content":{"rendered":"

Today’s post wasn’t supposed to go like this. It was supposed <\/em>to have a couple of really cute photos of me, but instead, those will have to wait. Don’t worry, you’ll hopefully get to see those next week. I thought it was much more important for my friends to read the following, ’cause if you own a website, it’s very possible your images have been stolen and put on another website.
\n
\n9:20am Update:<\/strong> My mommy checked the infringing links she posted below, and they’re coming up “Not Found.” It looks like BaileyBeGood has might have already been removed from this website (she’ll check later too). If you put your website name into the search box on the page ( Domain name removed ’cause it currently has non-family-friendly links on there<\/em>, (for example, search sugarthegoldenretriever<\/em>:
\n(Domain name removed ’cause it currently has non-family-friendly links on there<\/em>\/search.php?wd=sugarthegoldenretriever ) and you will see if any of your photos or images display on that website. As of 9:45am, there were numerous <\/em>pages of sugarthegoldenretriever.com’s photos, hot-linked on Domain name removed ’cause it currently has non-family-friendly links on there<\/em>.<\/p>\n

6pm Update<\/strong>: It appears that my mommy was not too clear about what she meant in this post. A couple of people misunderstood and thought she meant that the people on the list were stealing bandwidth from us. But that’s not what the list is. The list contains websites of just a few of my friends who have photos hot-linked (stolen) at the following website: Domain name removed ’cause it currently has non-family-friendly links on there<\/em>. Please, if you have any questions, I know my mommy will try and answer them. \ud83d\ude42<\/p>\n

6-27-11 Update<\/strong>: Bad site<\/a> is back up and running under a different domain.<\/p>\n

Continue with the Original post:<\/strong><\/p>\n

Remember this post: Stolen Image & Bandwidth, Oh My!<\/em><\/a>? Well, my mommy thought it would be a good idea to explore things further. It’s a good thing she did, ’cause she found another website that embedded my YouTube videos (which is OK), but they also took 3 screen shots of each video and posted those on their website, which is not allowed. She sent them a DMCA-compliant email and those pages have been removed.<\/p>\n

You’re probably wondering what this has to do with all of you. Well, since this starts to get too complicated for a soon-to-be puppy of 1 year old, I think I’ll let my mommy explain. I asked her to share her knowledge so you can protect your copyright too. <\/p>\n

Here’s what I’ll be doing today while she’s working hard to protect my copyright. \ud83d\ude42<\/p>\n

\"Mad
\nMy favorite lounging position, on my favorite couch by the window.<\/em><\/center><\/p>\n

OK mommy, it’s all yours… \ud83d\ude09<\/p>\n

Hi friends. I’m so sorry to intrude on Bailey’s post, but I discovered a website that was posting images from blogs including Bailey’s. In reviewing the images (the few that managed to sneak past the code we had added), I was surprised to learn that many of Bailey’s friend’s had images posted on the infringing website as well. These images were hot-linked and were stealing bandwidth (if you own your own website this is not good). <\/p>\n

I learned something else while I was there. I noticed that a few of Bailey’s images were being displayed, even though we had an .htaccess file that included code (mentioned in the Stolen Image & Bandwidth post) to prevent her images from being hot-linked on another website. On my own<\/em> websites, I had different code inside my .htaccess file. If you have your own website, you should become familiar with .htaccess files. Read further for a few helpful links.<\/p>\n

Getting back to the two codes… I thought I would try putting the two codes together in the .htaccess file, to see if this would stop my images from displaying on the infringing website. After I added the new code, the majority of Bailey’s images that were displaying on the infringing website (which was a lot!) now displayed “Image Cannot Be Displayed” on the infringing website. There were only a couple that still displayed. Also, there were images of Bailey’s that I could not prevent from displaying, because they were hosted on other websites such as Facebook, Cafepress, etc. <\/p>\n

Owning a website is hard work. Honest website owners can never stop defending their copyright. It’s unfortunate that we have to constantly be on guard because of thieves, but if you spend a little time each week or even each month, reviewing your stats (which is where I found this infringing website) and\/or just searching Google, you should be able to keep your website somewhat <\/em>free of theft. It’s impossible to be totally <\/em>free of all <\/em>website theft all <\/em>the time, but you could come close!<\/p>\n

I am not going to link the infringing website to this post — I do not want to give them anymore back links. But I will post it for you to copy and paste into your browser. <\/p>\n

Before I get to that, I want to show you the entire code I have added to Bailey’s .htaccess file in the image folder:<\/p>\n

<\/font>
\nRewriteEngine On
\nRewriteCond %{HTTP_REFERER} !^$
\nRewriteCond %{HTTP_REFERER} !^http(s)?:\/\/(www\\.)?yourdomain.com [NC]
\nRewriteRule \\.(jpeg|jpg|gif|png)$ - [F]<\/p>\n

SetEnvIfNoCase Referer \"^http:\/\/www.yourdomain.com\" local_ref=1
\nSetEnvIfNoCase Referer \"^http:\/\/yourdomain.com\" local_ref=1
\nSetEnvIfNoCase Referer \"^http:\/\/www.yourdomain.com\/\" local_ref=1
\nSetEnvIfNoCase Referer \"^http:\/\/yourdomain.com\/\" local_ref=1
\n<FilesMatch \".(gif|jpg|jpeg|png)\">
\nOrder Allow,Deny
\nAllow from env=local_ref
\n<\/FilesMatch>
\n<Files *>
\ndeny from colo.iinet.com
\ndeny from iterasi.net
\ndeny from Domain name removed 'cause it currently has non-family-friendly links on there<\/em>
\n<\/Files>
\n<Files .htaccess>
\norder allow,deny
\ndeny from all
\n<\/Files><\/font><\/code><\/p>\n

Remember:<\/strong> You can only do this if you own your own domain name. If you’re not familiar with .htaccess files, you should first contact your webhosting company to make sure you are allowed to use .htaccess. If you have any questions about creating the file, or where it should reside, you should contact your webhosting company. <\/p>\n

How to create an .htaccess file:<\/strong><\/p>\n

For those of you who would like to create an .htaccess file and add the following code, here’s all you have to do:<\/p>\n

1. Open Wordpad or Notepad.
\n2. Copy and paste the above code, replacing yourdomain<\/em> with your real domain name.
\n3. Where it says, “deny from colo.iinet.com, deny from iterasi.net, and deny from Domain name removed ’cause it currently has non-family-friendly links on there<\/em>” — these are just a few of the sites we have blocked access to our websites. You can add other sites here as well.<\/p>\n