Remove links to remote URL

Author: ritesh-pandey

content/archives/old-tech-blog/entries/banshee-now-with-creative-commons-support-devel/contents.lr

@@ -8,7 +8,7 @@ body:
 
 Great news from [Gabriel Burt](http://gburt.blogspot.com/), lead developer for the Open Source media player [Banshee](http://banshee-project.org/):
 
-[![](banshee-cc.png)](http://labs.creativecommons.org/files/2009/01/banshee-cc.png)  
+[![](banshee-cc.png)](banshee-cc.png)
 (click for larger version) 
 
 **Search based on the license of a song/album with direct support of displaying CC license logos!**

content/archives/old-tech-blog/entries/bridging-public-bugtrackers-and-local-tasklists/contents.lr

@@ -32,15 +32,15 @@ Anyway, enough talk, let's give it a spin. You'll need a recent version org-mode
 
 Next open up the relevant org-mode file. Move to the "Roundup" line, hit Tab to cycle its visibility, and move to the line that starts with "#+call:"
 
-[![](cc_blog_ccommons_screenshot1.png)](http://labs.creativecommons.org/files/2010/11/cc_blog_ccommons_screenshot1.png)
+[![](cc_blog_ccommons_screenshot1.png)](cc_blog_ccommons_screenshot1.png)
 
 Now press "Ctrl+c Ctrl+c". You'll see it populate with issues from [my issues list](http://code.creativecommons.org/issues/issue?status=-1,1,2,3,4,5,6,7&@sort=-activity&@search_text=&@dispname=Your%20Issues&@filter=status,assignedto&@group=priority&@columns=id,activity,title,creator,status&assignedto=40&@pagesize=50&@startwith=0):
 
-[![](cc_blog_ccommons_screenshot2.png)](http://labs.creativecommons.org/files/2010/11/cc_blog_ccommons_screenshot2.png)
+[![](cc_blog_ccommons_screenshot2.png)](cc_blog_ccommons_screenshot2.png)
 
 What's happening here? So we're executing an org-babel block at point. [Org-babel](http://orgmode.org/worg/org-contrib/babel/intro.php) is an org-mode extension that allows you to make blocks of code executable, and even chain from one language to another (it also has some stuff relevant to Donald Knuth's "literate programming" which is cool but I'm not using here). If we look at the code blocks:
 
-[![](cc_blog_ccommons_screenshot3.png)](http://labs.creativecommons.org/files/2010/11/cc_blog_ccommons_screenshot3.png)
+[![](cc_blog_ccommons_screenshot3.png)](cc_blog_ccommons_screenshot3.png)
 
 Anyway, there are three code blocks here.
 

content/archives/old-tech-blog/entries/cc-legaleratta-errata-annotations-without-republishing-licenses/contents.lr

@@ -6,7 +6,7 @@ author: lunpa
 ---
 body:
 
-[![Screenshot of the errata tool.](errata_highlighted1.png)](http://labs.creativecommons.org/files/2012/02/errata_highlighted1.png)
+[![Screenshot of the errata tool.](errata_highlighted1.png)](errata_highlighted1.png)
 
 The html for the legalcode pages cannot be changed once they are published. The reason for this is because we provide sha1 hashes of them so that they may be redistributed. It also is a reason of credibility; that the license you've applied to your work today will still be the same one tomorrow. However, sometimes there are errors. They need to be accessible, yet they usually are too small to merit releasing a new version of the license.
 

content/archives/old-tech-blog/entries/find-and-reuse-with-attribution-cc-licensed-images/contents.lr

@@ -17,7 +17,7 @@ Nino Barbieri [CC BY-SA 2.5](http://creativecommons.org/licenses/by-sa/2.5/)
 
 The inclusion of structured data with the HTML means you can click the license link above and the license deed will display the attribution information, as well as our generated attribution HTML.
 
-[![](Screenshot-Creative-Commons-—-Attribution-ShareAlike-2.5-Generic-Google-Chrome.png)](http://labs.creativecommons.org/files/2010/10/Screenshot-Creative-Commons-—-Attribution-ShareAlike-2.5-Generic-Google-Chrome.png)
+[![](Screenshot-Creative-Commons-—-Attribution-ShareAlike-2.5-Generic-Google-Chrome.png)](Screenshot-Creative-Commons-—-Attribution-ShareAlike-2.5-Generic-Google-Chrome.png)
 
 ---
 pub_date: 2010-10-04

content/archives/old-tech-blog/entries/libreoffice-and-cc-openoffice-plugin/contents.lr

@@ -12,7 +12,7 @@ Over the summer, our GSOC student Akila Wajirasena gave a [wonderful overhaul to
 
 The good news? It seems that it works just fine out of the box:
 
-[![CC LibreOffice plugin test](cc_libreoffice_plugin_test.png)](http://labs.creativecommons.org/files/2010/12/cc_libreoffice_plugin_test.png)
+[![CC LibreOffice plugin test](cc_libreoffice_plugin_test.png)](cc_libreoffice_plugin_test.png)
 
 We've only tested it on some limited systems though, so if you do have some problems, [please report them here](http://code.creativecommons.org/issues/issue738).
 

content/archives/old-tech-blog/entries/license-identifier-on-the-deeds/contents.lr

@@ -9,7 +9,7 @@ body:
 
 Yesterday we [launched a refresh of the site design](http://creativecommons.org/weblog/entry/25965) for [creativecommons.org](http://creativecommons.org/). Included in the changes pushed was one small one originally suggested by our international [Affiliate Network](http://creativecommons.org/affiliates): the inclusion of the license identifier on the deeds. 
 
-[![](CC-BY-with-dc-identifier.png)](http://labs.creativecommons.org/files/2011/01/CC-BY-with-dc-identifier.png)
+[![](CC-BY-with-dc-identifier.png)](CC-BY-with-dc-identifier.png)
 
 Anyone who's been in the CC community for any length of time has seen people refer to the licenses by their short-hand names: CC BY for [Attribution](http://creativecommons.org/licenses/by/3.0/), BY-SA for [Attribution-ShareAlike](http://creativecommons.org/licenses/by-sa/3.0/), etc. But that short hand, while useful, has been a bit of [inside baseball](http://en.wikipedia.org/wiki/Inside_baseball_\(metaphor\)): it's part of the URL, but never appeared on the deeds, which we want to be the human readable summary of the license. As of yesterday the short-hand name is now on the deed. We've also annotated it with RDFa, so the licenses self-describe their short name (software can dereference the license URI and look for information describing it there). Thanks again to Alek and the affiliate network for suggesting this change.
 

content/archives/old-tech-blog/entries/three-layers-of-a-cc-license/contents.lr

@@ -9,7 +9,7 @@ body:
 
 Included in [last week's redesign](http://creativecommons.org/weblog/entry/25965) is an updated Licenses page, describing the CC licenses and what makes them unique. The combination of machine-readable metadata, human readable deeds, and the legal code are unique (to my knowledge) in the public licensing world, and this approach enables interesting applications of the licenses and broadens their accessibility. That said, the approach is not always easy to describe.
 
-[![](3layers-300x164.png)](http://labs.creativecommons.org/files/2011/01/3layers.png)
+[![](3layers-300x164.png)](3layers.png)
 
 After seeing Alex's updated graphics for the page, I roped him into helping me create an interactive version, based on CSS3 Transitions and Transformations. You can find the visualization [here on CC Labs](http://labs.creativecommons.org/2011/demos/license-layers/). More information about why and how I built it is on [my personal blog](http://yergler.net/blog/2011/01/07/css3-license-layers/). Note that this demonstration requires Chrome, Safari, or Firefox 4. Opera 11 sort of works. IE, well, doesn't. 
 

content/archives/old-tech-blog/entries/welcome-hudson-to-creative-commons/contents.lr

@@ -12,7 +12,7 @@ We've been working over the past year on improving our tooling and processes for
 
 Earlier this week I spent a little time installing [Hudson](http://hudson-ci.org/) on our [development server](http://code.creativecommons.org). By looking at the [dashboard](http://code.creativecommons.org/hudson), you can easily see the build status of CC projects, including the aforementioned license components, and [DiscoverEd](http://wiki.creativecommons.org/DiscoverEd), our linked data search prototype. 
 
-[![](trend.png)](http://labs.creativecommons.org/files/2010/08/trend.png)
+[![](trend.png)](trend.png)
 
 Hudson is already proving itself worth the time to deploy and configure. After installation, I saw that a test for the API was failing. I pinged John, and was happy to see the build go green a few minutes later when he checked in a fix and Hudson rebuilt the package. Graphs like the testing trend for [discovered](http://code.creativecommons.org/hudson/job/discovered/) also help quantify the progress being made. Overall, it already feels like we have better visibility into the state of our infrastructure.