Sorry

This feed does not validate.

In addition, interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://davorg.theplanetarium.org/atom.xml

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <feed xmlns="http://www.w3.org/2005/Atom">
  3.  <title>planet davorg</title>
  4.  <link rel="alternate" href="http://davorg.theplanetarium.org/" type="text/html"/>
  5.  <subtitle>Aggregating Dave's stuff</subtitle>
  6.  <author>
  7.    <name>Dave Cross</name>
  8.    <email>[email protected]</email>
  9.  </author>
  10.  <updated>2017-12-13T22:03:07Z</updated>
  11.  <link rel="self" href="http://davorg.theplanetarium.org/" type="application/atom+xml"/>
  12.  <id>http://davorg.theplanetarium.org/</id>
  13.  <entry>
  14.    
  15.    <link rel="alternate" href="https://twitter.com/davorg/status/941025791776878593" type="text/html"/>
  16.    <content type="xhtml">
  17.      <div xmlns="http://www.w3.org/1999/xhtml">Total omni-shambles https://t.co/RwUMBrxeih</div>
  18.    </content>
  19.    <updated>2017-12-13T19:23:26Z</updated>
  20.  <title>twitter: Total omni-shambles https://t.co/RwUMBrxeih</title></entry>
  21.  <entry>
  22.    
  23.    <link rel="alternate" href="https://twitter.com/davorg/status/941016905187545088" type="text/html"/>
  24.    <content type="xhtml">
  25.      <div xmlns="http://www.w3.org/1999/xhtml">12 hours after charging it fully and my @TheTicwatch  is on 15%. I should Just send it back and go back to my @pebble.</div>
  26.    </content>
  27.    <updated>2017-12-13T18:48:08Z</updated>
  28.  <title>twitter: 12 hours after charging it fully and my @TheTicwatch  is on 15%. I should Just send it back and go back to my @pebble.</title></entry>
  29.  <entry>
  30.    
  31.    <summary type="xhtml">
  32.      <div xmlns="http://www.w3.org/1999/xhtml">Your Only Doll (Dora) - Laura Marling</div>
  33.    </summary>
  34.    <link rel="alternate" href="https://www.last.fm/music/Laura+Marling/_/Your+Only+Doll+(Dora)" type="text/html"/>
  35.    <updated>2017-12-13T18:18:01Z</updated>
  36.    <author>
  37.      <name>Laura Marling</name>
  38.    </author>
  39.    <id>https://musicbrainz.org/recording/</id>
  40.  <title>last.fm: Your Only Doll (Dora) - Laura Marling</title></entry>
  41.  <entry>
  42.    
  43.    <summary type="xhtml">
  44.      <div xmlns="http://www.w3.org/1999/xhtml">My Friends - Laura Marling</div>
  45.    </summary>
  46.    <link rel="alternate" href="https://www.last.fm/music/Laura+Marling/_/My+Friends" type="text/html"/>
  47.    <updated>2017-12-13T18:12:14Z</updated>
  48.    <author>
  49.      <name>Laura Marling</name>
  50.    </author>
  51.    <id>https://musicbrainz.org/recording/e4986a1b-ab16-4e9e-b4ed-c0a27c0f5f62</id>
  52.  <title>last.fm: My Friends - Laura Marling</title></entry>
  53.  <entry>
  54.    
  55.    <summary type="xhtml">
  56.      <div xmlns="http://www.w3.org/1999/xhtml">Sowing The Seeds Of Love - Tears for Fears</div>
  57.    </summary>
  58.    <link rel="alternate" href="https://www.last.fm/music/Tears+for+Fears/_/Sowing+The+Seeds+Of+Love" type="text/html"/>
  59.    <updated>2017-12-13T18:05:23Z</updated>
  60.    <author>
  61.      <name>Tears for Fears</name>
  62.    </author>
  63.    <id>https://musicbrainz.org/recording/88c36548-8dcd-40be-a7b0-2d2685971ed1</id>
  64.  <title>last.fm: Sowing The Seeds Of Love - Tears for Fears</title></entry>
  65.  <entry>
  66.    
  67.    <summary type="xhtml">
  68.      <div xmlns="http://www.w3.org/1999/xhtml">Do It with a Rockstar - Amanda Palmer</div>
  69.    </summary>
  70.    <link rel="alternate" href="https://www.last.fm/music/Amanda+Palmer/_/Do+It+with+a+Rockstar" type="text/html"/>
  71.    <updated>2017-12-13T18:00:08Z</updated>
  72.    <author>
  73.      <name>Amanda Palmer</name>
  74.    </author>
  75.    <id>https://musicbrainz.org/recording/</id>
  76.  <title>last.fm: Do It with a Rockstar - Amanda Palmer</title></entry>
  77.  <entry>
  78.    
  79.    <summary type="xhtml">
  80.      <div xmlns="http://www.w3.org/1999/xhtml">THE SILVER BIRCH - The Magnetic North</div>
  81.    </summary>
  82.    <link rel="alternate" href="https://www.last.fm/music/The+Magnetic+North/_/THE+SILVER+BIRCH" type="text/html"/>
  83.    <updated>2017-12-13T17:56:39Z</updated>
  84.    <author>
  85.      <name>The Magnetic North</name>
  86.    </author>
  87.    <id>https://musicbrainz.org/recording/</id>
  88.  <title>last.fm: THE SILVER BIRCH - The Magnetic North</title></entry>
  89.  <entry>
  90.    
  91.    <link rel="alternate" href="https://twitter.com/davorg/status/940955321220124672" type="text/html"/>
  92.    <content type="xhtml">
  93.      <div xmlns="http://www.w3.org/1999/xhtml">Has @MooreSenate conceded yet? BBC story still says no. https://t.co/zB62LX6q0u</div>
  94.    </content>
  95.    <updated>2017-12-13T14:43:25Z</updated>
  96.  <title>twitter: Has @MooreSenate conceded yet? BBC story still says no. https://t.co/zB62LX6q0u</title></entry>
  97.  <entry>
  98.    
  99.    <link rel="alternate" href="https://twitter.com/davorg/status/940940181577846784" type="text/html"/>
  100.    <content type="xhtml">
  101.      <div xmlns="http://www.w3.org/1999/xhtml">Email from @AXS_UK about @thecure_ at @BSTHydePark - "a stunning 120 minute headline show". I assume that's ignoring the nine encores.</div>
  102.    </content>
  103.    <updated>2017-12-13T13:43:15Z</updated>
  104.  <title>twitter: Email from @AXS_UK about @thecure_ at @BSTHydePark - "a stunning 120 minute headline show". I assume that's ignoring the nine encores.</title></entry>
  105.  <entry>
  106.    
  107.    <link rel="alternate" href="https://twitter.com/davorg/status/940933264612700160" type="text/html"/>
  108.    <content type="xhtml">
  109.      <div xmlns="http://www.w3.org/1999/xhtml">I know that sometimes a broadband connection can feel like this :-) https://t.co/YGe6yFCBTc</div>
  110.    </content>
  111.    <updated>2017-12-13T13:15:46Z</updated>
  112.  <title>twitter: I know that sometimes a broadband connection can feel like this :-) https://t.co/YGe6yFCBTc</title></entry>
  113.  <entry xmlns:flickr="urn:flickr:user" xmlns:dc="http://purl.org/dc/elements/1.1/">
  114.    
  115.    <link rel="alternate" type="text/html" href="http://www.flickr.com/photos/davorg/38121805775/"/>
  116.    <id>tag:flickr.com,2005:/photo/38121805775</id>
  117.    <published>2017-12-12T15:39:46Z</published>
  118.    <updated>2017-12-12T15:39:46Z</updated>
  119.    <flickr:date_taken>2017-12-12T15:39:46-08:00</flickr:date_taken>
  120.    <dc:date.Taken>2017-12-12T15:39:46-08:00</dc:date.Taken>
  121.    <content type="html"> &lt;p&gt;&lt;a href="http://www.flickr.com/people/davorg/"&gt;Dave Cross&lt;/a&gt; posted a photo:&lt;/p&gt;
  122. &lt;p&gt;&lt;a href="http://www.flickr.com/photos/davorg/38121805775/" title="Union Chapel Chandelier"&gt;&lt;img src="http://farm5.staticflickr.com/4541/38121805775_ba435d0f92_m.jpg" width="240" height="240" alt="Union Chapel Chandelier" /&gt;&lt;/a&gt;&lt;/p&gt;
  123.  
  124. &lt;p&gt;via Instagram &lt;a href="http://ift.tt/2nOK3lo" rel="nofollow"&gt;ift.tt/2nOK3lo&lt;/a&gt;&lt;/p&gt;</content>
  125.    <author>
  126.      <name>Dave Cross</name>
  127.      <uri>http://www.flickr.com/people/davorg/</uri>
  128.      <flickr:nsid>[email protected]</flickr:nsid>
  129.      <flickr:buddyicon>http://farm4.staticflickr.com/3678/buddyicons/[email protected]?1372610206#[email protected]</flickr:buddyicon>
  130.    </author>
  131.    <link rel="license" type="text/html" href="https://creativecommons.org/licenses/by-nc-sa/2.0/deed.en"/>
  132.    <link rel="enclosure" type="image/jpeg" href="http://farm5.staticflickr.com/4541/38121805775_ba435d0f92_b.jpg"/>
  133.    <category term="ifttt" scheme="http://www.flickr.com/photos/tags/"/>
  134.    <category term="instagram" scheme="http://www.flickr.com/photos/tags/"/>
  135.    <displaycategories>
  136.            </displaycategories>
  137.    <title>flickr: Union Chapel Chandelier</title></entry>
  138.  <entry>
  139.    <title>perl hacks: Regenerating Perl School</title>
  140.    <link rel="alternate" href="http://feedproxy.google.com/~r/PerlHacks/~3/9Y0UdPXskxk/" type="text/html"/>
  141.    <content type="xhtml">
  142.      <div xmlns="http://www.w3.org/1999/xhtml"><p>About five years ago I ran a few training courses under the Perl School brand. The idea was simple – if you price training courses cheaply and run them at the weekend then you eliminate the most common reasons why people don’t keep their Perl knowledge up to date.</p>
  143. <p>Of course, it’s not quite that simple. And I think I ran six courses before running out of attendees.</p>
  144. <p>But there are still people who would benefit from getting some more up to date information about how Perl works. So I’ve decided to resurrect the Perl School brand in a new attempt to spread the Modern Perl knowledge beyond the echo chamber. I announced my plans during my lightning talk at last month’s <a href="//perlhacks.com/2017/12/london-perl-workshop-report/">London Perl Workshop</a>.</p>
  145. <p>This time I’m going to do it by publishing cheap books. You might remember that time <a href="//perlhacks.com/2014/11/lpw-perl-webbook/">I promised to write a guide to modern web development with Perl</a> and how badly that ended up. But in the process, I learned a lot about publishing ebooks to Amazon. I even <a href="https://www.slideshare.net/davorg/conference-driven-publishing-56093858">gave a talk</a> where I suggested that Perl book publishing could become a cottage industry. And that’s what I’m currently aiming at.</p>
  146. <p>I’ve made a start already. just before the LPW I published a book called <em><a href="https://www.amazon.com/Perl-Taster-Your-First-Hours-ebook/dp/B077MB1LH1">Perl Taster</a></em> which aims to take people through their first two hours of learning Perl. It’s cheap enough (and small enough) that people can give Perl a try without investing too much money or time.</p>
  147. <p>But my plans don’t stop there. I have ideas for half a dozen other books that I can publish over the next few months. Basically, if you’ve one of my training courses over the last five years then you can expect a (short!) book based on that course to appear at some point during 2018. Currently my plans include books on:</p>
  148. <ul>
  149. <li>Moose</li>
  150. <li>DBIx::Class</li>
  151. <li>Modern Core Perl</li>
  152. <li>Dancer2</li>
  153. <li>Testing</li>
  154. </ul>
  155. <p>Obviously, there are plenty of other books that could be written this way. And I don’t want to have to write them all myself. Which is where you come in. Is there a Perl-related subject that you’re an expert on? Would you be interested in writing a book about it?</p>
  156. <p>I’m offering to help people publish Perl books. If you can write a book using Markdown, then let me take care of the complicated bits of turning your text into an e-book and getting it published on Amazon (and, perhaps later, other e-book platforms).</p>
  157. <p>So, over to you. What do you want to write a book about.</p>
  158. <p>p,s. At some point I should probably finish the e-book I was writing about publishing e-books.</p>
  159. <p>The post <a rel="nofollow" href="https://perlhacks.com/2017/12/regenerating-perl-school/">Regenerating Perl School</a> appeared first on <a rel="nofollow" href="https://perlhacks.com">Perl Hacks</a>.</p>
  160. <img src="http://feeds.feedburner.com/~r/PerlHacks/~4/9Y0UdPXskxk" height="1" width="1" alt=""/></div>
  161.    </content>
  162.    <summary type="xhtml">
  163.      <div xmlns="http://www.w3.org/1999/xhtml"><p>About five years ago I ran a few training courses under the Perl School brand. The idea was simple – if you price training courses cheaply and run them at the weekend then you eliminate the most common reasons why people don’t keep their Perl knowledge up to date. Of course, it’s not quite that … </p>
  164. <p class="link-more"><a href="https://perlhacks.com/2017/12/regenerating-perl-school/" class="more-link">Continue reading<span class="screen-reader-text"> "Regenerating Perl School"</span></a></p>
  165. <p>The post <a rel="nofollow" href="https://perlhacks.com/2017/12/regenerating-perl-school/">Regenerating Perl School</a> appeared first on <a rel="nofollow" href="https://perlhacks.com">Perl Hacks</a>.</p>
  166. </div>
  167.    </summary>
  168.    <author>
  169.      <name>Dave Cross</name>
  170.    </author>
  171.    <id>https://perlhacks.com/?p=1777</id>
  172.    <published>2017-12-11T14:30:47Z</published>
  173.    <updated>2017-12-11T14:30:47Z</updated>
  174.    <category term="Books"/>
  175.    <category term="amazon"/>
  176.    <category term="books"/>
  177.    <category term="e-book"/>
  178.    <category term="lpw2017"/>
  179.    <category term="markdown"/>
  180.    <category term="perlschool"/>
  181.  </entry>
  182.  <entry xmlns:flickr="urn:flickr:user" xmlns:dc="http://purl.org/dc/elements/1.1/">
  183.    
  184.    <link rel="alternate" type="text/html" href="http://www.flickr.com/photos/davorg/38072353045/"/>
  185.    <id>tag:flickr.com,2005:/photo/38072353045</id>
  186.    <published>2017-12-10T13:17:34Z</published>
  187.    <updated>2017-12-10T13:17:34Z</updated>
  188.    <flickr:date_taken>2017-12-10T13:17:34-08:00</flickr:date_taken>
  189.    <dc:date.Taken>2017-12-10T13:17:34-08:00</dc:date.Taken>
  190.    <content type="html"> &lt;p&gt;&lt;a href="http://www.flickr.com/people/davorg/"&gt;Dave Cross&lt;/a&gt; posted a photo:&lt;/p&gt;
  191. &lt;p&gt;&lt;a href="http://www.flickr.com/photos/davorg/38072353045/" title="Vinyl ceiling, Village Brighton"&gt;&lt;img src="http://farm5.staticflickr.com/4566/38072353045_aa1f2f6b66_m.jpg" width="240" height="240" alt="Vinyl ceiling, Village Brighton" /&gt;&lt;/a&gt;&lt;/p&gt;
  192.  
  193. &lt;p&gt;via Instagram &lt;a href="http://ift.tt/2BZD24h" rel="nofollow"&gt;ift.tt/2BZD24h&lt;/a&gt;&lt;/p&gt;</content>
  194.    <author>
  195.      <name>Dave Cross</name>
  196.      <uri>http://www.flickr.com/people/davorg/</uri>
  197.      <flickr:nsid>[email protected]</flickr:nsid>
  198.      <flickr:buddyicon>http://farm4.staticflickr.com/3678/buddyicons/[email protected]?1372610206#[email protected]</flickr:buddyicon>
  199.    </author>
  200.    <link rel="license" type="text/html" href="https://creativecommons.org/licenses/by-nc-sa/2.0/deed.en"/>
  201.    <link rel="enclosure" type="image/jpeg" href="http://farm5.staticflickr.com/4566/38072353045_aa1f2f6b66_b.jpg"/>
  202.    <category term="ifttt" scheme="http://www.flickr.com/photos/tags/"/>
  203.    <category term="instagram" scheme="http://www.flickr.com/photos/tags/"/>
  204.    <displaycategories>
  205.            </displaycategories>
  206.    <title>flickr: Vinyl ceiling, Village Brighton</title></entry>
  207.  <entry xmlns:flickr="urn:flickr:user" xmlns:dc="http://purl.org/dc/elements/1.1/">
  208.    
  209.    <link rel="alternate" type="text/html" href="http://www.flickr.com/photos/davorg/25064179048/"/>
  210.    <id>tag:flickr.com,2005:/photo/25064179048</id>
  211.    <published>2017-12-09T14:37:16Z</published>
  212.    <updated>2017-12-09T14:37:16Z</updated>
  213.    <flickr:date_taken>2017-12-09T14:37:16-08:00</flickr:date_taken>
  214.    <dc:date.Taken>2017-12-09T14:37:16-08:00</dc:date.Taken>
  215.    <content type="html"> &lt;p&gt;&lt;a href="http://www.flickr.com/people/davorg/"&gt;Dave Cross&lt;/a&gt; posted a photo:&lt;/p&gt;
  216. &lt;p&gt;&lt;a href="http://www.flickr.com/photos/davorg/25064179048/" title="Made a friend"&gt;&lt;img src="http://farm5.staticflickr.com/4569/25064179048_d17e84e84b_m.jpg" width="240" height="240" alt="Made a friend" /&gt;&lt;/a&gt;&lt;/p&gt;
  217.  
  218. &lt;p&gt;via Instagram &lt;a href="http://ift.tt/2iHDStW" rel="nofollow"&gt;ift.tt/2iHDStW&lt;/a&gt;&lt;/p&gt;</content>
  219.    <author>
  220.      <name>Dave Cross</name>
  221.      <uri>http://www.flickr.com/people/davorg/</uri>
  222.      <flickr:nsid>[email protected]</flickr:nsid>
  223.      <flickr:buddyicon>http://farm4.staticflickr.com/3678/buddyicons/[email protected]?1372610206#[email protected]</flickr:buddyicon>
  224.    </author>
  225.    <link rel="license" type="text/html" href="https://creativecommons.org/licenses/by-nc-sa/2.0/deed.en"/>
  226.    <link rel="enclosure" type="image/jpeg" href="http://farm5.staticflickr.com/4569/25064179048_d17e84e84b_b.jpg"/>
  227.    <category term="ifttt" scheme="http://www.flickr.com/photos/tags/"/>
  228.    <category term="instagram" scheme="http://www.flickr.com/photos/tags/"/>
  229.    <displaycategories>
  230.            </displaycategories>
  231.    <title>flickr: Made a friend</title></entry>
  232.  <entry xmlns:media="http://search.yahoo.com/mrss/">
  233.    <id>tag:github.com,2008:PullRequestEvent/6957602167</id>
  234.    <published>2017-12-07T15:35:22Z</published>
  235.    <updated>2017-12-07T15:35:22Z</updated>
  236.    <link type="text/html" rel="alternate" href="https://github.com/grantm/xml-simple/pull/7"/>
  237.    
  238.    <author>
  239.      <name>davorg</name>
  240.      <email>[email protected]</email>
  241.      <uri>https://github.com/davorg</uri>
  242.    </author>
  243.    <media:thumbnail height="30" width="30" url="https://avatars1.githubusercontent.com/u/24642?s=30&amp;v=4"/>
  244.    <content type="html">&lt;!-- pull_request --&gt;
  245. &lt;div class="d-flex border-bottom border-gray-light py-3"&gt;
  246.  &lt;a href="/davorg" rel="noreferrer"&gt;&lt;img alt="@davorg" class="avatar mr-3" height="32" src="https://avatars2.githubusercontent.com/u/24642?s=64&amp;amp;v=4" width="32"&gt;&lt;/a&gt;
  247.  &lt;div class="d-flex flex-column width-full"&gt;
  248.    &lt;div&gt;
  249.      &lt;div class="d-flex flex-justify-between flex-items-baseline"&gt;
  250.        &lt;div&gt;
  251.          &lt;a href="/davorg" class="link-gray-dark text-bold wb-break-all" data-ga-click="News feed, event click, Event click type:PullRequestEvent target:actor" rel="noreferrer"&gt;davorg&lt;/a&gt; opened a pull request in &lt;a href="/grantm/xml-simple" class="link-gray-dark text-bold wb-break-all" data-ga-click="News feed, event click, Event click type:PullRequestEvent target:repo" rel="noreferrer"&gt;grantm/xml-simple&lt;/a&gt;
  252.        &lt;/div&gt;
  253.        &lt;span class="f6 text-gray-light no-wrap ml-4"&gt;
  254.          &lt;relative-time datetime="2017-12-07T15:35:22Z"&gt;Dec 7, 2017&lt;/relative-time&gt;
  255.        &lt;/span&gt;
  256.      &lt;/div&gt;
  257.    &lt;/div&gt;
  258.  
  259.    &lt;div class="border rounded-1 p-3 my-2"&gt;
  260.      &lt;svg aria-label="Pull request" class="octicon octicon-git-pull-request open d-inline-block mt-1 float-left" height="16" role="img" version="1.1" viewBox="0 0 12 16" width="12"&gt;&lt;path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0 0 10 15a1.993 1.993 0 0 0 1-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 0 0-1 3.72v6.56A1.993 1.993 0 0 0 2 15a1.993 1.993 0 0 0 1-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"&gt;&lt;/path&gt;&lt;/svg&gt;
  261.  
  262.      &lt;div class="ml-4"&gt;
  263.        &lt;div&gt;
  264.          &lt;span class="f3 lh-condensed text-bold text-gray-dark"&gt;&lt;a href="/grantm/xml-simple/pull/7" aria-label="Handle objects that overload stringification" class="text-gray-dark text-bold" data-ga-click="News feed, event click, Event click type:PullRequestEvent target:pull" rel="noreferrer"&gt;Handle objects that overload stringification&lt;/a&gt;&lt;/span&gt;
  265.          &lt;span class="f4 text-gray-light ml-1"&gt;#7&lt;/span&gt;
  266.            &lt;p class="text-gray mt-1 mb-0"&gt;
  267.              &lt;/p&gt;&lt;p&gt;This fixes a problem that we've just seen at my current client. But I think it might be more widely useful.
  268. And, yes, I know that the real fix is t…&lt;/p&gt;
  269.            &lt;p&gt;&lt;/p&gt;
  270.        &lt;/div&gt;
  271.  
  272.          &lt;div class="diffstat d-inline-block mt-3 tooltipped tooltipped-se" aria-label="1 commit with 6 additions and 1 deletion"&gt;
  273.            &lt;span class="text-green"&gt;+6&lt;/span&gt;
  274.            &lt;span class="text-red"&gt;-1&lt;/span&gt;
  275.          &lt;/div&gt;
  276.  
  277.      &lt;/div&gt;
  278.    &lt;/div&gt;
  279.  &lt;/div&gt;
  280. &lt;/div&gt;
  281. </content>
  282.  <title>github: davorg opened a pull request in grantm/xml-simple</title></entry>
  283.  <entry xmlns:media="http://search.yahoo.com/mrss/">
  284.    <id>tag:github.com,2008:PushEvent/6957591241</id>
  285.    <published>2017-12-07T15:33:28Z</published>
  286.    <updated>2017-12-07T15:33:28Z</updated>
  287.    <link type="text/html" rel="alternate" href="https://github.com/davorg/xml-simple/compare/cfd65b8c88...f40660d352"/>
  288.    
  289.    <author>
  290.      <name>davorg</name>
  291.      <email>[email protected]</email>
  292.      <uri>https://github.com/davorg</uri>
  293.    </author>
  294.    <media:thumbnail height="30" width="30" url="https://avatars1.githubusercontent.com/u/24642?s=30&amp;v=4"/>
  295.    <content type="html">&lt;!-- push --&gt;
  296. &lt;div class="d-flex border-bottom border-gray-light py-3"&gt;
  297.  &lt;a href="/davorg" rel="noreferrer"&gt;&lt;img alt="@davorg" class="avatar mr-3" height="32" src="https://avatars2.githubusercontent.com/u/24642?s=64&amp;amp;v=4" width="32"&gt;&lt;/a&gt;
  298.  &lt;div class="d-flex flex-justify-between flex-items-baseline width-full"&gt;
  299.    &lt;div&gt;
  300.      &lt;a href="/davorg" class="link-gray-dark text-bold wb-break-all" data-ga-click="News feed, event click, Event click type:PushEvent target:actor" rel="noreferrer"&gt;davorg&lt;/a&gt; pushed to &lt;a href="/davorg/xml-simple/tree/master" class="branch-name" data-ga-click="News feed, event click, Event click type:PushEvent target:branch" rel="noreferrer"&gt;master&lt;/a&gt; in &lt;a href="/davorg/xml-simple" class="link-gray-dark text-bold wb-break-all" data-ga-click="News feed, event click, Event click type:PushEvent target:repo" rel="noreferrer"&gt;davorg/xml-simple&lt;/a&gt;
  301.        &lt;div class="commits pusher-is-only-committer"&gt;
  302.          &lt;ul&gt;
  303.            &lt;li class="d-flex flex-items-baseline"&gt;
  304.              &lt;span title="davorg"&gt;
  305.                &lt;img alt="@davorg" class="mr-1" height="16" src="https://avatars1.githubusercontent.com/u/24642?s=32&amp;amp;v=4" width="16"&gt;
  306.              &lt;/span&gt;
  307.              &lt;code&gt;&lt;a href="/davorg/xml-simple/commit/f40660d352b2e4df5dfee2bd18d564242d2a67ab" class="mr-1" data-ga-click="News feed, event click, Event click type:PushEvent target:sha" rel="noreferrer"&gt;f40660d&lt;/a&gt;&lt;/code&gt;
  308.              &lt;div class="message"&gt;
  309.                &lt;blockquote&gt;
  310.                  Handle objects that overload stringification
  311.                &lt;/blockquote&gt;
  312.              &lt;/div&gt;
  313.            &lt;/li&gt;
  314.          &lt;/ul&gt;
  315.        &lt;/div&gt;
  316.    &lt;/div&gt;
  317.    &lt;span class="f6 text-gray-light no-wrap ml-4"&gt;
  318.      &lt;relative-time datetime="2017-12-07T15:33:28Z"&gt;Dec 7, 2017&lt;/relative-time&gt;
  319.    &lt;/span&gt;
  320.  &lt;/div&gt;
  321. &lt;/div&gt;
  322. </content>
  323.  <title>github: davorg pushed to master in davorg/xml-simple</title></entry>
  324.  <entry xmlns:media="http://search.yahoo.com/mrss/">
  325.    <id>tag:github.com,2008:ForkEvent/6957544487</id>
  326.    <published>2017-12-07T15:25:22Z</published>
  327.    <updated>2017-12-07T15:25:22Z</updated>
  328.    <link type="text/html" rel="alternate" href="https://github.com/davorg/xml-simple"/>
  329.    
  330.    <author>
  331.      <name>davorg</name>
  332.      <email>[email protected]</email>
  333.      <uri>https://github.com/davorg</uri>
  334.    </author>
  335.    <media:thumbnail height="30" width="30" url="https://avatars1.githubusercontent.com/u/24642?s=30&amp;v=4"/>
  336.    <content type="html">&lt;!-- fork --&gt;
  337. &lt;div class="d-flex flex-items-baseline border-bottom border-gray-light py-3"&gt;
  338.  &lt;a href="/davorg" rel="noreferrer"&gt;&lt;img alt="@davorg" class="avatar mr-3" height="32" src="https://avatars2.githubusercontent.com/u/24642?s=64&amp;amp;v=4" width="32"&gt;&lt;/a&gt;
  339.  &lt;div class="d-flex flex-justify-between flex-items-baseline width-full"&gt;
  340.    &lt;div&gt;
  341.      &lt;a href="/davorg" class="link-gray-dark text-bold wb-break-all" data-ga-click="News feed, event click, Event click type:ForkEvent target:actor" rel="noreferrer"&gt;davorg&lt;/a&gt; forked &lt;a href="/davorg/xml-simple" class="link-gray-dark text-bold wb-break-all" data-ga-click="News feed, event click, Event click type:ForkEvent target:parent" title="davorg/xml-simple" rel="noreferrer"&gt;davorg/xml-simple&lt;/a&gt; from &lt;a href="/grantm/xml-simple" class="link-gray-dark text-bold wb-break-all" data-ga-click="News feed, event click, Event click type:ForkEvent target:repo" rel="noreferrer"&gt;grantm/xml-simple&lt;/a&gt;
  342.    &lt;/div&gt;
  343.    &lt;span class="f6 text-gray-light no-wrap ml-4"&gt;
  344.      &lt;relative-time datetime="2017-12-07T15:25:22Z"&gt;Dec 7, 2017&lt;/relative-time&gt;
  345.    &lt;/span&gt;
  346.  &lt;/div&gt;
  347. &lt;/div&gt;
  348. </content>
  349.  <title>github: davorg forked davorg/xml-simple from grantm/xml-simple</title></entry>
  350.  <entry xmlns:flickr="urn:flickr:user" xmlns:dc="http://purl.org/dc/elements/1.1/">
  351.    
  352.    <link rel="alternate" type="text/html" href="http://www.flickr.com/photos/davorg/27070138279/"/>
  353.    <id>tag:flickr.com,2005:/photo/27070138279</id>
  354.    <published>2017-12-05T08:40:47Z</published>
  355.    <updated>2017-12-05T08:40:47Z</updated>
  356.    <flickr:date_taken>2017-12-05T08:40:47-08:00</flickr:date_taken>
  357.    <dc:date.Taken>2017-12-05T08:40:47-08:00</dc:date.Taken>
  358.    <content type="html"> &lt;p&gt;&lt;a href="http://www.flickr.com/people/davorg/"&gt;Dave Cross&lt;/a&gt; posted a photo:&lt;/p&gt;
  359. &lt;p&gt;&lt;a href="http://www.flickr.com/photos/davorg/27070138279/" title="Something colourful on Potters Fields today"&gt;&lt;img src="http://farm5.staticflickr.com/4585/27070138279_f8d7190365_m.jpg" width="240" height="240" alt="Something colourful on Potters Fields today" /&gt;&lt;/a&gt;&lt;/p&gt;
  360.  
  361. &lt;p&gt;via Instagram &lt;a href="http://ift.tt/2ASghBw" rel="nofollow"&gt;ift.tt/2ASghBw&lt;/a&gt;&lt;/p&gt;</content>
  362.    <author>
  363.      <name>Dave Cross</name>
  364.      <uri>http://www.flickr.com/people/davorg/</uri>
  365.      <flickr:nsid>[email protected]</flickr:nsid>
  366.      <flickr:buddyicon>http://farm4.staticflickr.com/3678/buddyicons/[email protected]?1372610206#[email protected]</flickr:buddyicon>
  367.    </author>
  368.    <link rel="license" type="text/html" href="https://creativecommons.org/licenses/by-nc-sa/2.0/deed.en"/>
  369.    <link rel="enclosure" type="image/jpeg" href="http://farm5.staticflickr.com/4585/27070138279_f8d7190365_b.jpg"/>
  370.    <category term="ifttt" scheme="http://www.flickr.com/photos/tags/"/>
  371.    <category term="instagram" scheme="http://www.flickr.com/photos/tags/"/>
  372.    <displaycategories>
  373.            </displaycategories>
  374.    <title>flickr: Something colourful on Potters Fields today</title></entry>
  375.  <entry xmlns:flickr="urn:flickr:user" xmlns:dc="http://purl.org/dc/elements/1.1/">
  376.    
  377.    <link rel="alternate" type="text/html" href="http://www.flickr.com/photos/davorg/27069038059/"/>
  378.    <id>tag:flickr.com,2005:/photo/27069038059</id>
  379.    <published>2017-12-05T07:07:10Z</published>
  380.    <updated>2017-12-05T07:07:10Z</updated>
  381.    <flickr:date_taken>2017-12-05T07:07:10-08:00</flickr:date_taken>
  382.    <dc:date.Taken>2017-12-05T07:07:10-08:00</dc:date.Taken>
  383.    <content type="html"> &lt;p&gt;&lt;a href="http://www.flickr.com/people/davorg/"&gt;Dave Cross&lt;/a&gt; posted a photo:&lt;/p&gt;
  384. &lt;p&gt;&lt;a href="http://www.flickr.com/photos/davorg/27069038059/" title="Gorillaz"&gt;&lt;img src="http://farm5.staticflickr.com/4541/27069038059_01cd41beca_m.jpg" width="240" height="240" alt="Gorillaz" /&gt;&lt;/a&gt;&lt;/p&gt;
  385.  
  386. &lt;p&gt;via Instagram &lt;a href="http://ift.tt/2inhKVO" rel="nofollow"&gt;ift.tt/2inhKVO&lt;/a&gt;&lt;/p&gt;</content>
  387.    <author>
  388.      <name>Dave Cross</name>
  389.      <uri>http://www.flickr.com/people/davorg/</uri>
  390.      <flickr:nsid>[email protected]</flickr:nsid>
  391.      <flickr:buddyicon>http://farm4.staticflickr.com/3678/buddyicons/[email protected]?1372610206#[email protected]</flickr:buddyicon>
  392.    </author>
  393.    <link rel="license" type="text/html" href="https://creativecommons.org/licenses/by-nc-sa/2.0/deed.en"/>
  394.    <link rel="enclosure" type="image/jpeg" href="http://farm5.staticflickr.com/4541/27069038059_01cd41beca_b.jpg"/>
  395.    <category term="ifttt" scheme="http://www.flickr.com/photos/tags/"/>
  396.    <category term="instagram" scheme="http://www.flickr.com/photos/tags/"/>
  397.    <displaycategories>
  398.            </displaycategories>
  399.    <title>flickr: Gorillaz</title></entry>
  400.  <entry>
  401.    <title>perl hacks: London Perl Workshop Report</title>
  402.    <link rel="alternate" href="http://feedproxy.google.com/~r/PerlHacks/~3/glBfuQ5t5r8/" type="text/html"/>
  403.    <content type="html">&lt;p&gt;(Photo above by Chris Jack)&lt;/p&gt;
  404. &lt;p&gt;Last Saturday was the annual London Perl Workshop. I should write up what happened before I forget it all.&lt;/p&gt;
  405. &lt;p&gt;I arrived at about 8:30 in the morning and was able to check in quickly – collecting a bit of swag which included a free t-shirt as I was a speaker. I then made my way up to the main lecture theatre in order to see Katherine Spice welcoming people to the day on behalf of the new team of organisers. After that headed off to the smaller lecture theatre to set up for my tutorial. There were a few differences from previous years. Firstly, I was giving a completely Perl-free tutorial (about on-page SEO techniques) and secondly, I had been moved out of the tutorial track and into one of the main talk tracks. As a side effect of that second change, I was also asked to trim my talk from my usual two hours to a more “talk-like” eighty minutes.&lt;/p&gt;
  406. &lt;p&gt;The talk seemed to go well. I got some interesting questions and a few people came up to me later in the day to tell me they had found it interesting useful (sometimes both!) The slides to the talk are available on SlideShare: &lt;a class="notranslate" title="Web Site Tune-Up - Improve Your Googlejuice" href="https://www.slideshare.net/davorg/web-site-tuneup-improve-your-googlejuice" target="_blank" rel="noopener"&gt;Web Site Tune-Up – Improve Your Googlejuice.&lt;/a&gt;&lt;/p&gt;
  407. &lt;p&gt;Following that, I had time to see one talk before the coffee break and I chose &lt;a href="http://act.yapc.eu/lpw2017/talk/7219"&gt;Why learning a bit of Crypto is good for you‎ &lt;/a&gt;by Colin Newell. Colin gave a good (if, necessarily rather shallow) explanation of how learning a small amount of cryptography can help you improve the security of your systems.&lt;/p&gt;
  408. &lt;p&gt;Then it was was the morning coffee break. For the past few years, this break has traditionally included cakes which were supplied by a sponsor. When that didn’t look like happening this year, organiser Neil Bowers (with a gentle nudge from Leon Timmermans) came up with &lt;a href="http://neilb.org/2017/10/29/community-cakes-lpw-2017.html"&gt;the idea of a community bake&lt;/a&gt;. And that’s what happened. A number of attendees baked cakes for us all. I had one of Neil’s blueberry muffins and it was lovely.&lt;/p&gt;
  409. &lt;p&gt;There was a slight change in the schedule after the coffee break. Matt Trout was unable to be at the workshop so, at the last minute, JJ Allen stepped in and gave his talk &lt;a href="http://act.yapc.eu/lpw2017/talk/7265"&gt;To delete or not to delete, that is the question‎&lt;/a&gt;, which was about some impending data protection laws which will affect all businesses. I stayed in the same room to see Neil Bowers explain &lt;a href="http://act.yapc.eu/lpw2017/talk/7242"&gt;The PAUSE Operating Model‎ &lt;/a&gt;and then JJ returned to talk about something completely different – &lt;a href="http://act.yapc.eu/lpw2017/talk/7266"&gt;Perl and Docker, sitting in a tree‎&lt;/a&gt;.  JJ’s company, Opus VL, have released some of their &lt;a href="https://metacpan.org/pod/OpusVL::Docker"&gt;Docker infrastructure code&lt;/a&gt; to CPAN and I’m sure many people will find it useful.&lt;/p&gt;
  410. &lt;p&gt;Then it was lunchtime. I bought a sandwich from the university’s cafe and sat in the foyer talking to various friends who walked past.&lt;/p&gt;
  411. &lt;p&gt;I started the afternoon watching Paul Evans on &lt;a href="http://act.yapc.eu/lpw2017/talk/7243"&gt;‎Devel::MAT updated‎&lt;/a&gt;. &lt;a href="https://metacpan.org/pod/Devel::MAT"&gt;Devel::MAT&lt;/a&gt; is a development tool which aims to do for memory analysis what &lt;a href="https://metacpan.org/pod/Devel::NYTProf"&gt;Devel::NYTProf&lt;/a&gt; does for profiling. It looks very useful. That was followed by Julien Fieggehenn’s talk &lt;a href="http://act.yapc.eu/lpw2017/talk/7220"&gt;Turning humans into developers with Perl‎.&lt;/a&gt; Julien doesn’t just train people in Perl, he acts as a mentor for them for a couple of months when they join his company, so he was able to talk in some detail about much wider issues than just choosing which topics to cover in a training course.&lt;/p&gt;
  412. &lt;p&gt;Talking about wider issues, I then saw Tom Hukins’ talk &lt;a href="http://act.yapc.eu/lpw2017/talk/7263"&gt;Development: More than Writing Code?‎ &lt;/a&gt;Tom is, of course, right that there’s more to being a good developer than just writing good code. This is a topic that I’m thinking of developing a training course on. Tom was followed by Paul Johnson giving good advice on &lt;b&gt;&lt;a href="http://act.yapc.eu/lpw2017/talk/7252"&gt;‎&lt;/a&gt;&lt;/b&gt;&lt;a href="http://act.yapc.eu/lpw2017/talk/7252"&gt;Modernising A Legacy Perl Application&lt;/a&gt;.&lt;/p&gt;
  413. &lt;p&gt;The afternoon coffee break included some professionally baked pastries. They were also lovely, but don’t think they were appreciated quite as much as the morning’s community versions.&lt;/p&gt;
  414. &lt;p&gt;After the coffee break, we all gathered in the main lecture theatre for the plenary session. Ann Barcomb spoke about &lt;a href="http://act.yapc.eu/lpw2017/talk/7273"&gt;Fifteen Years of Contributing Casually‎&lt;/a&gt;. Ann was once a Perl developer. I first met her at the first YAPC::Europe in London in 2000 and she was then part of the organising team for the second YAPC::Europe in Amsterdam in 2001. But since then she has become a researcher into the sociology of the open source movement. You can read a lot of her research on &lt;a href="http://www.barcomb.org/"&gt;her &lt;/a&gt;web site. Her talk illustrated her findings with some personal anecdotes about her own casual contributions to the Perl community. Everyone seemed to find it fascinating and the Q&amp;A at the end of the talk showed every signs of turning into a full-scale discussion. On a personal level, it was great to catch up with Ann again about fifteen years after we had been in the same room together.&lt;/p&gt;
  415. &lt;p&gt;And then there were the lightning talks. They were their usual mixture of intriguing and entertaining. Mark Keating (enjoying his first LPW that he wasn’t organising) implored us to get involved in the &lt;a href="https://ww2.enlightenedperl.org/"&gt;Enlightened Perl Organisation&lt;/a&gt;. I announced a plan to publish more Perl books (of which, more later). I was particularly impressed by &lt;span title=""&gt;Kenichi Ishigaki who flew in from Japan just to give a lightning talk about his module&lt;a href="https://metacpan.org/pod/Perl::PrereqScanner::NotQuiteLite"&gt; Perl::PrereqScanner::NotQuiteLite.&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
  416. &lt;p&gt;After that, there were a few closing words from Neil Bowers and, in another innovation brought in by the new organisers, drinks were served on site rather than in a local pub. Of course, some people went off to a local pub after that as well.&lt;/p&gt;
  417. &lt;p&gt;As always, it was a great day. The new organising team seem to have hit the ground running and produced an impressive workshop. My thanks to &lt;a href="http://act.yapc.eu/lpw2017/team.html"&gt;the organisers&lt;/a&gt;, the volunteers, the speakers, &lt;a href="http://act.yapc.eu/lpw2017/sponsors.html"&gt;the sponsors&lt;/a&gt; and all of the attendees.&lt;/p&gt;
  418. &lt;p&gt;I’m already looking forward to next year’s workshop.&lt;/p&gt;
  419. &lt;p&gt;The post &lt;a rel="nofollow" href="https://perlhacks.com/2017/12/london-perl-workshop-report/"&gt;London Perl Workshop Report&lt;/a&gt; appeared first on &lt;a rel="nofollow" href="https://perlhacks.com"&gt;Perl Hacks&lt;/a&gt;.&lt;/p&gt;
  420. &lt;img src="http://feeds.feedburner.com/~r/PerlHacks/~4/glBfuQ5t5r8" height="1" width="1" alt=""/&gt;</content>
  421.    <summary type="xhtml">
  422.      <div xmlns="http://www.w3.org/1999/xhtml"><p>(Photo above by Chris Jack) Last Saturday was the annual London Perl Workshop. I should write up what happened before I forget it all. I arrived at about 8:30 in the morning and was able to check in quickly – collecting a bit of swag which included a free t-shirt as I was a speaker. … </p>
  423. <p class="link-more"><a href="https://perlhacks.com/2017/12/london-perl-workshop-report/" class="more-link">Continue reading<span class="screen-reader-text"> "London Perl Workshop Report"</span></a></p>
  424. <p>The post <a rel="nofollow" href="https://perlhacks.com/2017/12/london-perl-workshop-report/">London Perl Workshop Report</a> appeared first on <a rel="nofollow" href="https://perlhacks.com">Perl Hacks</a>.</p>
  425. </div>
  426.    </summary>
  427.    <author>
  428.      <name>Dave Cross</name>
  429.    </author>
  430.    <id>https://perlhacks.com/?p=1768</id>
  431.    <published>2017-12-02T11:18:56Z</published>
  432.    <updated>2017-12-02T11:18:56Z</updated>
  433.    <category term="Conferences"/>
  434.    <category term="conferences"/>
  435.    <category term="london perl workshop"/>
  436.    <category term="lpw"/>
  437.    <category term="lpw2017"/>
  438.    <category term="perl"/>
  439.  </entry>
  440.  <entry xmlns:media="http://search.yahoo.com/mrss/">
  441.    <id>tag:github.com,2008:IssuesEvent/6923489319</id>
  442.    <published>2017-11-30T09:14:46Z</published>
  443.    <updated>2017-11-30T09:14:46Z</updated>
  444.    <link type="text/html" rel="alternate" href="https://github.com/blogs-perl-org/blogs.perl.org/issues/344"/>
  445.    
  446.    <author>
  447.      <name>davorg</name>
  448.      <email>[email protected]</email>
  449.      <uri>https://github.com/davorg</uri>
  450.    </author>
  451.    <media:thumbnail height="30" width="30" url="https://avatars1.githubusercontent.com/u/24642?s=30&amp;v=4"/>
  452.    <content type="html">&lt;!-- issues --&gt;
  453. &lt;div class="d-flex border-bottom border-gray-light py-3"&gt;
  454.  &lt;a href="/davorg" rel="noreferrer"&gt;&lt;img alt="@davorg" class="avatar mr-3" height="32" src="https://avatars2.githubusercontent.com/u/24642?s=64&amp;amp;v=4" width="32"&gt;&lt;/a&gt;
  455.  &lt;div class="d-flex flex-column width-full"&gt;
  456.    &lt;div&gt;
  457.      &lt;div class="d-flex flex-justify-between flex-items-baseline"&gt;
  458.        &lt;div&gt;
  459.          &lt;a href="/davorg" class="link-gray-dark text-bold wb-break-all" data-ga-click="News feed, event click, Event click type:IssuesEvent target:actor" rel="noreferrer"&gt;davorg&lt;/a&gt; closed an issue in &lt;a href="/blogs-perl-org/blogs.perl.org" class="link-gray-dark text-bold wb-break-all" data-ga-click="News feed, event click, Event click type:IssuesEvent target:repo" rel="noreferrer"&gt;blogs-perl-org/blogs.perl.org&lt;/a&gt;
  460.        &lt;/div&gt;
  461.        &lt;span class="f6 text-gray-light no-wrap ml-4"&gt;
  462.          &lt;relative-time datetime="2017-11-30T09:14:46Z"&gt;Nov 30, 2017&lt;/relative-time&gt;
  463.        &lt;/span&gt;
  464.      &lt;/div&gt;
  465.    &lt;/div&gt;
  466.  
  467.    &lt;div class="border rounded-1 p-3 mt-3"&gt;
  468.      &lt;svg aria-label="Issue" class="octicon octicon-issue-closed closed d-inline-block mt-1 float-left" height="16" role="img" version="1.1" viewBox="0 0 16 16" width="16"&gt;&lt;path fill-rule="evenodd" d="M7 10h2v2H7v-2zm2-6H7v5h2V4zm1.5 1.5l-1 1L12 9l4-4.5-1-1L12 7l-1.5-1.5zM8 13.7A5.71 5.71 0 0 1 2.3 8c0-3.14 2.56-5.7 5.7-5.7 1.83 0 3.45.88 4.5 2.2l.92-.92A6.947 6.947 0 0 0 8 1C4.14 1 1 4.14 1 8s3.14 7 7 7 7-3.14 7-7l-1.52 1.52c-.66 2.41-2.86 4.19-5.48 4.19v-.01z"&gt;&lt;/path&gt;&lt;/svg&gt;
  469.      &lt;div class="ml-4"&gt;
  470.        &lt;span class="f3 lh-condensed text-bold text-gray-dark"&gt;
  471.          &lt;a href="/blogs-perl-org/blogs.perl.org/issues/344" aria-label="User bonnyin is a spammer" class="text-gray-dark" data-ga-click="News feed, event click, Event click type:IssuesEvent target:issue" title="User bonnyin is a spammer" rel="noreferrer"&gt;User bonnyin is a spammer&lt;/a&gt;
  472.        &lt;/span&gt;
  473.        &lt;span class="f4 text-gray-light ml-1"&gt;#344&lt;/span&gt;
  474.          &lt;p class="text-gray mt-1 mb-0"&gt;
  475.            &lt;/p&gt;&lt;p&gt;&lt;code&gt;http://blogs.perl.org/users/bonnyin/
  476. http://blogs.perl.org/users/bonnyin/2017/11/berufskleider-fur-frauen.html
  477. &lt;/code&gt;&lt;/p&gt;
  478.          &lt;p&gt;&lt;/p&gt;
  479.  
  480.          &lt;div class="f6 text-gray mt-3"&gt;
  481.            1 comment
  482.          &lt;/div&gt;
  483.      &lt;/div&gt;
  484.    &lt;/div&gt;
  485.  &lt;/div&gt;
  486. &lt;/div&gt;
  487. </content>
  488.  <title>github: davorg closed an issue in blogs-perl-org/blogs.perl.org</title></entry>
  489.  <entry xmlns:media="http://search.yahoo.com/mrss/">
  490.    <id>tag:github.com,2008:IssueCommentEvent/6923489310</id>
  491.    <published>2017-11-30T09:14:45Z</published>
  492.    <updated>2017-11-30T09:14:45Z</updated>
  493.    <link type="text/html" rel="alternate" href="https://github.com/blogs-perl-org/blogs.perl.org/issues/344#issuecomment-348127818"/>
  494.    
  495.    <author>
  496.      <name>davorg</name>
  497.      <email>[email protected]</email>
  498.      <uri>https://github.com/davorg</uri>
  499.    </author>
  500.    <media:thumbnail height="30" width="30" url="https://avatars1.githubusercontent.com/u/24642?s=30&amp;v=4"/>
  501.    <content type="html">&lt;!-- issue_comment --&gt;
  502. &lt;div class="d-flex border-bottom border-gray-light py-3"&gt;
  503.  &lt;a href="/davorg" rel="noreferrer"&gt;&lt;img alt="@davorg" class="avatar mr-3" height="32" src="https://avatars2.githubusercontent.com/u/24642?s=64&amp;amp;v=4" width="32"&gt;&lt;/a&gt;
  504.  &lt;div class="d-flex flex-column width-full"&gt;
  505.    &lt;div&gt;
  506.      &lt;div class="d-flex flex-justify-between flex-items-baseline"&gt;
  507.        &lt;div&gt;
  508.          &lt;a href="/davorg" class="link-gray-dark text-bold wb-break-all" data-ga-click="News feed, event click, Event click type:IssueCommentEvent target:actor" rel="noreferrer"&gt;davorg&lt;/a&gt; commented on issue &lt;a href="/blogs-perl-org/blogs.perl.org/issues/344#issuecomment-348127818" class="link-gray-dark text-bold" data-ga-click="News feed, event click, Event click type:IssueCommentEvent target:issue-comment" title="User bonnyin is a spammer" rel="noreferrer"&gt;blogs-perl-org/blogs.perl.org#344&lt;/a&gt;
  509.        &lt;/div&gt;
  510.        &lt;span class="f6 text-gray-light ml-4"&gt;
  511.          &lt;relative-time datetime="2017-11-30T09:14:45Z"&gt;Nov 30, 2017&lt;/relative-time&gt;
  512.        &lt;/span&gt;
  513.      &lt;/div&gt;
  514.    &lt;/div&gt;
  515.    &lt;div class="message markdown-body mt-3"&gt;
  516.      &lt;blockquote&gt;
  517.        &lt;p&gt;Thanks. Nuked.&lt;/p&gt;
  518.      &lt;/blockquote&gt;
  519.    &lt;/div&gt;
  520.  &lt;/div&gt;
  521. &lt;/div&gt;
  522. </content>
  523.  <title>github: davorg commented on issue blogs-perl-org/blogs.perl.org#344</title></entry>
  524.  <entry>
  525.    <title>slideshare: Web Site Tune-Up - Improve Your Googlejuice</title>
  526.    <link rel="alternate" href="https://www.slideshare.net/davorg/web-site-tuneup-improve-your-googlejuice" type="text/html"/>
  527.    <content type="html">
  528.        &lt;img alt="" src="//cdn.slidesharecdn.com/ss_thumbnails/seo-171129091138-thumbnail-2.jpg?cb=1511946764" style="border:1px solid #C3E6D8;float:right;" /&gt;&lt;br&gt; A talk about on-page SEO that I gave at the 2017 London Perl Workshop
  529.      </content>
  530.    <summary type="html">
  531.        &lt;img alt="" src="//cdn.slidesharecdn.com/ss_thumbnails/seo-171129091138-thumbnail-2.jpg?cb=1511946764" style="border:1px solid #C3E6D8;float:right;" /&gt;&lt;br&gt; A talk about on-page SEO that I gave at the 2017 London Perl Workshop
  532.      </summary>
  533.    <author>
  534.      <name>[email protected](davorg)</name>
  535.    </author>
  536.    <id>https://www.slideshare.net/davorg/web-site-tuneup-improve-your-googlejuice</id>
  537.    <published>2017-11-29T09:11:38Z</published>
  538.    <updated>2017-11-29T09:11:38Z</updated>
  539.  </entry>
  540.  <entry>
  541.    <title>perl hacks: London Perl Workshop Klaxon</title>
  542.    <link rel="alternate" href="http://feedproxy.google.com/~r/PerlHacks/~3/0qM-5SRD6VM/" type="text/html"/>
  543.    <content type="xhtml">
  544.      <div xmlns="http://www.w3.org/1999/xhtml"><p>The <a href="http://act.yapc.eu/lpw2017/">London Perl Workshop</a> is looking frighteningly imminent. It’s on November 25th – that’s less than three weeks away. All across the capital (and even further afield) if you listen hard you will hear the sounds of speakers frantically trying to get their talks ready.</p>
  545. <p>That, at least, is how I have spent my weekend. I’m presenting a new training course at the workshop and I’ve been working hard on the slides for the last couple of days.</p>
  546. <p>This new course is a bit of an experiment for me. It’s a completely Perl-free session. For most of this year, I’ve been working for a well-known property portal and the work I’ve been doing for them has concentrated on search engine optimisation and I’m going to take this opportunity to share some of my new-found knowledge with a room full of people.</p>
  547. <p>I know what you’re thinking. SEO is either a) really dull keyword research or b) snake-oil. To be fair, I’ve seen both of those things, but that’s not what I’m going to be covering. I’d hate to be seen as either boring or a snake-oil salesman!</p>
  548. <p>No, I’m going to be covering something that I think is far more interesting. The course will be all about making your web site more attractive to Google. And if Google likes your web site, they will crawl your site more often, extract more useful information from it and (hopefully) show your site in response to more user search queries. Getting your site to appear in more search results means more visitors and more visitors means a more successful web site.</p>
  549. <p>I won’t be covering anything complicated. There’s nothing that you won’t be able to implement in a couple of hours. Anyone could use these techniques – but the point is that most people don’t. That’s why they work.</p>
  550. <p>The <a href="http://act.yapc.eu/lpw2017/schedule">schedule</a> hasn’t been published yet, so I don’t know when I’ll be giving the talk, but I expect to have that information in the next few days. I do know that my slot is 80 minutes – that’s because the organisers have received a large number of high-quality proposals, so we all have to squeeze up a bit to fit in as many of them as possible.</p>
  551. <p>The London Perl Workshop is one of my favourite conferences. The range of talks is always great. And it seems that this year’s workshop (which has a new organising team) is going to be no exception.</p>
  552. <p>Hope to see some of you on 25th November.</p>
  553. <p>The post <a rel="nofollow" href="https://perlhacks.com/2017/11/london-perl-workshop-klaxon/">London Perl Workshop Klaxon</a> appeared first on <a rel="nofollow" href="https://perlhacks.com">Perl Hacks</a>.</p>
  554. <img src="http://feeds.feedburner.com/~r/PerlHacks/~4/0qM-5SRD6VM" height="1" width="1" alt=""/></div>
  555.    </content>
  556.    <summary type="xhtml">
  557.      <div xmlns="http://www.w3.org/1999/xhtml"><p>The London Perl Workshop is looking frighteningly imminent. It’s on November 25th – that’s less than three weeks away. All across the capital (and even further afield) if you listen hard you will hear the sounds of speakers frantically trying to get their talks ready. That, at least, is how I have spent my weekend. I’m … </p>
  558. <p class="link-more"><a href="https://perlhacks.com/2017/11/london-perl-workshop-klaxon/" class="more-link">Continue reading<span class="screen-reader-text"> "London Perl Workshop Klaxon"</span></a></p>
  559. <p>The post <a rel="nofollow" href="https://perlhacks.com/2017/11/london-perl-workshop-klaxon/">London Perl Workshop Klaxon</a> appeared first on <a rel="nofollow" href="https://perlhacks.com">Perl Hacks</a>.</p>
  560. </div>
  561.    </summary>
  562.    <author>
  563.      <name>Dave Cross</name>
  564.    </author>
  565.    <id>https://perlhacks.com/?p=1755</id>
  566.    <published>2017-11-05T16:47:30Z</published>
  567.    <updated>2017-11-05T16:47:30Z</updated>
  568.    <category term="Conferences"/>
  569.    <category term="conference"/>
  570.    <category term="london perl workshop"/>
  571.    <category term="lpw"/>
  572.    <category term="lpw2018"/>
  573.    <category term="perl"/>
  574.    <category term="seo"/>
  575.  </entry>
  576.  <entry>
  577.    <title>davblog: When Smart Meters Aren’t</title>
  578.    <link rel="alternate" href="http://feedproxy.google.com/~r/realdavblog/~3/WXZ58QNh3J0/smart-meters-arent.html" type="text/html"/>
  579.    <content type="html">&lt;p&gt;In a process that took ten years, from 1986 to 1996, the Conservative government privatised energy supply in the UK and turned it into a competitive marketplace. The British public resigned themselves to a lifetime of scouring pricing leaflets and frequently changing energy suppliers in order to get the best deal. This became simpler with the introduction of comparison sites like &lt;a href="https://www.uswitch.com/"&gt;uSwitch&lt;/a&gt; and nowadays most switches can be completed online with very little effort on the part of the customer.&lt;/p&gt;
  580. &lt;p&gt;Of course, one of the crucial reasons why this works is that nothing actually changes on your premises. Your gas and electricity are still supplied through the same meters. The actual changeover is just a flick of a switch or a turn of a tap in a distribution centre miles from your house.&lt;/p&gt;
  581. &lt;p&gt;I’m a member of the Money Saving Expert’s &lt;a href="https://www.moneysavingexpert.com/cheapenergyclub"&gt;Cheap Energy Club&lt;/a&gt;. This makes my life even easier. They know all about our energy usage and a couple of times a year I get an email from them suggesting that I could change a bit of money by switching to a different plan.&lt;/p&gt;
  582. &lt;p&gt;They also set up deals for their customers. They have enough clout that they can go to big energy suppliers and say “we’ll give you X,000 new customers if you can give them a good fixed deal on power”.&lt;/p&gt;
  583. &lt;p&gt;And that’s how I switched to British Gas in February 2016. I got a good fixed deal through the Cheap Energy Club.&lt;/p&gt;
  584. &lt;p&gt;The next innovation in British power supply was the recent introduction of smart meters. These are meters that can be read remotely by the suppliers, eliminating the need for meter readers. Because it’s automatic, the suppliers will read your meters far more frequently (daily, or even more often) giving customers a far better picture of their usage. You even get a little display device which communicates with the meter and gives minute by minute information about how much power you are using.&lt;/p&gt;
  585. &lt;p&gt;Last August I investigated getting a Smart Meter through British Gas. They came and fitted it and everything seemed to work well. All was well with the world.&lt;/p&gt;
  586. &lt;p&gt;Then, a couple of months ago, British Gas announced massive price hikes. This didn’t bother me at the time as I was on a fixed deal. But that deal was going to end in October – at which point my electricity was going to get very expensive.&lt;/p&gt;
  587. &lt;p&gt;A week or so later, I got an email from the Cheap Energy Club telling me what I already knew. But also suggesting a few alternative plans. I glanced through them and agreed with their suggestion of a fixed plan with Ovo. My power would go up in price – but by nowhere near as much as it would with British Gas. I clicked the relevant buttons and the switchover started.&lt;/p&gt;
  588. &lt;p&gt;Ovo started supplying my power this week and sent me an email asking for initial meter readings. I contacted them on Twitter, pointing out that I had smart meters, so there was no need for me to send them manual readings.&lt;/p&gt;
  589. &lt;p&gt;Their first reply was vaguely encouraging&lt;/p&gt;
  590. &lt;blockquote class="twitter-tweet" data-width="525"&gt;
  591. &lt;p lang="en" dir="ltr"&gt;Welcome to OVO, Dave. As we&amp;#39;re in the process of taking over the smart meters so that it sends us your readings, I&amp;#39;d submit them yourself&lt;/p&gt;
  592. &lt;p&gt;— OVO Energy (@OVOEnergy) &lt;a href="https://twitter.com/OVOEnergy/status/915560091910332416?ref_src=twsrc%5Etfw"&gt;October 4, 2017&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;
  593. &lt;p&gt;&lt;script async src="//platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;&lt;/p&gt;
  594. &lt;p&gt;But actually, that turned out to be untrue. The truth is that there are (currently) two versions of the smart meter system. Everyone who has had a smart meter installed up until now has been given a system called SMETS1. And SMETS1 meters can only be read remotely by the company who installed them. There’s a new version called SMETS2 which will be rolled out soon, which allows all companies to read the same meters. And there will be a SMETS1 upgrade at some point (starting late 2018 is the best estimate I’ve been able to get) which will bring the same feature to the older meters (and by “older”, I mean the ones that have been installed everywhere).&lt;/p&gt;
  595. &lt;p&gt;Of course, the SMETS1 meters can be used to supply power to customers of any company. But only working as dumb meters which the customers have to read manually. And, yes, I know this is very much a first world problem, but it would be nice if technology actually moved us forward!&lt;/p&gt;
  596. &lt;p&gt;I see this very much as a failure of regulation. The government have been in a real hurry to get all households in the UK on smart meters. At one point they wanted us all switched over by 2020. I understand that target has now been softened so that every household must be offered a new meter by 2020. But it seems that somewhere in the rush to make the meters available, the most obvious requirements have been dropped.&lt;/p&gt;
  597. &lt;p&gt;The power companies keep this all very quiet. The market for power supply in the UK isn’t growing particularly quickly, so they’re all desperate to grab each other’s customers. And they won’t tell us anything that would make us think twice about switching supplier.&lt;/p&gt;
  598. &lt;p&gt;Ovo will come out and fit new smart meters for me. And (like the original British Gas installation) it will be “free”. Of course, they aren’t giving anything away and customers are paying for these “free” installations in their power costs. It would be interesting to see how many households have had multiple smart meter installations.&lt;/p&gt;
  599. &lt;p&gt;Of course, if you’re switching to save money (as most of us are), then I’m not suggesting that you shouldn’t switch if your smart meters will no longer be smart. But I’d suggest asking your new supplier if they can use your previous supplier’s smart meters. And making a loud “tut” sound when they say they can’t.&lt;/p&gt;
  600. &lt;p&gt;And when you’re offered new smart meters, don’t get them installed unless they are SMETS2.&lt;/p&gt;
  601. &lt;p&gt;The post &lt;a rel="nofollow" href="https://blog.dave.org.uk/2017/10/smart-meters-arent.html"&gt;When Smart Meters Aren&amp;#8217;t&lt;/a&gt; appeared first on &lt;a rel="nofollow" href="https://blog.dave.org.uk"&gt;Davblog&lt;/a&gt;.&lt;/p&gt;
  602. &lt;img src="http://feeds.feedburner.com/~r/realdavblog/~4/WXZ58QNh3J0" height="1" width="1" alt=""/&gt;</content>
  603.    <summary type="xhtml">
  604.      <div xmlns="http://www.w3.org/1999/xhtml"><p>In a process that took ten years, from 1986 to 1996, the Conservative government privatised energy supply in the UK and turned it into a competitive marketplace. The British public resigned themselves to a lifetime of scouring pricing leaflets and frequently changing energy suppliers in order to get the best deal. This became simpler with … </p>
  605. <p class="link-more"><a href="https://blog.dave.org.uk/2017/10/smart-meters-arent.html" class="more-link">Continue reading<span class="screen-reader-text"> "When Smart Meters Aren’t"</span></a></p>
  606. <p>The post <a rel="nofollow" href="https://blog.dave.org.uk/2017/10/smart-meters-arent.html">When Smart Meters Aren’t</a> appeared first on <a rel="nofollow" href="https://blog.dave.org.uk">Davblog</a>.</p>
  607. </div>
  608.    </summary>
  609.    <author>
  610.      <name>Dave Cross</name>
  611.    </author>
  612.    <id>https://blog.dave.org.uk/?p=3645</id>
  613.    <published>2017-10-07T10:09:27Z</published>
  614.    <updated>2017-10-07T10:09:27Z</updated>
  615.    <category term="life"/>
  616.    <category term="british gas"/>
  617.    <category term="idiocy"/>
  618.    <category term="ovo"/>
  619.    <category term="power"/>
  620.    <category term="regulation"/>
  621.    <category term="smart meter"/>
  622.    <category term="supplier"/>
  623.  </entry>
  624.  <entry>
  625.    <title>davblog: Brighton SEO</title>
  626.    <link rel="alternate" href="http://feedproxy.google.com/~r/realdavblog/~3/9UoD7hGktXw/brighton-seo.html" type="text/html"/>
  627.    <content type="html">&lt;p&gt;Last Friday, I was in Brighton for the &lt;a href="http://www.brightonseo.com"&gt;Brighton SEO&lt;/a&gt; conference. It was quite a change for me. I’ve been going to technical conferences for about twenty years or so, but the ones I go to tend to be rather grass-roots affairs like &lt;a href="http://www.yapceurope.org/"&gt;YAPC&lt;/a&gt; or &lt;a href="http://www.opentech.org.uk/"&gt;Opentech&lt;/a&gt;. Even big conferences like &lt;a href="https://fosdem.org/"&gt;FOSDEM&lt;/a&gt; have a very grass-roots feel to them.&lt;/p&gt;
  628. &lt;p&gt;Brighton SEO is different. Brighton SEO is a huge conference and there is obviously a lot of money sloshing around in the SEO industry. I’ve been to big technical conferences like &lt;a href="https://conferences.oreilly.com/oscon"&gt;OSCON&lt;/a&gt;, but tickets for conferences like that are expensive. Brighton SEO is free for most attendees. They must have lots of very generous sponsors.&lt;/p&gt;
  629. &lt;p&gt;The conference took place at the Brighton Centre. The people I was staying with in Brighton asked how much of the centre the conference took up. Turns out the answer was “all of it”. Not bad for a conference that started out as a few friends meeting in a pub just a few years ago.&lt;/p&gt;
  630. &lt;p&gt;The conference day is broken up into four sessions. It was easy enough to choose sessions that sounded useful to me. I’ve only really been looking into SEO since the start of the year and I’m more interested in the technical side of SEO. I don’t have much time for things like content marketing and keyword tracking (although I’m sure they have their place).&lt;/p&gt;
  631. &lt;p&gt;So I started in a session about Javascript and Frameworks. This began with &lt;span class="post-byline"&gt;&lt;span class="author publisher-anchor-color"&gt;Bartosz Góralewicz talking about how well &lt;a href="https://www.slideshare.net/goralewicz/can-google-properly-crawl-and-index-javascript-seo-experiments-results-and-findings"&gt;Google can crawl and index pages built with various Javascript frameworks&lt;/a&gt;. This tied in well with some work I’m doing with a client whose Angular-based web site is getting terrible Google results. Turns out that while Google can crawl and index Javascript-based sites, the results are patchy and very much depend on which framework you use. As I told my client, you need a web site that returns HTML containing real content. You can’t rely on Google to see your AJAX-loaded content.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
  632. &lt;p&gt;This was followed by Emily Grossman talking about &lt;a href="https://www.slideshare.net/MobileMoxie/introduction-to-pwas-new-js-frameworks-for-mobile-79805928"&gt;Progressive Web Apps&lt;/a&gt; – which are basically web sites bundled up to look like smartphone apps. I plan to try this out with a couple of my sites soon.&lt;/p&gt;
  633. &lt;p&gt;The final talk in this session was David Lockie on &lt;a href="https://www.slideshare.net/pragmaticagency/david-lockie-using-open-source-software-to-speed-up-your-roadmap-brightonseo-2017"&gt;Using Open Source Software to Speed Up Your Roadmap&lt;/a&gt;. I’ve used pretty much nothing but open source software for the last thirty years so I needed no convincing that he was advocating a good approach.&lt;/p&gt;
  634. &lt;p&gt;A quick coffee break and then the second session started. I chose a session on Onsite SEO. I was amused to see that even after only eight months of working on SEO, I could pick a session that was too basic for me.&lt;/p&gt;
  635. &lt;p&gt;The session started with Chloé Bodard on &lt;span class="j-title-breadcrumb"&gt;&lt;a href="https://www.slideshare.net/chloebodard/brightonseo-2017-seo-quick-wins-from-a-technical-check"&gt;SEO quick wins from a technical check&lt;/a&gt;. This was interesting because it’s close to a service that I’m thinking of offering to clients. But I learned very little.&lt;/span&gt;&lt;/p&gt;
  636. &lt;p&gt;Chloé was followed by Sébastien Monnier with a talk entitled &lt;span class="j-title-breadcrumb"&gt;&lt;a href="https://www.slideshare.net/woptimoslides/how-google-tag-manager-can-save-your-seo-talk-for-brighton-seo-2017"&gt;How Google Tag Manager Can Save Your SEO&lt;/a&gt;. Earlier this year I was involved in discussions where a client was talking about using Google Tag Manager. Another developer and I managed to persuade them that it was a bad idea as GTM inserts data into the page using Javascript and the right approach was to ensure that the correct data was inserted into the page as it was first built. It was gratifying to hear Sébastien (who is a former Google employee) say that (and I’m paraphrasing) “GTM is really a tool for SEOs to work around bad developers”.&lt;/span&gt;&lt;/p&gt;
  637. &lt;p&gt;The final talk in the session was Aysun Akarsu and &lt;a href="https://www.slideshare.net/searchdatalogy/on-the-road-to-https-everywhere"&gt;On the Road to HTTPS Worldwide&lt;/a&gt;. This was a good talk, but it would have been far more useful to me &lt;em&gt;before&lt;/em&gt; we moved ZPG’s three major web sites to https earlier this year.&lt;/p&gt;
  638. &lt;p&gt;It was then lunch and with some ZPG colleagues I wandered off to sample some of Brighton’s excellent food.&lt;/p&gt;
  639. &lt;p&gt;For the first session in the afternoon, I chose three talks on Technical SEO. We started with Peter Nikolow with &lt;a href="https://www.slideshare.net/mobilio/quick-and-dirty-serverside-tweaks-to-improve-your-seo-brighton-seo-september-2017"&gt;Quick and Dirty Server-Side Hacks to Improve Your SEO&lt;/a&gt;. To be honest, I think Peter misjudged his audience. I was following the conference hashtag on Twitter and there were a lot of people saying that his talk was going over their head. It didn’t go over my head, but I thought that some of his server-side knowledge looked a little dated.&lt;/p&gt;
  640. &lt;p&gt;Then there was Dominic Woodman with a talk entitled &lt;a href="https://www.slideshare.net/DominicWoodman/matching-keywords-to-pages-information-architecture/" target="_blank" rel="noopener"&gt;Advanced Site Architecture – Testing architecture &amp; keyword/page groupings&lt;/a&gt;. There was a lot of good stuff in this talk and I need to go back over the slides in a lot more detail.&lt;/p&gt;
  641. &lt;p&gt;The session ended with Dawn Anderson talking about &lt;a href="https://www.slideshare.net/DawnFitton/technical-seo-generational-cruft-in-seo-there-is-never-a-new-site-when-theres-history-brighton-seo-concise-deck" target="_blank" rel="noopener"&gt;Generational Cruft in SEO – There is Never a ‘New Site’ When There’s History&lt;/a&gt;. A lot of this talk rang very true for me. In fact just the week before, I had been configuring a web site to return 410 responses when Google and Bing came looking for XML sitemaps that had been switched off two years ago.&lt;/p&gt;
  642. &lt;p&gt;For the fourth and final session, I chose the talks on Crawl and Indexation. This session began with Chris Green giving a talk called &lt;a href="https://www.slideshare.net/chr156r33n/robots-txt-meta-x-the-snog-marry-avoid-of-the-web-crawling-world-brighton-seo-sep-2017" target="_blank" rel="noopener"&gt;Robots: X, Meta &amp; TXT – The Snog, Marry &amp; Avoid of the Web Crawling World&lt;/a&gt;. The title was slightly cringe-making, but there was some good content about using the right tools to ensure that pages you don’t want crawled don’t end up in Google’s index.&lt;/p&gt;
  643. &lt;p&gt;I think I wass getting tired by this point. I confess that I don’t remember much about &lt;span class="st"&gt;François&lt;/span&gt; Goube’s &lt;a href="https://www.slideshare.net/OnCrawl/how-to-optimize-googles-crawl-budget-brightonseo-2017"&gt;How to Optimise Your Crawl Budget&lt;/a&gt;. I’m sure it was full of good stuff.&lt;/p&gt;
  644. &lt;p&gt;There was no chance of dozing off during Cindy Krum’s closing talk &lt;a href="https://www.slideshare.net/MobileMoxie/the-truth-about-mobilefirst-indexing-mozcon-2017"&gt;Understanding the Impact of Mobile-First Indexing&lt;/a&gt; (the link goes to the slides for a slightly older version of the talk). This was a real wake-up call about how Google’s indexing will change over the next few years.&lt;/p&gt;
  645. &lt;p&gt;I had a great time at my first Brighton SEO. I wonder how much of that is down to the fact that for probably the first time this millennium I was at a conference and not giving a talk. But I’m already thinking about a talk for the next Brighton SEO conference.&lt;/p&gt;
  646. &lt;p&gt;Many thanks to all of the organisers and speakers. I will be back.&lt;/p&gt;
  647. &lt;p&gt;The post &lt;a rel="nofollow" href="https://blog.dave.org.uk/2017/09/brighton-seo.html"&gt;Brighton SEO&lt;/a&gt; appeared first on &lt;a rel="nofollow" href="https://blog.dave.org.uk"&gt;Davblog&lt;/a&gt;.&lt;/p&gt;
  648. &lt;img src="http://feeds.feedburner.com/~r/realdavblog/~4/9UoD7hGktXw" height="1" width="1" alt=""/&gt;</content>
  649.    <summary type="xhtml">
  650.      <div xmlns="http://www.w3.org/1999/xhtml"><p>Last Friday, I was in Brighton for the Brighton SEO conference. It was quite a change for me. I’ve been going to technical conferences for about twenty years or so, but the ones I go to tend to be rather grass-roots affairs like YAPC or Opentech. Even big conferences like FOSDEM have a very grass-roots … </p>
  651. <p class="link-more"><a href="https://blog.dave.org.uk/2017/09/brighton-seo.html" class="more-link">Continue reading<span class="screen-reader-text"> "Brighton SEO"</span></a></p>
  652. <p>The post <a rel="nofollow" href="https://blog.dave.org.uk/2017/09/brighton-seo.html">Brighton SEO</a> appeared first on <a rel="nofollow" href="https://blog.dave.org.uk">Davblog</a>.</p>
  653. </div>
  654.    </summary>
  655.    <author>
  656.      <name>Dave Cross</name>
  657.    </author>
  658.    <id>https://blog.dave.org.uk/?p=3641</id>
  659.    <published>2017-09-24T10:07:16Z</published>
  660.    <updated>2017-09-24T10:07:16Z</updated>
  661.    <category term="tech"/>
  662.    <category term="brightonseo"/>
  663.    <category term="conference"/>
  664.    <category term="seo"/>
  665.  </entry>
  666.  <entry>
  667.    <title>davblog: Mail Rail Map</title>
  668.    <link rel="alternate" href="http://feedproxy.google.com/~r/realdavblog/~3/vJjTH7gjWUY/mail-rail-map.html" type="text/html"/>
  669.    <content type="html">&lt;p&gt;If you read &lt;a href="//blog.dave.org.uk/2017/09/riding-mail-rail.html"&gt;yesterday’s post about my Mail Rail trip&lt;/a&gt;, you’ll remember that my slight quibble with the experience was that there weren’t any maps showing the route that the tour takes.&lt;/p&gt;
  670. &lt;p&gt;Well, I’ve found one. And I think it explains why they don’t shout about the route.&lt;/p&gt;
  671. &lt;p&gt;I was Googling for any maps of the whole Mail Rail system when I came across &lt;a href="https://www.londonreconnections.com/2013/reopening-londons-mail-rail/"&gt;this blog post from 2013&lt;/a&gt; where John Bull examined the documents that made up the planning request that the British Postal Museum and Archive had submitted to Islington Council. For real document buffs, the blog post included a link to &lt;a href="http://planning.islington.gov.uk/Northgate/PlanningExplorer/Generic/StdDetails.aspx?PT=Planning%20Applications%20On-Line&amp;TYPE=PL/PlanningPK.xml&amp;PARAM0=359011&amp;XSLT=/Northgate/PlanningExplorer/SiteFiles/Skins/Islington/xslt/PL/PLDetails.xslt&amp;FT=Planning%20Application%20Details&amp;PUBLIC=Y&amp;XMLSIDE=/Northgate/PlanningExplorer/SiteFiles/Skins/Islington/Menus/PL.xml&amp;DAURI=PLANNING"&gt;the original planning request&lt;/a&gt;.&lt;/p&gt;
  672. &lt;p&gt;But, for me, the interesting part is the diagram I’ve included at the top of this post. It’s a map of the intended route. And it ties in well with the tour I took on Saturday, so I’m going to assume there were no changes in the four years between the planning request and the exhibit opening.&lt;/p&gt;
  673. &lt;p&gt;The Mail Rail exhibit is the coloured sections. The Postal Museum is on the other side of the road in the Calthorpe House. The bit in green is the entrance hall and gift shop and the blue bit is where you queue and board the train.&lt;/p&gt;
  674. &lt;p&gt;And the pink shows the route that the train takes. You can see it doesn’t go very far. In fact, it doesn’t make it out of the Mount Pleasant complex. It goes from the depot, takes a sharp turn to the right and pulls into the south-east Mount Pleasant platform. That’s where you see the first multi-media presentation. Once it pulls out of that station, the train comes off of the main tracks and takes a maintenance loop which brings it back into the same station but on the north-west platform where it stops for the second multi-media presentation. After that, it returns to the depot where the passengers alight.&lt;/p&gt;
  675. &lt;p&gt;So, all-in-all, you don’t get to see much of the system at all. I knew that you wouldn’t go far, but I’m a little surprised that you don’t get any further than Mount Pleasant station. And that, I expect, is why they don’t publicise the route.&lt;/p&gt;
  676. &lt;p&gt;To be clear, I still think it’s well worth a visit. And it’s great to see such an interesting part of London’s communication infrastructure open to the public.&lt;/p&gt;
  677. &lt;p&gt;But I really hope that in the future, more of the system can be opened up – even if it’s just for occasional trips for enthusiasts. I know I’d be first in line for a ticket.&lt;/p&gt;
  678. &lt;p&gt;The post &lt;a rel="nofollow" href="https://blog.dave.org.uk/2017/09/mail-rail-map.html"&gt;Mail Rail Map&lt;/a&gt; appeared first on &lt;a rel="nofollow" href="https://blog.dave.org.uk"&gt;Davblog&lt;/a&gt;.&lt;/p&gt;
  679. &lt;img src="http://feeds.feedburner.com/~r/realdavblog/~4/vJjTH7gjWUY" height="1" width="1" alt=""/&gt;</content>
  680.    <summary type="xhtml">
  681.      <div xmlns="http://www.w3.org/1999/xhtml"><p>If you read yesterday’s post about my Mail Rail trip, you’ll remember that my slight quibble with the experience was that there weren’t any maps showing the route that the tour takes. Well, I’ve found one. And I think it explains why they don’t shout about the route. I was Googling for any maps of … </p>
  682. <p class="link-more"><a href="https://blog.dave.org.uk/2017/09/mail-rail-map.html" class="more-link">Continue reading<span class="screen-reader-text"> "Mail Rail Map"</span></a></p>
  683. <p>The post <a rel="nofollow" href="https://blog.dave.org.uk/2017/09/mail-rail-map.html">Mail Rail Map</a> appeared first on <a rel="nofollow" href="https://blog.dave.org.uk">Davblog</a>.</p>
  684. </div>
  685.    </summary>
  686.    <author>
  687.      <name>Dave Cross</name>
  688.    </author>
  689.    <id>https://blog.dave.org.uk/?p=3632</id>
  690.    <published>2017-09-11T12:17:11Z</published>
  691.    <updated>2017-09-11T12:17:11Z</updated>
  692.    <category term="london"/>
  693.    <category term="history"/>
  694.    <category term="mail rail"/>
  695.    <category term="post"/>
  696.    <category term="postal museum"/>
  697.  </entry>
  698.  <entry>
  699.    <title>davblog: Riding the Mail Rail</title>
  700.    <link rel="alternate" href="http://feedproxy.google.com/~r/realdavblog/~3/aouiDR-8UHM/riding-mail-rail.html" type="text/html"/>
  701.    <content type="html">&lt;p&gt;I rode the Mail Rail yesterday. It was very exciting. More about that in a minute. Before that, I went to the &lt;a href="https://www.postalmuseum.org/"&gt;Postal Museum&lt;/a&gt;.&lt;/p&gt;
  702. &lt;p&gt;I’ve often thought that the UK needed a museum about the Post Office. And the new (well, newish – it’s been open a couple of months) Postal Museum is a really good start.&lt;/p&gt;
  703. &lt;p&gt;Most of the museum is a pretty standard chronological look at the postal service in the UK. There are exhibits telling the story of the service from its earliest incarnation five hundred years ago. It’s interesting and the displays are well-designed but I couldn’t help thinking it was all a bit simplified. There were many places where I would have welcomed a deeper investigation. Mind you, I find myself thinking that in many modern museums, so perhaps the problem is with me.&lt;/p&gt;
  704. &lt;p&gt;Towards the end of the museum is a small cinema area where they show various short films associated with the Post Office (yes, this includes &lt;a href="https://www.youtube.com/watch?v=S7SD6qt0EFI"&gt;&lt;em&gt;Night Mail&lt;/em&gt;&lt;/a&gt;). I could have sat there watching all of them – but I didn’ t have the time. And I think they missed a trick by not selling a DVD of the films in the gift shop.&lt;/p&gt;
  705. &lt;p&gt;The Postal Museum is well worth a visit. It’s not as big as I thought it would be. We went round it all in about 45 minutes.&lt;/p&gt;
  706. &lt;p&gt;But the reason I left it a couple a months to visit the Postal Museum was because it was only this weekend that the other nearby attraction, the &lt;a href="https://en.wikipedia.org/wiki/London_Post_Office_Railway"&gt;Mail Rail&lt;/a&gt;, finally opened to the public.&lt;/p&gt;
  707. &lt;p&gt;The Mail Rail is an underground railway system which, between 1927 and 2003 was used to transport post around London. I remember hearing about it soon after I first moved to London and I’ve been fascinated by it ever since.&lt;/p&gt;
  708. &lt;p&gt;And last week it opened as a visitor attraction. New carriages have been installed which are (only just) more comfortable for people to sit in and you can take a 20 minute guided tour of the line. Well, it’s 20 minutes if you include the time the train is sitting in the platform as you all board.&lt;/p&gt;
  709. &lt;p&gt;I enjoyed the ride. To be honest, I would have been happy just riding around the tunnels for 20 minutes, but there are a couple of points where you stop and are shown a multi-media presentation about the system and the postal service. A lot of time and money has been spent on them and they were really enjoyable (if not particularly informative).&lt;/p&gt;
  710. &lt;p&gt;As you leave the platform at the end of your ride, you pass though an interesting exhibition on the history of the system.&lt;/p&gt;
  711. &lt;p&gt;If I had one suggestion for improvement, I would like to have seen a map of the system with the bits that the tour covers marked. I suspect that you don’t actually get out of the bits of the system under Mount Pleasant sorting office. [&lt;strong&gt;Update:&lt;/strong&gt; I found a map. &lt;a href="https://blog.dave.org.uk/2017/09/mail-rail-map.html"&gt;See here for details&lt;/a&gt;.]&lt;/p&gt;
  712. &lt;p&gt;I recommend a visit. I’ll be returning at some point in the future to see it again.&lt;/p&gt;
  713. &lt;p&gt;Here’s a video I took of my tour.&lt;/p&gt;
  714. &lt;p&gt;&lt;iframe class='youtube-player' type='text/html' width='525' height='326' src='https://www.youtube.com/embed/963WLJ4Vm2Y?version=3&amp;rel=1&amp;fs=1&amp;autohide=2&amp;showsearch=0&amp;showinfo=1&amp;iv_load_policy=1&amp;wmode=transparent' allowfullscreen='true' style='border:0;'&gt;&lt;/iframe&gt;&lt;/p&gt;
  715. &lt;p&gt;The post &lt;a rel="nofollow" href="https://blog.dave.org.uk/2017/09/riding-mail-rail.html"&gt;Riding the Mail Rail&lt;/a&gt; appeared first on &lt;a rel="nofollow" href="https://blog.dave.org.uk"&gt;Davblog&lt;/a&gt;.&lt;/p&gt;
  716. &lt;img src="http://feeds.feedburner.com/~r/realdavblog/~4/aouiDR-8UHM" height="1" width="1" alt=""/&gt;</content>
  717.    <summary type="xhtml">
  718.      <div xmlns="http://www.w3.org/1999/xhtml"><p>I rode the Mail Rail yesterday. It was very exciting. More about that in a minute. Before that, I went to the Postal Museum. I’ve often thought that the UK needed a museum about the Post Office. And the new (well, newish – it’s been open a couple of months) Postal Museum is a really … </p>
  719. <p class="link-more"><a href="https://blog.dave.org.uk/2017/09/riding-mail-rail.html" class="more-link">Continue reading<span class="screen-reader-text"> "Riding the Mail Rail"</span></a></p>
  720. <p>The post <a rel="nofollow" href="https://blog.dave.org.uk/2017/09/riding-mail-rail.html">Riding the Mail Rail</a> appeared first on <a rel="nofollow" href="https://blog.dave.org.uk">Davblog</a>.</p>
  721. </div>
  722.    </summary>
  723.    <author>
  724.      <name>Dave Cross</name>
  725.    </author>
  726.    <id>https://blog.dave.org.uk/?p=3629</id>
  727.    <published>2017-09-10T09:07:50Z</published>
  728.    <updated>2017-09-10T09:07:50Z</updated>
  729.    <category term="london"/>
  730.    <category term="history"/>
  731.    <category term="mail rail"/>
  732.    <category term="post"/>
  733.    <category term="postal museum"/>
  734.  </entry>
  735.  <entry>
  736.    <title>cpan: DAVECROSS has released SVG-TrafficLight-0.1.3</title>
  737.    <link rel="alternate" href="https://metacpan.org/release/DAVECROSS/SVG-TrafficLight-0.1.3" type="text/html"/>
  738.    <content type="xhtml">
  739.      <div xmlns="http://www.w3.org/1999/xhtml"> </div>
  740.    </content>
  741.    <summary type="xhtml">
  742.      <div xmlns="http://www.w3.org/1999/xhtml">Perl extension to produce SVG diagrams of traffic lights.</div>
  743.    </summary>
  744.    <author>
  745.      <name>DAVECROSS</name>
  746.    </author>
  747.    <id>https://metacpan.org/release/DAVECROSS/SVG-TrafficLight-0.1.3</id>
  748.    <published>2017-09-06T12:07:43</published>
  749.    <updated>2017-09-06T12:07:43</updated>
  750.  </entry>
  751.  <entry>
  752.    <title>cpan: DAVECROSS has released SVG-Timeline-0.0.7</title>
  753.    <link rel="alternate" href="https://metacpan.org/release/DAVECROSS/SVG-Timeline-0.0.7" type="text/html"/>
  754.    <content type="xhtml">
  755.      <div xmlns="http://www.w3.org/1999/xhtml"> </div>
  756.    </content>
  757.    <summary type="xhtml">
  758.      <div xmlns="http://www.w3.org/1999/xhtml">Program to draw an SVG timeline diagram from events defined in a file</div>
  759.    </summary>
  760.    <author>
  761.      <name>DAVECROSS</name>
  762.    </author>
  763.    <id>https://metacpan.org/release/DAVECROSS/SVG-Timeline-0.0.7</id>
  764.    <published>2017-09-06T07:58:59</published>
  765.    <updated>2017-09-06T07:58:59</updated>
  766.  </entry>
  767. </feed>
  768.  
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda