X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/1dba9534f0537cdd58650b2a2d4672e5df41d966..17ddfe379836481b829ea2070f16b2a928806eb8:/blog/archive/2016/03/03.rss

diff --git a/blog/archive/2016/03/03.rss b/blog/archive/2016/03/03.rss
index e0de987512..ce18e89cdd 100644
--- a/blog/archive/2016/03/03.rss
+++ b/blog/archive/2016/03/03.rss
@@ -68,7 +68,7 @@ As always, patches are very welcome.</p>
 		<guid isPermaLink="true">http://www.hungry.com/~pere/blog/UsingQR____Electronic__paper_invoices_using_JSON_and_QR_codes.html</guid>
                 <pubDate>Sat, 19 Mar 2016 09:40:00 +0100</pubDate>
 		<description>&lt;p&gt;Back in 2013 I proposed
-&lt;a href=&quot;https://people.skolelinux.org/pere/blog/_Electronic__paper_invoices___using_vCard_in_a_QR_code.html&quot;&gt;a
+&lt;a href=&quot;http://www.hungry.com/~pere/blog/_Electronic__paper_invoices___using_vCard_in_a_QR_code.html&quot;&gt;a
 way to make paper and PDF invoices easier to process electronically by
 adding a QR code with the key information about the invoice&lt;/a&gt;.  I
 suggested using vCard field definition, to get some standard format
@@ -87,7 +87,7 @@ specification (based on a real world example, some numbers replaced to
 get a more bogus entry).  I&#39;ve reformatted the JSON to make it easier
 to read.  Normally this is all on one long line:&lt;/p&gt;
 
-&lt;p&gt;&lt;img src=&quot;https://people.skolelinux.org/pere/blog/images/2016-03-19-qr-invoice.png&quot; align=&quot;right&quot;&gt;&lt;pre&gt;
+&lt;p&gt;&lt;img src=&quot;http://www.hungry.com/~pere/blog/images/2016-03-19-qr-invoice.png&quot; align=&quot;right&quot;&gt;&lt;pre&gt;
 {
  &quot;vh&quot;:500.00,
  &quot;vm&quot;:0,
@@ -172,7 +172,7 @@ sets.&lt;/p&gt;
 		<guid isPermaLink="true">http://www.hungry.com/~pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
                 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
 		<description>&lt;p&gt;Back in September, I blogged about
-&lt;a href=&quot;https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
+&lt;a href=&quot;http://www.hungry.com/~pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
 how it showed the decay and death of this battery (now replaced).  I
 created a simple deb package to handle the collection and graphing,
@@ -195,7 +195,7 @@ status of the battery.  The source package build and work just fine in
 Debian testing and stable (and probably oldstable too, but I have not
 tested).  The default graph you get for that system look like this:&lt;/p&gt;
 
-&lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;https://people.skolelinux.org/pere/blog/images/2016-03-15-battery-stats-graph-example.png&quot; width=&quot;70%&quot; align=&quot;center&quot;&gt;&lt;/p&gt;
+&lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://www.hungry.com/~pere/blog/images/2016-03-15-battery-stats-graph-example.png&quot; width=&quot;70%&quot; align=&quot;center&quot;&gt;&lt;/p&gt;
 
 &lt;p&gt;My plans for the future is to merge my old scripts into the
 battery-stats package, as my old scripts collected a lot more details