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>dave@dave.org.uk</email>
  9.  </author>
  10.  <updated>2014-07-28T06:03:23Z</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/493505111294246913" type="text/html"/>
  16.    <content type="xhtml">
  17.      <div xmlns="http://www.w3.org/1999/xhtml">Actually feeling a little cooler for the first time for weeks.</div>
  18.    </content>
  19.    <updated>2014-07-27T21:16:02Z</updated>
  20.  <title>twitter: Actually feeling a little cooler for the first time for weeks.</title></entry>
  21.  <entry>
  22.    <title>last.fm: Kate Bush – Eat the Music</title>
  23.    <link rel="alternate" href="http://www.last.fm/music/Kate+Bush/_/Eat+the+Music" type="text/html"/>
  24.    <content type="xhtml">
  25.      <div xmlns="http://www.w3.org/1999/xhtml">http://www.last.fm/music/Kate+Bush</div>
  26.    </content>
  27.    <id>http://www.last.fm/user/davorg#1406475888</id>
  28.    <published>2014-07-27T15:44:48Z</published>
  29.    <updated>2014-07-27T15:44:48Z</updated>
  30.  </entry>
  31.  <entry>
  32.    <title>last.fm: Lana Del Rey – Young and Beautiful</title>
  33.    <link rel="alternate" href="http://www.last.fm/music/Lana+Del+Rey/_/Young+and+Beautiful" type="text/html"/>
  34.    <content type="xhtml">
  35.      <div xmlns="http://www.w3.org/1999/xhtml">http://www.last.fm/music/Lana+Del+Rey</div>
  36.    </content>
  37.    <id>http://www.last.fm/user/davorg#1406475652</id>
  38.    <published>2014-07-27T15:40:52Z</published>
  39.    <updated>2014-07-27T15:40:52Z</updated>
  40.  </entry>
  41.  <entry>
  42.    <title>last.fm: Kate Bush – Room for the Life</title>
  43.    <link rel="alternate" href="http://www.last.fm/music/Kate+Bush/_/Room+for+the+Life" type="text/html"/>
  44.    <content type="xhtml">
  45.      <div xmlns="http://www.w3.org/1999/xhtml">http://www.last.fm/music/Kate+Bush</div>
  46.    </content>
  47.    <id>http://www.last.fm/user/davorg#1406475385</id>
  48.    <published>2014-07-27T15:36:25Z</published>
  49.    <updated>2014-07-27T15:36:25Z</updated>
  50.  </entry>
  51.  <entry>
  52.    <title>last.fm: Kirsty MacColl – Walking Down Madison</title>
  53.    <link rel="alternate" href="http://www.last.fm/music/Kirsty+MacColl/_/Walking+Down+Madison" type="text/html"/>
  54.    <content type="xhtml">
  55.      <div xmlns="http://www.w3.org/1999/xhtml">http://www.last.fm/music/Kirsty+MacColl</div>
  56.    </content>
  57.    <id>http://www.last.fm/user/davorg#1406475127</id>
  58.    <published>2014-07-27T15:32:07Z</published>
  59.    <updated>2014-07-27T15:32:07Z</updated>
  60.  </entry>
  61.  <entry>
  62.    <title>last.fm: Levellers – Bozos</title>
  63.    <link rel="alternate" href="http://www.last.fm/music/Levellers/_/Bozos" type="text/html"/>
  64.    <content type="xhtml">
  65.      <div xmlns="http://www.w3.org/1999/xhtml">http://www.last.fm/music/Levellers</div>
  66.    </content>
  67.    <id>http://www.last.fm/user/davorg#1406474906</id>
  68.    <published>2014-07-27T15:28:26Z</published>
  69.    <updated>2014-07-27T15:28:26Z</updated>
  70.  </entry>
  71.  <entry>
  72.    
  73.    <link rel="alternate" href="https://twitter.com/davorg/status/493411517040443392" type="text/html"/>
  74.    <content type="xhtml">
  75.      <div xmlns="http://www.w3.org/1999/xhtml">My Top 3 #lastfm Artists: The Beautiful South (22), Frankie Goes to Hollywood (15) &amp; The Pop Group (11) http://t.co/GkcjAPjPFZ</div>
  76.    </content>
  77.    <updated>2014-07-27T15:04:07Z</updated>
  78.  <title>twitter: My Top 3 #lastfm Artists: The Beautiful South (22), Frankie Goes to Hollywood (15) &amp;amp; The Pop Group (11) http://t.co/GkcjAPjPFZ</title></entry>
  79.  <entry>
  80.    
  81.    <link rel="alternate" href="https://twitter.com/davorg/status/493386565377605633" type="text/html"/>
  82.    <content type="xhtml">
  83.      <div xmlns="http://www.w3.org/1999/xhtml">New Day seem determined to resurrect an credit card account that was cancelled two years ago, but which they've bought from Santander.</div>
  84.    </content>
  85.    <updated>2014-07-27T13:24:58Z</updated>
  86.  <title>twitter: New Day seem determined to resurrect an credit card account that was cancelled two years ago, but which they've bought from Santander.</title></entry>
  87.  <entry>
  88.    
  89.    <link rel="alternate" href="https://twitter.com/davorg/status/493386346149740544" type="text/html"/>
  90.    <content type="xhtml">
  91.      <div xmlns="http://www.w3.org/1999/xhtml">Hate it when companies call you to discuss business on a Sunday afternoon. In this case it was New Day the Credit card company.</div>
  92.    </content>
  93.    <updated>2014-07-27T13:24:06Z</updated>
  94.  <title>twitter: Hate it when companies call you to discuss business on a Sunday afternoon. In this case it was New Day the Credit card company.</title></entry>
  95.  <entry>
  96.    
  97.    <link rel="alternate" href="https://twitter.com/davorg/status/493280242648485890" type="text/html"/>
  98.    <content type="xhtml">
  99.      <div xmlns="http://www.w3.org/1999/xhtml">RT @bengoldacre: Don't like the science? Sack the scientist. @Greenpeace show they're as bad as the toddlers who sacked @ProfDavidNutt http…</div>
  100.    </content>
  101.    <updated>2014-07-27T06:22:29Z</updated>
  102.  <title>twitter: RT @bengoldacre: Don't like the science? Sack the scientist. @Greenpeace show they're as bad as the toddlers who sacked @ProfDavidNutt http…</title></entry>
  103.  <entry>
  104.    <title>perl hacks: Github, Travis-CI and Perl</title>
  105.    <link rel="alternate" href="http://perlhacks.com/2014/07/github-travis-ci-perl/" type="text/html"/>
  106.    <content type="xhtml">
  107.      <div xmlns="http://www.w3.org/1999/xhtml"><p>Last night we held a London Perl Mongers Technical Meeting. It was organised by <a href="https://twitter.com/virtualsue">Sue Spenc</a>e and the <a href="http://www.conwayhall.org.uk/">venue</a> was sponsored by <a href="https://twitter.com/PerlRick">Rick Deller</a> of <a href="http://www.eligo.co.uk/">Eligo</a>.</p>
  108. <p>Much fun was had and much knowledge was imparted. <a href="https://twitter.com/kaokun">Alex Balhatchet</a> spoke about <a href="https://metacpan.org/pod/Test::Kit">Test::Kit</a>. <a href="https://twitter.com/geekuni">Andrew Solomon</a> talked about training people in Perl. <a href="https://metacpan.org/author/DOMM">Thomas Klausner </a>introduced <a href="https://metacpan.org/release/OX">OX</a> and <a href="https://angularjs.org/">AngularJS</a>. And Mike Francis talked about using <a href="https://metacpan.org/pod/Web::Simple">Web::Simple</a> and <a href="https://metacpan.org/pod/Web::Machine">Web::Machine</a> to build a REST interface to a database – only to be told that Tim Bunce had just <a href="https://metacpan.org/release/WebAPI-DBIC">released a module</a> that solved all of his problems.</p>
  109. <p>Oh, and I wittered on a bit about using Perl with <a href="http://github.com/">Github</a> and <a href="http://travis-ci.org/">Travis-CI</a>. The slides are below.</p>
  110. <p><iframe style="border: 1px solid #CCC; border-width: 1px; margin-bottom: 5px; max-width: 100%;" src="//www.slideshare.net/slideshow/embed_code/37351718" width="427" height="356" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" allowfullscreen="allowfullscreen"> </iframe></p>
  111. <div style="margin-bottom: 5px;"><strong> <a title="Github, Travis-CI and Perl" href="https://www.slideshare.net/davorg/github-travisci-and-perl" target="_blank">Github, Travis-CI and Perl</a> </strong> from <strong><a href="http://www.slideshare.net/davorg" target="_blank">Dave Cross</a></strong></div>
  112. <p>Thanks to everyone for organising, speaking or just coming along.</p>
  113. <p>The post <a rel="nofollow" href="http://perlhacks.com/2014/07/github-travis-ci-perl/">Github, Travis-CI and Perl</a> appeared first on <a rel="nofollow" href="http://perlhacks.com">Perl Hacks</a>.</p>
  114. </div>
  115.    </content>
  116.    <summary type="xhtml">
  117.      <div xmlns="http://www.w3.org/1999/xhtml"><p>Last night we held a London Perl Mongers Technical Meeting. It was organised by Sue Spence and the venue was sponsored by Rick Deller of Eligo. Much fun was had and much knowledge was imparted. Alex Balhatchet spoke about Test::Kit. Andrew Solomon talked about training people in Perl. Thomas Klausner introduced OX and AngularJS. And […]</p>
  118. <p>The post <a rel="nofollow" href="http://perlhacks.com/2014/07/github-travis-ci-perl/">Github, Travis-CI and Perl</a> appeared first on <a rel="nofollow" href="http://perlhacks.com">Perl Hacks</a>.</p>
  119. </div>
  120.    </summary>
  121.    <author>
  122.      <name>Dave Cross</name>
  123.    </author>
  124.    <id>http://perlhacks.com/?p=935</id>
  125.    <published>2014-07-25T16:14:39Z</published>
  126.    <updated>2014-07-25T16:14:39Z</updated>
  127.    <category term="Speaking"/>
  128.    <category term="continuous integration"/>
  129.    <category term="github"/>
  130.    <category term="london"/>
  131.    <category term="london.pm"/>
  132.    <category term="techmeet"/>
  133.    <category term="travis-ci"/>
  134.  </entry>
  135.  <entry>
  136.    <title>perl hacks: London Perl Workshop</title>
  137.    <link rel="alternate" href="http://perlhacks.com/2014/07/london-perl-workshop-3/" type="text/html"/>
  138.    <content type="xhtml">
  139.      <div xmlns="http://www.w3.org/1999/xhtml"><p>The London Perl Workshop 2014 has been announced. It will be at the University of Westminster (the usual location) on Saturday 8th November. That’s a few weeks earlier in the year than it usually is.</p>
  140. <p>The theme for this year is “The Internet of Things”.</p>
  141. <p>You can find out more about the workshop, register and propose talks <a href="http://act.yapc.eu/lpw2014/">at the web site</a>. Hope to see many of you there.</p>
  142. <p>Many thanks (as always) to <a href="https://twitter.com/shadowcat_mdk">Mark Keating</a> for organising the workshop.</p>
  143. <p>The post <a rel="nofollow" href="http://perlhacks.com/2014/07/london-perl-workshop-3/">London Perl Workshop</a> appeared first on <a rel="nofollow" href="http://perlhacks.com">Perl Hacks</a>.</p>
  144. </div>
  145.    </content>
  146.    <summary type="xhtml">
  147.      <div xmlns="http://www.w3.org/1999/xhtml"><p>The London Perl Workshop 2014 has been announced. It will be at the University of Westminster (the usual location) on Saturday 8th November. That’s a few weeks earlier in the year than it usually is. The theme for this year is “The Internet of Things”. You can find out more about the workshop, register and […]</p>
  148. <p>The post <a rel="nofollow" href="http://perlhacks.com/2014/07/london-perl-workshop-3/">London Perl Workshop</a> appeared first on <a rel="nofollow" href="http://perlhacks.com">Perl Hacks</a>.</p>
  149. </div>
  150.    </summary>
  151.    <author>
  152.      <name>Dave Cross</name>
  153.    </author>
  154.    <id>http://perlhacks.com/?p=933</id>
  155.    <published>2014-07-25T15:59:15Z</published>
  156.    <updated>2014-07-25T15:59:15Z</updated>
  157.    <category term="Conferences"/>
  158.    <category term="london"/>
  159.    <category term="london perl workshop"/>
  160.    <category term="london.pm"/>
  161.  </entry>
  162.  <entry>
  163.    <title>slideshare: Github, Travis-CI and Perl</title>
  164.    <link rel="alternate" href="http://www.slideshare.net/davorg/github-travisci-and-perl" type="text/html"/>
  165.    <content type="html">
  166.        &lt;img src="//cdn.slidesharecdn.com/ss_thumbnails/travis-ci-140725055617-phpapp02-thumbnail-2.jpg?cb=1406285843" alt ="" style="border:1px solid #C3E6D8;float:right;" /&gt;&lt;br&gt; A quick introduction to using Github and Travis-CI to test Perl projects
  167.      </content>
  168.    <summary type="html">
  169.        &lt;img src="//cdn.slidesharecdn.com/ss_thumbnails/travis-ci-140725055617-phpapp02-thumbnail-2.jpg?cb=1406285843" alt ="" style="border:1px solid #C3E6D8;float:right;" /&gt;&lt;br&gt; A quick introduction to using Github and Travis-CI to test Perl projects
  170.      </summary>
  171.    <author>
  172.      <name>davorg@slideshare.net(davorg)</name>
  173.    </author>
  174.    <id>http://www.slideshare.net/davorg/github-travisci-and-perl</id>
  175.    <published>2014-07-25T10:56:17Z</published>
  176.    <updated>2014-07-25T10:56:17Z</updated>
  177.  </entry>
  178.  <entry xmlns:media="http://search.yahoo.com/mrss/">
  179.    <id>tag:github.com,2008:PushEvent/2201629426</id>
  180.    <published>2014-07-24T14:46:43Z</published>
  181.    <updated>2014-07-24T14:46:43Z</updated>
  182.    <link type="text/html" rel="alternate" href="https://github.com/davorg/hipsterperl/compare/60cda8139b...2c57660cfc"/>
  183.    
  184.    <author>
  185.      <name>davorg</name>
  186.      <email>dave@perlhacks.com</email>
  187.      <uri>https://github.com/davorg</uri>
  188.    </author>
  189.    <media:thumbnail height="30" width="30" url="https://avatars3.githubusercontent.com/u/24642?s=30"/>
  190.    <content type="html">&lt;!-- push --&gt;
  191. &lt;span class="mega-octicon octicon-git-commit"&gt;&lt;/span&gt;
  192.  
  193. &lt;div class="time"&gt;
  194.  &lt;time datetime="2014-07-24T14:46:43Z" is="relative-time"&gt;July 24, 2014&lt;/time&gt;
  195. &lt;/div&gt;
  196.  
  197. &lt;div class="title"&gt;
  198.  &lt;a href="https://github.com/davorg"&gt;davorg&lt;/a&gt; &lt;span&gt;pushed&lt;/span&gt; to &lt;a href="/davorg/hipsterperl/tree/gh-pages"&gt;gh-pages&lt;/a&gt; at &lt;a href="https://github.com/davorg/hipsterperl" class="css-truncate css-truncate-target"&gt;davorg/hipsterperl&lt;/a&gt;
  199. &lt;/div&gt;
  200.  
  201. &lt;div class="details"&gt;
  202.  &lt;a href="https://github.com/davorg"&gt;&lt;img alt="Dave Cross" class="gravatar js-avatar" data-user="24642" height="30" src="https://avatars2.githubusercontent.com/u/24642?s=60" width="30" /&gt;&lt;/a&gt;
  203.  
  204.    &lt;div class="commits pusher-is-only-committer"&gt;
  205.      &lt;ul&gt;
  206.        &lt;li&gt;
  207.          &lt;span title="davorg"&gt;
  208.            &lt;img alt="Dave Cross" class=" js-avatar" data-user="24642" height="16" src="https://avatars3.githubusercontent.com/u/24642?s=32" width="16" /&gt;
  209.          &lt;/span&gt;
  210.          &lt;code&gt;&lt;a href="/davorg/hipsterperl/commit/2c57660cfc91a74cd39766c2b9c7b48b8f14ab08"&gt;2c57660&lt;/a&gt;&lt;/code&gt;
  211.          &lt;div class="message"&gt;
  212.            &lt;blockquote&gt;
  213.              Fixed title
  214.            &lt;/blockquote&gt;
  215.          &lt;/div&gt;
  216.        &lt;/li&gt;
  217.        &lt;li&gt;
  218.          &lt;span title="davorg"&gt;
  219.            &lt;img alt="Dave Cross" class=" js-avatar" data-user="24642" height="16" src="https://avatars3.githubusercontent.com/u/24642?s=32" width="16" /&gt;
  220.          &lt;/span&gt;
  221.          &lt;code&gt;&lt;a href="/davorg/hipsterperl/commit/ddd411f51bec6764676f5205913c0b6cca8d90dc"&gt;ddd411f&lt;/a&gt;&lt;/code&gt;
  222.          &lt;div class="message"&gt;
  223.            &lt;blockquote&gt;
  224.              Removed unwanted backup file.
  225.            &lt;/blockquote&gt;
  226.          &lt;/div&gt;
  227.        &lt;/li&gt;
  228.        &lt;li class="more"&gt;&lt;a href="https://github.com/davorg/hipsterperl/compare/60cda8139b...2c57660cfc"&gt;View comparison for these 2 commits &amp;raquo;&lt;/a&gt;&lt;/li&gt;
  229.      &lt;/ul&gt;
  230.    &lt;/div&gt;
  231. &lt;/div&gt;
  232. </content>
  233.  <title>github: davorg pushed to gh-pages at davorg/hipsterperl</title></entry>
  234.  <entry xmlns:media="http://search.yahoo.com/mrss/">
  235.    <id>tag:github.com,2008:PushEvent/2200210352</id>
  236.    <published>2014-07-23T19:53:33Z</published>
  237.    <updated>2014-07-23T19:53:33Z</updated>
  238.    <link type="text/html" rel="alternate" href="https://github.com/davorg/hipsterperl/compare/a5d11e8c2c...60cda8139b"/>
  239.    
  240.    <author>
  241.      <name>davorg</name>
  242.      <email>dave@perlhacks.com</email>
  243.      <uri>https://github.com/davorg</uri>
  244.    </author>
  245.    <media:thumbnail height="30" width="30" url="https://avatars3.githubusercontent.com/u/24642?s=30"/>
  246.    <content type="html">&lt;!-- push --&gt;
  247. &lt;span class="mega-octicon octicon-git-commit"&gt;&lt;/span&gt;
  248.  
  249. &lt;div class="time"&gt;
  250.  &lt;time datetime="2014-07-23T19:53:33Z" is="relative-time"&gt;July 23, 2014&lt;/time&gt;
  251. &lt;/div&gt;
  252.  
  253. &lt;div class="title"&gt;
  254.  &lt;a href="https://github.com/davorg"&gt;davorg&lt;/a&gt; &lt;span&gt;pushed&lt;/span&gt; to &lt;a href="/davorg/hipsterperl/tree/gh-pages"&gt;gh-pages&lt;/a&gt; at &lt;a href="https://github.com/davorg/hipsterperl" class="css-truncate css-truncate-target"&gt;davorg/hipsterperl&lt;/a&gt;
  255. &lt;/div&gt;
  256.  
  257. &lt;div class="details"&gt;
  258.  &lt;a href="https://github.com/davorg"&gt;&lt;img alt="Dave Cross" class="gravatar js-avatar" data-user="24642" height="30" src="https://avatars2.githubusercontent.com/u/24642?s=60" width="30" /&gt;&lt;/a&gt;
  259.  
  260.    &lt;div class="commits pusher-is-only-committer"&gt;
  261.      &lt;ul&gt;
  262.        &lt;li&gt;
  263.          &lt;span title="davorg"&gt;
  264.            &lt;img alt="Dave Cross" class=" js-avatar" data-user="24642" height="16" src="https://avatars3.githubusercontent.com/u/24642?s=32" width="16" /&gt;
  265.          &lt;/span&gt;
  266.          &lt;code&gt;&lt;a href="/davorg/hipsterperl/commit/60cda8139b03f4148d5934b033c9c08d4ac0be72"&gt;60cda81&lt;/a&gt;&lt;/code&gt;
  267.          &lt;div class="message"&gt;
  268.            &lt;blockquote&gt;
  269.              Changed first background image.
  270.            &lt;/blockquote&gt;
  271.          &lt;/div&gt;
  272.        &lt;/li&gt;
  273.      &lt;/ul&gt;
  274.    &lt;/div&gt;
  275. &lt;/div&gt;
  276. </content>
  277.  <title>github: davorg pushed to gh-pages at davorg/hipsterperl</title></entry>
  278.  <entry xmlns:media="http://search.yahoo.com/mrss/">
  279.    <id>tag:github.com,2008:PushEvent/2200172304</id>
  280.    <published>2014-07-23T19:32:35Z</published>
  281.    <updated>2014-07-23T19:32:35Z</updated>
  282.    <link type="text/html" rel="alternate" href="https://github.com/davorg/hipsterperl/compare/d366015ba0...a5d11e8c2c"/>
  283.    
  284.    <author>
  285.      <name>davorg</name>
  286.      <email>dave@perlhacks.com</email>
  287.      <uri>https://github.com/davorg</uri>
  288.    </author>
  289.    <media:thumbnail height="30" width="30" url="https://avatars3.githubusercontent.com/u/24642?s=30"/>
  290.    <content type="html">&lt;!-- push --&gt;
  291. &lt;span class="mega-octicon octicon-git-commit"&gt;&lt;/span&gt;
  292.  
  293. &lt;div class="time"&gt;
  294.  &lt;time datetime="2014-07-23T19:32:35Z" is="relative-time"&gt;July 23, 2014&lt;/time&gt;
  295. &lt;/div&gt;
  296.  
  297. &lt;div class="title"&gt;
  298.  &lt;a href="https://github.com/davorg"&gt;davorg&lt;/a&gt; &lt;span&gt;pushed&lt;/span&gt; to &lt;a href="/davorg/hipsterperl/tree/gh-pages"&gt;gh-pages&lt;/a&gt; at &lt;a href="https://github.com/davorg/hipsterperl" class="css-truncate css-truncate-target"&gt;davorg/hipsterperl&lt;/a&gt;
  299. &lt;/div&gt;
  300.  
  301. &lt;div class="details"&gt;
  302.  &lt;a href="https://github.com/davorg"&gt;&lt;img alt="Dave Cross" class="gravatar js-avatar" data-user="24642" height="30" src="https://avatars2.githubusercontent.com/u/24642?s=60" width="30" /&gt;&lt;/a&gt;
  303.  
  304.    &lt;div class="commits pusher-is-only-committer"&gt;
  305.      &lt;ul&gt;
  306.        &lt;li&gt;
  307.          &lt;span title="davorg"&gt;
  308.            &lt;img alt="Dave Cross" class=" js-avatar" data-user="24642" height="16" src="https://avatars3.githubusercontent.com/u/24642?s=32" width="16" /&gt;
  309.          &lt;/span&gt;
  310.          &lt;code&gt;&lt;a href="/davorg/hipsterperl/commit/a5d11e8c2c9790d0461194a79d4123a2e747653e"&gt;a5d11e8&lt;/a&gt;&lt;/code&gt;
  311.          &lt;div class="message"&gt;
  312.            &lt;blockquote&gt;
  313.              Added CNAME
  314.            &lt;/blockquote&gt;
  315.          &lt;/div&gt;
  316.        &lt;/li&gt;
  317.      &lt;/ul&gt;
  318.    &lt;/div&gt;
  319. &lt;/div&gt;
  320. </content>
  321.  <title>github: davorg pushed to gh-pages at davorg/hipsterperl</title></entry>
  322.  <entry xmlns:media="http://search.yahoo.com/mrss/">
  323.    <id>tag:github.com,2008:PushEvent/2200160812</id>
  324.    <published>2014-07-23T19:26:07Z</published>
  325.    <updated>2014-07-23T19:26:07Z</updated>
  326.    <link type="text/html" rel="alternate" href="https://github.com/davorg/hipsterperl/compare/2718664d38...d366015ba0"/>
  327.    
  328.    <author>
  329.      <name>davorg</name>
  330.      <email>dave@perlhacks.com</email>
  331.      <uri>https://github.com/davorg</uri>
  332.    </author>
  333.    <media:thumbnail height="30" width="30" url="https://avatars3.githubusercontent.com/u/24642?s=30"/>
  334.    <content type="html">&lt;!-- push --&gt;
  335. &lt;span class="mega-octicon octicon-git-commit"&gt;&lt;/span&gt;
  336.  
  337. &lt;div class="time"&gt;
  338.  &lt;time datetime="2014-07-23T19:26:07Z" is="relative-time"&gt;July 23, 2014&lt;/time&gt;
  339. &lt;/div&gt;
  340.  
  341. &lt;div class="title"&gt;
  342.  &lt;a href="https://github.com/davorg"&gt;davorg&lt;/a&gt; &lt;span&gt;pushed&lt;/span&gt; to &lt;a href="/davorg/hipsterperl/tree/gh-pages"&gt;gh-pages&lt;/a&gt; at &lt;a href="https://github.com/davorg/hipsterperl" class="css-truncate css-truncate-target"&gt;davorg/hipsterperl&lt;/a&gt;
  343. &lt;/div&gt;
  344.  
  345. &lt;div class="details"&gt;
  346.  &lt;a href="https://github.com/davorg"&gt;&lt;img alt="Dave Cross" class="gravatar js-avatar" data-user="24642" height="30" src="https://avatars2.githubusercontent.com/u/24642?s=60" width="30" /&gt;&lt;/a&gt;
  347.  
  348.    &lt;div class="commits pusher-is-only-committer"&gt;
  349.      &lt;ul&gt;
  350.        &lt;li&gt;
  351.          &lt;span title="davorg"&gt;
  352.            &lt;img alt="Dave Cross" class=" js-avatar" data-user="24642" height="16" src="https://avatars3.githubusercontent.com/u/24642?s=32" width="16" /&gt;
  353.          &lt;/span&gt;
  354.          &lt;code&gt;&lt;a href="/davorg/hipsterperl/commit/d366015ba0fc5c70011dc31e98b6156b4524db7b"&gt;d366015&lt;/a&gt;&lt;/code&gt;
  355.          &lt;div class="message"&gt;
  356.            &lt;blockquote&gt;
  357.              Moved stuff around.
  358.            &lt;/blockquote&gt;
  359.          &lt;/div&gt;
  360.        &lt;/li&gt;
  361.      &lt;/ul&gt;
  362.    &lt;/div&gt;
  363. &lt;/div&gt;
  364. </content>
  365.  <title>github: davorg pushed to gh-pages at davorg/hipsterperl</title></entry>
  366.  <entry xmlns:media="http://search.yahoo.com/mrss/">
  367.    <id>tag:github.com,2008:CreateEvent/2200156454</id>
  368.    <published>2014-07-23T19:23:40Z</published>
  369.    <updated>2014-07-23T19:23:40Z</updated>
  370.    <link type="text/html" rel="alternate" href="https://github.com/davorg/hipsterperl/compare/gh-pages"/>
  371.    
  372.    <author>
  373.      <name>davorg</name>
  374.      <email>dave@perlhacks.com</email>
  375.      <uri>https://github.com/davorg</uri>
  376.    </author>
  377.    <media:thumbnail height="30" width="30" url="https://avatars3.githubusercontent.com/u/24642?s=30"/>
  378.    <content type="html">&lt;!-- create --&gt;
  379. &lt;div class="simple"&gt;
  380.  &lt;span class="octicon octicon-git-branch"&gt;&lt;/span&gt;
  381.  
  382.  &lt;div class="title"&gt;
  383.    &lt;a href="https://github.com/davorg"&gt;davorg&lt;/a&gt; &lt;span&gt;created&lt;/span&gt; branch &lt;a href="/davorg/hipsterperl/tree/gh-pages" class="css-truncate css-truncate-target branch-link" title="gh-pages"&gt;&lt;span class="octicon octicon-git-branch"&gt;&lt;/span&gt;gh-pages&lt;/a&gt; at &lt;a href="https://github.com/davorg/hipsterperl" class="css-truncate css-truncate-target"&gt;davorg/hipsterperl&lt;/a&gt;
  384.  &lt;/div&gt;
  385.  
  386.  &lt;div class="time"&gt;
  387.    &lt;time datetime="2014-07-23T19:23:40Z" is="relative-time"&gt;July 23, 2014&lt;/time&gt;
  388.  &lt;/div&gt;
  389. &lt;/div&gt;
  390. </content>
  391.  <title>github: davorg created branch gh-pages at davorg/hipsterperl</title></entry>
  392.  <entry>
  393.    <title>books read: 500 Social Media Marketing Tips: Essential Advice, Hints and Strategy for Business: Facebook, Twitter, Pinterest, Google+, YouTube, Instagram, LinkedIn, and More!</title>
  394.    <link rel="alternate" href="http://www.goodreads.com/review/show/1004356357?utm_medium=api&amp;utm_source=rss" type="text/html"/>
  395.    <content type="xhtml">
  396.      <div xmlns="http://www.w3.org/1999/xhtml">
  397.      
  398.      <a href="http://www.goodreads.com/book/show/17447401-500-social-media-marketing-tips?utm_medium=api&amp;utm_source=rss"><img alt="500 Social Media Marketing Tips: Essential Advice, Hints and Strategy for Business: Facebook, Twitter, Pinterest, Google+, YouTube, Instagram, LinkedIn, and More!" src="http://d.gr-assets.com/books/1361902445s/17447401.jpg"/></a><br/>
  399.                                      author: Andrew Macarthy<br/>
  400.                                      name: David<br/>
  401.                                      average rating: 3.92<br/>
  402.                                      book published: 2013<br/>
  403.                                      rating: 0<br/>
  404.                                      read at: <br/>
  405.                                      date added: 2014/07/23<br/>
  406.                                      shelves: currently-reading<br/>
  407.                                      review: <br/><br/>
  408.                                      
  409.    </div>
  410.    </content>
  411.    <id>http://www.goodreads.com/review/show/1004356357?utm_medium=api&amp;utm_source=rss</id>
  412.    <published>2014-07-23T01:45:32-07:00</published>
  413.    <updated>2014-07-23T01:45:32-07:00</updated>
  414.  </entry>
  415.  <entry>
  416.    <title>davblog: First Direct Update</title>
  417.    <link rel="alternate" href="http://feedproxy.google.com/~r/realdavblog/~3/NJ-sXTgM-yo/first-direct-update.html" type="text/html"/>
  418.    <content type="html">&lt;p&gt;Earlier in the week I talked about my concerns with &lt;a href="http://blog.dave.org.uk/2014/07/first-direct-passwords.html"&gt;First Direct&amp;#8217;s new password policy&lt;/a&gt;. I got an email from them about this, but it really wasn&amp;#8217;t very reassuring.&lt;/p&gt;
  419. &lt;p&gt;But I kept digging. And on Thursday I got a bit more information from &amp;#8220;^GD&amp;#8221; on the &lt;a href="http://twitter.com/firstdirecthelp"&gt;@firstdirecthelp&lt;/a&gt; twitter account. It still doesn&amp;#8217;t answer all of my questions, but I think we&amp;#8217;re a lot closer to the truth. Here&amp;#8217;s what I was told.&lt;/p&gt;
  420. &lt;blockquote class="twitter-tweet" width="550"&gt;&lt;p&gt;&lt;a href="https://twitter.com/davorg"&gt;@davorg&lt;/a&gt; Hi Dave, I can confirm that the password is encrypted. Security and safety will always be a priority for first direct. ^GD&lt;/p&gt;
  421. &lt;p&gt;&amp;mdash; first direct help (@firstdirecthelp) &lt;a href="https://twitter.com/firstdirecthelp/statuses/489774367379697664"&gt;July 17, 2014&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;
  422. &lt;p&gt;&lt;script async src="//platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;&lt;/p&gt;
  423. &lt;p&gt;The obvious question that this raises is why, then, do they limit the length of the passwords. I asked and got this (three-tweet) reply.&lt;/p&gt;
  424. &lt;blockquote class="twitter-tweet" width="550"&gt;&lt;p&gt;&lt;a href="https://twitter.com/davorg"&gt;@davorg&lt;/a&gt; Hi Dave, it was a business decision to have the password length limited to a maximum of 10 characters. (1/3)^GD&lt;/p&gt;
  425. &lt;p&gt;&amp;mdash; first direct help (@firstdirecthelp) &lt;a href="https://twitter.com/firstdirecthelp/statuses/489778601366405121"&gt;July 17, 2014&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;
  426. &lt;p&gt;&lt;script async src="//platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;&lt;/p&gt;
  427. &lt;blockquote class="twitter-tweet" width="550"&gt;&lt;p&gt;&lt;a href="https://twitter.com/davorg"&gt;@davorg&lt;/a&gt; Due to the restrictions within the app the risk from having a short password is minimal. (2/3)^GD&lt;/p&gt;
  428. &lt;p&gt;&amp;mdash; first direct help (@firstdirecthelp) &lt;a href="https://twitter.com/firstdirecthelp/statuses/489778808682074112"&gt;July 17, 2014&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;
  429. &lt;p&gt;&lt;script async src="//platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;&lt;/p&gt;
  430. &lt;blockquote class="twitter-tweet" width="550"&gt;&lt;p&gt;&lt;a href="https://twitter.com/davorg"&gt;@davorg&lt;/a&gt;  We always advise that the password chosen for the Digital Secure Key is unique.(3/3)^GD&lt;/p&gt;
  431. &lt;p&gt;&amp;mdash; first direct help (@firstdirecthelp) &lt;a href="https://twitter.com/firstdirecthelp/statuses/489778882107551744"&gt;July 17, 2014&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;
  432. &lt;p&gt;&lt;script async src="//platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;&lt;/p&gt;
  433. &lt;p&gt;To which, I replied&lt;/p&gt;
  434. &lt;blockquote class="twitter-tweet" width="550"&gt;&lt;p&gt;&lt;a href="https://twitter.com/firstdirecthelp"&gt;@firstdirecthelp&lt;/a&gt; Thanks for the reply. But you&amp;#39;re aware (I assume) that this goes against current security best practice recommendations.&lt;/p&gt;
  435. &lt;p&gt;&amp;mdash; Dave Cross (@davorg) &lt;a href="https://twitter.com/davorg/statuses/489779600109891584"&gt;July 17, 2014&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;
  436. &lt;p&gt;&lt;script async src="//platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;&lt;/p&gt;
  437. &lt;p&gt;And got the response&lt;/p&gt;
  438. &lt;blockquote class="twitter-tweet" width="550"&gt;&lt;p&gt;&lt;a href="https://twitter.com/davorg"&gt;@davorg&lt;/a&gt; You&amp;#39;re welcome, I will certainly pass your comments on to the development team.(1/2)^GD&lt;/p&gt;
  439. &lt;p&gt;&amp;mdash; first direct help (@firstdirecthelp) &lt;a href="https://twitter.com/firstdirecthelp/statuses/489781248789725184"&gt;July 17, 2014&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;
  440. &lt;p&gt;&lt;script async src="//platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;&lt;/p&gt;
  441. &lt;blockquote class="twitter-tweet" width="550"&gt;&lt;p&gt;&lt;a href="https://twitter.com/davorg"&gt;@davorg&lt;/a&gt; As a business we are satisfied with the levels of security that we have in place. (2/2)^GD&lt;/p&gt;
  442. &lt;p&gt;&amp;mdash; first direct help (@firstdirecthelp) &lt;a href="https://twitter.com/firstdirecthelp/statuses/489781375147335680"&gt;July 17, 2014&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;
  443. &lt;p&gt;&lt;script async src="//platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;&lt;/p&gt;
  444. &lt;p&gt;I thought that &amp;#8220;as a business we are satisfied&amp;#8221; rather missed the point. And told them so.&lt;/p&gt;
  445. &lt;blockquote class="twitter-tweet" width="550"&gt;&lt;p&gt;&lt;a href="https://twitter.com/firstdirecthelp"&gt;@firstdirecthelp&lt;/a&gt; Sure, but (importantly) it&amp;#39;s not just about the business being satisfied. You also need to convince your customers [1/2]&lt;/p&gt;
  446. &lt;p&gt;&amp;mdash; Dave Cross (@davorg) &lt;a href="https://twitter.com/davorg/statuses/489781791868616704"&gt;July 17, 2014&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;
  447. &lt;p&gt;&lt;script async src="//platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;&lt;/p&gt;
  448. &lt;blockquote class="twitter-tweet" width="550"&gt;&lt;p&gt;&lt;a href="https://twitter.com/firstdirecthelp"&gt;@firstdirecthelp&lt;/a&gt; And some of those customers will be experts in computer security who will know about best practice. [2/2]&lt;/p&gt;
  449. &lt;p&gt;&amp;mdash; Dave Cross (@davorg) &lt;a href="https://twitter.com/davorg/statuses/489781998433882112"&gt;July 17, 2014&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;
  450. &lt;p&gt;&lt;script async src="//platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;&lt;/p&gt;
  451. &lt;p&gt;I got no response to that. And &lt;a href="http://twitter.com/brunns"&gt;@brunns&lt;/a&gt; got no response when he tried to push them for more details about how the passwords are stored.&lt;/p&gt;
  452. &lt;blockquote class="twitter-tweet" width="550"&gt;&lt;p&gt;&lt;a href="https://twitter.com/firstdirecthelp"&gt;@firstdirecthelp&lt;/a&gt; &lt;a href="https://twitter.com/davorg"&gt;@davorg&lt;/a&gt; Encrypted, or hashed?&lt;/p&gt;
  453. &lt;p&gt;&amp;mdash; Simon Brunning (@brunns) &lt;a href="https://twitter.com/brunns/statuses/489782060375371777"&gt;July 17, 2014&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;
  454. &lt;p&gt;&lt;script async src="//platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;&lt;/p&gt;
  455. &lt;p&gt;So, to summarise what we know.&lt;/p&gt;
  456. &lt;ul&gt;
  457. &lt;li&gt;First Direct say they store the passwords &amp;#8220;encrypted&amp;#8221;, but it&amp;#8217;s unclear exactly what that means&lt;/li&gt;
  458. &lt;li&gt;It was a business decision to limit the length of the passwords, but we don&amp;#8217;t know why that was considered a good idea&lt;/li&gt;
  459. &lt;li&gt;It still appears that First Direct believe that security by obscurity is an important part of their security policy&lt;/li&gt;
  460. &lt;/ul&gt;
  461. &lt;p&gt;I haven &amp;#8216;t really been reassured by this interaction with First Direct. I felt that the first customer support agent I talked to tried to fob me off with glib truisms, but &amp;#8220;^GD&amp;#8221; tried to actually get answers to my questions &amp;#8211; although his obvious lack of knowledge in this area meant that I didn&amp;#8217;t really get the detailed answers that I wanted.&lt;/p&gt;
  462. &lt;p&gt;I&amp;#8217;m not sure that there&amp;#8217;s anything to be achieved by pushing this any further.&lt;/p&gt;
  463. &lt;div class="crp_related"&gt;&lt;h3&gt;Related Posts:&lt;/h3&gt;&lt;ul&gt;&lt;li&gt;&lt;a href="http://blog.dave.org.uk/2013/08/insurance-update.html"     class="crp_title"&gt;Insurance Update&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="http://blog.dave.org.uk/2012/08/the-chances-of-anything-going-to-mars.html"     class="crp_title"&gt;The Chances of Anything Going to Mars&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="http://blog.dave.org.uk/2011/12/hitchens-last-laugh.html"     class="crp_title"&gt;Hitchens&amp;#8217; Last Laugh&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="http://blog.dave.org.uk/2012/08/gullible.html"     class="crp_title"&gt;Gullible&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="http://blog.dave.org.uk/2014/07/first-direct-passwords.html"     class="crp_title"&gt;First Direct Passwords&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;p&gt;The post &lt;a rel="nofollow" href="http://blog.dave.org.uk/2014/07/first-direct-update.html"&gt;First Direct Update&lt;/a&gt; appeared first on &lt;a rel="nofollow" href="http://blog.dave.org.uk"&gt;Davblog&lt;/a&gt;.&lt;/p&gt;
  464. &lt;img src="http://feeds.feedburner.com/~r/realdavblog/~4/NJ-sXTgM-yo" height="1" width="1"/&gt;</content>
  465.    <summary type="html">&lt;p&gt;Earlier in the week I talked about my concerns with First Direct&amp;#8217;s new password policy. I got an email from them about this, but it really wasn&amp;#8217;t very reassuring. But I kept digging. And on Thursday I got a bit more information from &amp;#8220;^GD&amp;#8221; on the @firstdirecthelp twitter account. It still doesn&amp;#8217;t answer all of [&amp;#8230;]
  466. &lt;div class="crp_related"&gt;
  467. &lt;h3&gt;Related Posts:&lt;/h3&gt;
  468. &lt;ul&gt;
  469. &lt;li&gt;&lt;a href="http://blog.dave.org.uk/2013/08/insurance-update.html"     class="crp_title"&gt;Insurance Update&lt;/a&gt;&lt;/li&gt;
  470. &lt;li&gt;&lt;a href="http://blog.dave.org.uk/2012/08/the-chances-of-anything-going-to-mars.html"     class="crp_title"&gt;The Chances of Anything Going to Mars&lt;/a&gt;&lt;/li&gt;
  471. &lt;li&gt;&lt;a href="http://blog.dave.org.uk/2011/12/hitchens-last-laugh.html"     class="crp_title"&gt;Hitchens&amp;#8217; Last Laugh&lt;/a&gt;&lt;/li&gt;
  472. &lt;li&gt;&lt;a href="http://blog.dave.org.uk/2012/08/gullible.html"     class="crp_title"&gt;Gullible&lt;/a&gt;&lt;/li&gt;
  473. &lt;li&gt;&lt;a href="http://blog.dave.org.uk/2014/07/first-direct-passwords.html"     class="crp_title"&gt;First Direct Passwords&lt;/a&gt;&lt;/li&gt;
  474. &lt;/ul&gt;
  475. &lt;/div&gt;
  476. &lt;p&gt;The post &lt;a rel="nofollow" href="http://blog.dave.org.uk/2014/07/first-direct-update.html"&gt;First Direct Update&lt;/a&gt; appeared first on &lt;a rel="nofollow" href="http://blog.dave.org.uk"&gt;Davblog&lt;/a&gt;.&lt;/p&gt;
  477. </summary>
  478.    <author>
  479.      <name>Dave Cross</name>
  480.    </author>
  481.    <id>http://blog.dave.org.uk/?p=3378</id>
  482.    <published>2014-07-19T11:02:07Z</published>
  483.    <updated>2014-07-19T11:02:07Z</updated>
  484.    <category term="tech"/>
  485.    <category term="banking"/>
  486.    <category term="first direct"/>
  487.    <category term="passwords"/>
  488.    <category term="security"/>
  489.  </entry>
  490.  <entry>
  491.    <title>davblog: First Direct Passwords</title>
  492.    <link rel="alternate" href="http://feedproxy.google.com/~r/realdavblog/~3/VLTr8OXPipg/first-direct-passwords.html" type="text/html"/>
  493.    <content type="xhtml">
  494.      <div xmlns="http://www.w3.org/1999/xhtml"><p>I’ve been a happy customer of <a href="http://firstdirect.com/">First Direct</a> since a month or so after they opened, almost twenty-five years ago.</p>
  495. <p>One of the things I really liked about them was that they hadn’t followed other banks down the route of insisting that you carried a new code-generating dongle around so that you can log into their online banking. But, of course, it was only a matter of time before that changed.</p>
  496. <p>A couple of weeks ago I got a message from them telling me that <a href="http://www2.firstdirect.com/1/2/securekey">Secure Key</a> was on its way. And yesterday when I logged on to my account I was prompted to choose the flavour of secure key that I wanted to use. To be fair to them they have chosen a particularly non-intrusive implementation. Each customer gets three options:</p>
  497. <ol>
  498. <li>The traditional small dongle to carry around with you</li>
  499. <li>An extension to their smartphone app</li>
  500. <li>No secure key at all</li>
  501. </ol>
  502. <p>If you choose the final option then you only get restricted (basically read-only) access to your account through their web site. And if you choose one of the first two options, you can always log on without  the secure key and get the same restricted access.</p>
  503. <p>I chose the smartphone option. I already use their <a href="https://play.google.com/store/apps/details?id=com.firstdirect.bankingonthego">Android app</a> and I pretty much always have my phone with me.</p>
  504. <p>Usually when you log on to First Direct’s online banking you’re asked for three random characters from your password. Under the new system, that changes. I now need to log on to my smartphone app and that will give me a code to input into the web site. But to get into the smartphone app, I don’t use the old three character login. No, I needed to set up a new Digital Secure Password – which I can use for all of my interactions in this brave new world.</p>
  505. <p>And that’s where I think First Direct have slipped up a bit.</p>
  506. <p>When they asked my for my new password, they told me that it needed to be between 6 and 10 characters long.</p>
  507. <p>Those of you with any knowledge of computer security will understand why that worries me. For those who don’t, here’s a brief explanation.</p>
  508. <p>Somewhere in First Direct’s systems is a database that stores details of their customers. There will be a table containing users which has a row of data for each person who logs in to the service. That row will contain information like the users name, login name, email address and (crucially) password. So when someone tries to log in the system find the right row of data (based on the login name) and compares the password in that row with the password that has been entered on the login screen. If the two match then the person is let into the system.</p>
  509. <p>Whenever you have a database table, you have to worry about what would happen if someone managed to get hold of the contents of that table. Clearly it would be a disaster if someone got hold of this table of user data – as they would then have access to the usernames and passwords of all of the bank’s users.</p>
  510. <p>So, to prevent this being a problem, most rational database administrators will encrypt any passwords stored in database tables. And they will encrypt them in such a way that it is impossible (ok, that’s overstating the case a bit – but certainly really really difficult) to decrypt the data to get the passwords back. They will probably use something called a “one-way hash” to do this (if you’re wondering how you check a password when it’s encrypted like this then <a href="http://blog.dave.org.uk/2005/11/basic-password.html">I explain that here</a>).</p>
  511. <p>And these one-way hashes have an interesting property. No matter how long the input string is, the hashed value you get out at the other end is the same length. For example, if you’re using a hashing algorithm called MD5, every hash you get out will be thirty-two characters long.</p>
  512. <p>Therefore, if you’re using a hashing algorithm to protect your users’ passwords, it doesn’t matter how long the password is. Because the hashed version will always be the same length. You should therefore encourage your users to make their passwords as long as they want. You shouldn’t be imposing artificial length restrictions on them.</p>
  513. <p>And that’s why people who know about computer security will have all shared my concerns when I said that First Direct imposed a length restriction on these new passwords. The most common reason for a maximum length on a password is that the company is storing passwords as plain text in the database. With all the attendant problems that will cause if someone gets hold of the data.</p>
  514. <p>I’m not saying for sure that First Direct are doing that. I’m just saying that it’s a possibility and one that is very worrying. If that’s not the case I’d like to know what other reason they have for limiting the password’s length like this.</p>
  515. <p>I’ve send them a message asking for clarification. I’ll update this post with any response that I get.</p>
  516. <p><strong>Update (17 July):</strong> I got a reply from First Direct. This is what they said.</p>
  517. <blockquote><p>Thank you for your message dated 16-Jul-2014 regarding the security of your password for your Digital Secure Key.</p>
  518. <p>Ensuring the security of our systems is, and will continue to be, our number one priority.</p>
  519. <p>All the details that are sent to and from the system are encrypted using high encryption levels. As long as you keep your password secret, we can assure you that the system is secure. As you will appreciate, we cannot provide further details about the security measures used by Internet Banking, as we must protect the integrity of the system.</p>
  520. <p>Our customers also have a responsibility to ensure that they protect their computers by following our common-sense recommendations.  Further information can be found by selecting ‘security’ from the bottom menu on our website, <a href="http://www.firstdirect.com" target="_blank">www.firstdirect.com</a></p>
  521. <p>Please let us know if you have any further questions, and we’ll be happy to discuss.</p></blockquote>
  522. <p>Which isn’t very helpful and doesn’t address my question. I’ve tried explaining it to them again.</p>
  523. <div class="crp_related"><h3>Related Posts:</h3><ul><li><a href="http://blog.dave.org.uk/2012/03/internet-security-rule-one.html" class="crp_title">Internet Security Rule One</a></li><li><a href="http://blog.dave.org.uk/2014/07/first-direct-update.html" class="crp_title">First Direct Update</a></li><li><a href="http://blog.dave.org.uk/2014/04/free-web-advice-marvel.html" class="crp_title">Free Web Advice: Marvel</a></li><li><a href="http://blog.dave.org.uk/2013/06/public-wifi.html" class="crp_title">Public Wifi</a></li><li><a href="http://blog.dave.org.uk/2011/12/lovefilm-and-silverlight.html" class="crp_title">LoveFilm and Silverlight</a></li></ul></div><p>The post <a rel="nofollow" href="http://blog.dave.org.uk/2014/07/first-direct-passwords.html">First Direct Passwords</a> appeared first on <a rel="nofollow" href="http://blog.dave.org.uk">Davblog</a>.</p>
  524. <img src="http://feeds.feedburner.com/~r/realdavblog/~4/VLTr8OXPipg" height="1" width="1"/></div>
  525.    </content>
  526.    <summary type="html">&lt;p&gt;I&amp;#8217;ve been a happy customer of First Direct since a month or so after they opened, almost twenty-five years ago. One of the things I really liked about them was that they hadn&amp;#8217;t followed other banks down the route of insisting that you carried a new code-generating dongle around so that you can log into [&amp;#8230;]
  527. &lt;div class="crp_related"&gt;
  528. &lt;h3&gt;Related Posts:&lt;/h3&gt;
  529. &lt;ul&gt;
  530. &lt;li&gt;&lt;a href="http://blog.dave.org.uk/2012/03/internet-security-rule-one.html"     class="crp_title"&gt;Internet Security Rule One&lt;/a&gt;&lt;/li&gt;
  531. &lt;li&gt;&lt;a href="http://blog.dave.org.uk/2014/07/first-direct-update.html"     class="crp_title"&gt;First Direct Update&lt;/a&gt;&lt;/li&gt;
  532. &lt;li&gt;&lt;a href="http://blog.dave.org.uk/2014/04/free-web-advice-marvel.html"     class="crp_title"&gt;Free Web Advice: Marvel&lt;/a&gt;&lt;/li&gt;
  533. &lt;li&gt;&lt;a href="http://blog.dave.org.uk/2013/06/public-wifi.html"     class="crp_title"&gt;Public Wifi&lt;/a&gt;&lt;/li&gt;
  534. &lt;li&gt;&lt;a href="http://blog.dave.org.uk/2011/12/lovefilm-and-silverlight.html"     class="crp_title"&gt;LoveFilm and Silverlight&lt;/a&gt;&lt;/li&gt;
  535. &lt;/ul&gt;
  536. &lt;/div&gt;
  537. &lt;p&gt;The post &lt;a rel="nofollow" href="http://blog.dave.org.uk/2014/07/first-direct-passwords.html"&gt;First Direct Passwords&lt;/a&gt; appeared first on &lt;a rel="nofollow" href="http://blog.dave.org.uk"&gt;Davblog&lt;/a&gt;.&lt;/p&gt;
  538. </summary>
  539.    <author>
  540.      <name>Dave Cross</name>
  541.    </author>
  542.    <id>http://blog.dave.org.uk/?p=3372</id>
  543.    <published>2014-07-16T12:37:36Z</published>
  544.    <updated>2014-07-16T12:37:36Z</updated>
  545.    <category term="tech"/>
  546.    <category term="banking"/>
  547.    <category term="first direct"/>
  548.    <category term="password"/>
  549.    <category term="security"/>
  550.  </entry>
  551.  <entry>
  552.    <title>perl hacks: London Perl Mongers Meeting</title>
  553.    <link rel="alternate" href="http://perlhacks.com/2014/07/london-perl-mongers-meeting/" type="text/html"/>
  554.    <content type="xhtml">
  555.      <div xmlns="http://www.w3.org/1999/xhtml"><p>I thought you might be interested in a couple of events that the London Perl Mongers have coming up in the next couple of months.</p>
  556. <p><strong>Technical Meeting</strong></p>
  557. <p><em>24th July 2014, Conway Hall</em><br/>
  558. Currently, four talks have been announced.</p>
  559. <ul>
  560. <li>Thomas Klausner (domm) from Vienna.pm is going to talk about OX &amp; AngularJS</li>
  561. <li> Alex Balhatchet is going to talk about his rewrite of Ovid’s Test::Kit module</li>
  562. <li>Mike Francis will tell us about creating a RESTful database frontend with Web::Simple &amp; Web::Machine and how annoying that was</li>
  563. <li>Dave Cross will natter about Github, Travis-CI and Perl</li>
  564. </ul>
  565. <p><a href="http://www.meetup.com/London-Perl-Mongers/events/191624922/">Meetup event</a> /<a href="https://www.facebook.com/events/469685493134908"> Facebook event</a> / <a href="http://lanyrd.com/2014/london-perl-mongers-hackday/">Lanyrd event</a></p>
  566. <p><strong>Hackday</strong></p>
  567. <p><em>20th September 2014, London Hackspace</em><br/>
  568. This is a new experiment for us. Do you want to hang out with some Perl Mongers and hack on one of your current projects? Or do you want to find a Perl project to hack on? Then come and join us at the London Hackspace in September.</p>
  569. <p><a href="http://www.meetup.com/London-Perl-Mongers/events/194285872/">Meetup event</a> / <a href="https://www.facebook.com/events/603111073136914">Facebook event</a> / <a href="http://lanyrd.com/2014/london-perl-mongers-hackday/">Lanyrd event</a></p>
  570. <p>Hope to see you at one or both of these event.</p>
  571. <p>The post <a rel="nofollow" href="http://perlhacks.com/2014/07/london-perl-mongers-meeting/">London Perl Mongers Meeting</a> appeared first on <a rel="nofollow" href="http://perlhacks.com">Perl Hacks</a>.</p>
  572. </div>
  573.    </content>
  574.    <summary type="xhtml">
  575.      <div xmlns="http://www.w3.org/1999/xhtml"><p>I thought you might be interested in a couple of events that the London Perl Mongers have coming up in the next couple of months. Technical Meeting 24th July 2014, Conway Hall Currently, four talks have been announced. Thomas Klausner (domm) from Vienna.pm is going to talk about OX &amp; AngularJS  Alex Balhatchet is going […]</p>
  576. <p>The post <a rel="nofollow" href="http://perlhacks.com/2014/07/london-perl-mongers-meeting/">London Perl Mongers Meeting</a> appeared first on <a rel="nofollow" href="http://perlhacks.com">Perl Hacks</a>.</p>
  577. </div>
  578.    </summary>
  579.    <author>
  580.      <name>Dave Cross</name>
  581.    </author>
  582.    <id>http://perlhacks.com/?p=930</id>
  583.    <published>2014-07-12T13:22:21Z</published>
  584.    <updated>2014-07-12T13:22:21Z</updated>
  585.    <category term="Community"/>
  586.    <category term="hackday"/>
  587.    <category term="london.pm"/>
  588.    <category term="technical meeting"/>
  589.  </entry>
  590.  <entry>
  591.    <title>perl hacks: Perl School Slides</title>
  592.    <link rel="alternate" href="http://perlhacks.com/2014/07/perl-school-slides/" type="text/html"/>
  593.    <content type="html">&lt;p&gt;In 2012 and 2013 I ran an experiment called &lt;a href="http://perlschool.com/"&gt;Perl School&lt;/a&gt;. I ran cheap Perl training on a Saturday at &lt;a href="https://www.campuslondon.com/"&gt;Google Campus&lt;/a&gt;. I got some great reactions but I stopped it after almost a year because it wasn&amp;#8217;t getting the traction that I hoped for and attendances were starting to drop.&lt;/p&gt;
  594. &lt;p&gt;That&amp;#8217;s not the end of Perl School though. I have a couple of ideas that I&amp;#8217;m considering and it will return at some point (in some form).&lt;/p&gt;
  595. &lt;p&gt;But I thought that the courses were good. And I realised earlier today that I hadn&amp;#8217;t made some of the slides public. So I uploaded them to Slideshare and they are embedded below.&lt;/p&gt;
  596. &lt;p&gt;Let me know if you find them interesting or useful.&lt;/p&gt;
  597. &lt;p style="margin:0"&gt;&lt;iframe src="//www.slideshare.net/slideshow/embed_code/36502584" width="427" height="356" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:1px solid #CCC; border-width:1px 1px 0; margin-bottom:5px; max-width: 100%;" allowfullscreen&gt; &lt;/iframe&gt;&lt;/p&gt;
  598. &lt;div style="margin-top:5px; margin-bottom:25px"&gt; &lt;strong&gt; &lt;a href="https://www.slideshare.net/davorg/database-programming-with-perl-and-dbixclass" title="Database Programming with Perl and DBIx::Class" target="_blank"&gt;Database Programming with Perl and DBIx::Class&lt;/a&gt; &lt;/strong&gt; from &lt;strong&gt;&lt;a href="http://www.slideshare.net/davorg" target="_blank"&gt;Dave Cross&lt;/a&gt;&lt;/strong&gt; &lt;/div&gt;
  599. &lt;p style="margin:0"&gt;&lt;iframe src="//www.slideshare.net/slideshow/embed_code/36502727" width="427" height="356" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:1px solid #CCC; border-width:1px 1px 0; margin-bottom:5px; max-width: 100%;" allowfullscreen&gt; &lt;/iframe&gt;&lt;/p&gt;
  600. &lt;div style="margin-top:5px; margin-bottom:25px"&gt; &lt;strong&gt; &lt;a href="https://www.slideshare.net/davorg/objectoriented-programming-with-perl-and-moose" title="Object-Oriented Programming with Perl and Moose" target="_blank"&gt;Object-Oriented Programming with Perl and Moose&lt;/a&gt; &lt;/strong&gt; from &lt;strong&gt;&lt;a href="http://www.slideshare.net/davorg" target="_blank"&gt;Dave Cross&lt;/a&gt;&lt;/strong&gt; &lt;/div&gt;
  601. &lt;p&gt;The post &lt;a rel="nofollow" href="http://perlhacks.com/2014/07/perl-school-slides/"&gt;Perl School Slides&lt;/a&gt; appeared first on &lt;a rel="nofollow" href="http://perlhacks.com"&gt;Perl Hacks&lt;/a&gt;.&lt;/p&gt;
  602. </content>
  603.    <summary type="xhtml">
  604.      <div xmlns="http://www.w3.org/1999/xhtml"><p>In 2012 and 2013 I ran an experiment called Perl School. I ran cheap Perl training on a Saturday at Google Campus. I got some great reactions but I stopped it after almost a year because it wasn’t getting the traction that I hoped for and attendances were starting to drop. That’s not the end […]</p>
  605. <p>The post <a rel="nofollow" href="http://perlhacks.com/2014/07/perl-school-slides/">Perl School Slides</a> appeared first on <a rel="nofollow" href="http://perlhacks.com">Perl Hacks</a>.</p>
  606. </div>
  607.    </summary>
  608.    <author>
  609.      <name>Dave Cross</name>
  610.    </author>
  611.    <id>http://perlhacks.com/?p=921</id>
  612.    <published>2014-07-01T12:23:48Z</published>
  613.    <updated>2014-07-01T12:23:48Z</updated>
  614.    <category term="Miscellaneous"/>
  615.  </entry>
  616.  <entry>
  617.    <title>slideshare: Object-Oriented Programming with Perl and Moose</title>
  618.    <link rel="alternate" href="http://www.slideshare.net/davorg/objectoriented-programming-with-perl-and-moose" type="text/html"/>
  619.    <content type="html">
  620.        &lt;img src="//cdn.slidesharecdn.com/ss_thumbnails/moose-140701053812-phpapp01-thumbnail-2.jpg?cb=1404211297" alt ="" style="border:1px solid #C3E6D8;float:right;" /&gt;&lt;br&gt;
  621.      </content>
  622.    <summary type="html">
  623.        &lt;img src="//cdn.slidesharecdn.com/ss_thumbnails/moose-140701053812-phpapp01-thumbnail-2.jpg?cb=1404211297" alt ="" style="border:1px solid #C3E6D8;float:right;" /&gt;&lt;br&gt;
  624.      </summary>
  625.    <author>
  626.      <name>davorg@slideshare.net(davorg)</name>
  627.    </author>
  628.    <id>http://www.slideshare.net/davorg/objectoriented-programming-with-perl-and-moose</id>
  629.    <published>2014-07-01T10:38:12Z</published>
  630.    <updated>2014-07-01T10:38:12Z</updated>
  631.  </entry>
  632.  <entry>
  633.    <title>slideshare: Database Programming with Perl and DBIx::Class</title>
  634.    <link rel="alternate" href="http://www.slideshare.net/davorg/database-programming-with-perl-and-dbixclass" type="text/html"/>
  635.    <content type="html">
  636.        &lt;img src="//cdn.slidesharecdn.com/ss_thumbnails/dbic-140701053449-phpapp01-thumbnail-2.jpg?cb=1404211152" alt ="" style="border:1px solid #C3E6D8;float:right;" /&gt;&lt;br&gt;
  637.      </content>
  638.    <summary type="html">
  639.        &lt;img src="//cdn.slidesharecdn.com/ss_thumbnails/dbic-140701053449-phpapp01-thumbnail-2.jpg?cb=1404211152" alt ="" style="border:1px solid #C3E6D8;float:right;" /&gt;&lt;br&gt;
  640.      </summary>
  641.    <author>
  642.      <name>davorg@slideshare.net(davorg)</name>
  643.    </author>
  644.    <id>http://www.slideshare.net/davorg/database-programming-with-perl-and-dbixclass</id>
  645.    <published>2014-07-01T10:34:49Z</published>
  646.    <updated>2014-07-01T10:34:49Z</updated>
  647.  </entry>
  648.  <entry>
  649.    <title>books read: The Complete Works of H.P. Lovecraft</title>
  650.    <link rel="alternate" href="http://www.goodreads.com/review/show/965111614?utm_medium=api&amp;utm_source=rss" type="text/html"/>
  651.    <content type="xhtml">
  652.      <div xmlns="http://www.w3.org/1999/xhtml">
  653.      
  654.      <a href="http://www.goodreads.com/book/show/11851522-the-complete-works-of-h-p-lovecraft?utm_medium=api&amp;utm_source=rss"><img alt="The Complete Works of H.P. Lovecraft" src="http://d.gr-assets.com/books/1327886768s/11851522.jpg"/></a><br/>
  655.                                      author: H.P. Lovecraft<br/>
  656.                                      name: David<br/>
  657.                                      average rating: 4.31<br/>
  658.                                      book published: 2011<br/>
  659.                                      rating: 0<br/>
  660.                                      read at: <br/>
  661.                                      date added: 2014/06/12<br/>
  662.                                      shelves: currently-reading<br/>
  663.                                      review: <br/><br/>
  664.                                      
  665.    </div>
  666.    </content>
  667.    <id>http://www.goodreads.com/review/show/965111614?utm_medium=api&amp;utm_source=rss</id>
  668.    <published>2014-06-12T01:50:30-07:00</published>
  669.    <updated>2014-06-12T01:50:30-07:00</updated>
  670.  </entry>
  671.  <entry>
  672.    <title>davblog: Sky Broadband Update</title>
  673.    <link rel="alternate" href="http://feedproxy.google.com/~r/realdavblog/~3/04sLV8hNcHw/sky-broadband-update.html" type="text/html"/>
  674.    <content type="xhtml">
  675.      <div xmlns="http://www.w3.org/1999/xhtml"><p>It’s probably time for an update on my Sky Broadband situation.</p>
  676. <p>I <a href="http://blog.dave.org.uk/2014/04/sky-broadband.html">last wrote about Sky</a> on 16th April. That was the date of their second failed attempt to connect me to their broadband. It was the date that I decided to cancel my order and go elsewhere.</p>
  677. <p>First the good news. I was considering alternative providers. I called Virgin Media and they told me that I could have a 50 Mb fibre connection for an extra £2 a month over what I already paid them for my TV and phone package. And, as a bonus, they could do it within a week – still five days earlier than Sky had scheduled their third attempt at connecting me. I ordered it, they came round on the promised day and everything works fine. Very happy with them.</p>
  678. <p>This then left me trying to cancel my Sky order. This was slightly complicated by the fact that Sky had successfully connected my phone line[1] and also the fact that this phone line is used for monitoring my ADT burglar alarm. I didn’t want to cancel the phone line until ADT had moved the alarm monitoring to the Virgin Media line. I explained all this to Sky and  they seemed to understand.</p>
  679. <p>A chap called Andy in Sky’s customer service took it upon himself to take on the project. He took to phoning me weekly to ask me what was going on with ADT. To be honest, I got a bit lazy and it took me a while to get in touch with them.</p>
  680. <p>Then my hand was forced. In the middle of May, some error lights on the burglar alarm started flashing. I called ADT to see what the problem was and they told me that it looked like the phone line was dead. I plugged a phone into the line and was able to confirm this. The phone line had been disconnected – despite my explicit instructions about not doing that until I asked for it.</p>
  681. <p>I was a bit stuck. Calling Sky’s customer support from a non-Sky phone line is very expensive. And the only Sky line I had was dead. I tried their online chat facility, but the people you get on that are absolutely useless. Luckily Andy was due to call me for a progress update the following day, so I decided to wait for that.</p>
  682. <p>When Andy called, I asked why they have disconnected the phone. He said that they hadn’t. He ran a few line checks and discovered a fault on the line. He offered to send an engineer to fix it. I told him not to bother and to go ahead with the cancellation. He told me that there was some problem with their systems that prevented him cancelling the contract right away but that he had reported the bug and would let me know when it was fixed.</p>
  683. <p>Time passed.</p>
  684. <p>Earlier this week, I wondered idly what was going on so I sent them an email asking for a progress report. A woman called and told me that my records said that someone (Andy, I assume) had been checking into my account daily and leaving notes explaining why he still couldn’t close the account.</p>
  685. <p>The following day, I got a call from Andy (I’m sure it was pure coincidence that this was the day after I had chased them). He told me that the bug had been fixed and asked me to confirm that I still wanted to cancel the account. I told him that I did and he started the process. He warned me that I wold receive a few automated emails.</p>
  686. <p>Within half an hour I got the first email, telling me that my services would be cancelled on Thursday 6th June. Hooray. But that wasn’t the end of the story.</p>
  687. <p>The following day, I got another (presumably automatic email) offering me twelve months of free line rental if I changed my mind. Then I got the same message by text. And today I’ve got a missed call from a number which Google tells me is Sky’s customer retention department. They certainly seem keen to keep me. It’s a shame they didn’t put so much effort in back in April when they might have been able to salvage something from the disaster.</p>
  688. <p>Oh, and I’ve received a bill. They want to charge me a month’s line rental for the phone line. A phone line that only ever really existed to serve a broadband connection that they weren’t able to provide. A phone line that I’ve used to make one call – the call to Sky customer services on 16th April when I first told them to cancel my order.</p>
  689. <p>I’ve cancelled the old Be Broadband direct debit that they were planning to use to take the money. I’m amazed that they wouldn’t just waive those charges.</p>
  690. <p>So, two months on I’m still (to some extent) a Sky customer. But the end is (hopefully) in sight.</p>
  691. <p>Oh, and throughout all of this, the  <a href="https://twitter.com/SkyHelpTeam">@SkyHelpTeam</a> Twitter account has been a source of much amusement. They reply to every mention, but haven’t got a clue what is going on. They use a social media customer tracker called <a href="http://www.lithium.com/products-solutions/social-media-management">Lithium</a>. But they must have it configured wrong because each conversation starts with them knowing no history of this problem at all. And, having watched the product video, that’s exactly what Lithium is for.</p>
  692. <p>Throughout this hold affair all of Sky customer service people (with about two exceptions) have shown themselves to be rubbish at their job.</p>
  693. <p>[1] You’ll have noticed, no doubt, that we had to phone lines. The home phone (along with our TV) has been provided by Virgin Media for years. I also had another phone line for the broadband. I had this on a separate contract because it had been paid for through the limited company that I use for contracting.</p>
  694. <div class="crp_related"><h3>Related Posts:</h3><ul><li><a href="http://blog.dave.org.uk/2014/04/sky-broadband.html" class="crp_title">Sky Broadband</a></li><li><a href="http://blog.dave.org.uk/2013/08/insurance-update.html" class="crp_title">Insurance Update</a></li><li><a href="http://blog.dave.org.uk/2012/07/loving-bose.html" class="crp_title">Loving Bose</a></li><li><a href="http://blog.dave.org.uk/2012/09/dear-recruiter.html" class="crp_title">Dear Recruiter</a></li><li><a href="http://blog.dave.org.uk/2012/03/week-notes-8-9.html" class="crp_title">Week Notes 8 &amp; 9</a></li></ul></div><p>The post <a rel="nofollow" href="http://blog.dave.org.uk/2014/06/sky-broadband-update.html">Sky Broadband Update</a> appeared first on <a rel="nofollow" href="http://blog.dave.org.uk">Davblog</a>.</p>
  695. <img src="http://feeds.feedburner.com/~r/realdavblog/~4/04sLV8hNcHw" height="1" width="1"/></div>
  696.    </content>
  697.    <summary type="html">&lt;p&gt;It&amp;#8217;s probably time for an update on my Sky Broadband situation. I last wrote about Sky on 16th April. That was the date of their second failed attempt to connect me to their broadband. It was the date that I decided to cancel my order and go elsewhere. First the good news. I was considering [&amp;#8230;]
  698. &lt;div class="crp_related"&gt;
  699. &lt;h3&gt;Related Posts:&lt;/h3&gt;
  700. &lt;ul&gt;
  701. &lt;li&gt;&lt;a href="http://blog.dave.org.uk/2014/04/sky-broadband.html"     class="crp_title"&gt;Sky Broadband&lt;/a&gt;&lt;/li&gt;
  702. &lt;li&gt;&lt;a href="http://blog.dave.org.uk/2013/08/insurance-update.html"     class="crp_title"&gt;Insurance Update&lt;/a&gt;&lt;/li&gt;
  703. &lt;li&gt;&lt;a href="http://blog.dave.org.uk/2012/07/loving-bose.html"     class="crp_title"&gt;Loving Bose&lt;/a&gt;&lt;/li&gt;
  704. &lt;li&gt;&lt;a href="http://blog.dave.org.uk/2012/09/dear-recruiter.html"     class="crp_title"&gt;Dear Recruiter&lt;/a&gt;&lt;/li&gt;
  705. &lt;li&gt;&lt;a href="http://blog.dave.org.uk/2012/03/week-notes-8-9.html"     class="crp_title"&gt;Week Notes 8 &amp;#038; 9&lt;/a&gt;&lt;/li&gt;
  706. &lt;/ul&gt;
  707. &lt;/div&gt;
  708. &lt;p&gt;The post &lt;a rel="nofollow" href="http://blog.dave.org.uk/2014/06/sky-broadband-update.html"&gt;Sky Broadband Update&lt;/a&gt; appeared first on &lt;a rel="nofollow" href="http://blog.dave.org.uk"&gt;Davblog&lt;/a&gt;.&lt;/p&gt;
  709. </summary>
  710.    <author>
  711.      <name>Dave Cross</name>
  712.    </author>
  713.    <id>http://blog.dave.org.uk/?p=3367</id>
  714.    <published>2014-06-08T13:51:45Z</published>
  715.    <updated>2014-06-08T13:51:45Z</updated>
  716.    <category term="customer service"/>
  717.    <category term="broadband"/>
  718.    <category term="sky"/>
  719.    <category term="tech"/>
  720.  </entry>
  721.  <entry>
  722.    <title>davblog: National Rail Travel Alert</title>
  723.    <link rel="alternate" href="http://feedproxy.google.com/~r/realdavblog/~3/xAnxg5S-ajo/national-rail-travel-alert.html" type="text/html"/>
  724.    <content type="xhtml">
  725.      <div xmlns="http://www.w3.org/1999/xhtml"><p>This is the text of a National Rail travel alert email that I received this morning.</p>
  726. <blockquote><p>Problems have been reported which may affect your journey between Balham (BAL) and Shepherd’s Bush (SPB)</p>
  727. <p>More details of this disruption can be found here: http://nationalrail.co.uk/service_disruptions/76437.aspx</p>
  728. <p>To see how this disruption affects your journey and to get alternative options planned for you, please use the <a title="Online Journey Planner" href="http://ojp.nationalrail.co.uk" target="OY-HomVFH_D16cVg8NT3jQ4">Online Journey Planner</a></p>
  729. <p>Alternatively, for up to date information for your station, use the <a href="http://ojp.nationalrail.co.uk/service/ldbboard/dep/BAL/SPB/To">Live Departure Boards.</a></p>
  730. <p>Prefer to get in touch by phone? Call TrainTracker on 0871 200 49 50 (10p per min, mobiles higher) or text your journey details to 84950 to use TrainTracker Text</p>
  731. <p>You can manage your alerts by visiting: http://ojp.nationalrail.co.uk/personal/member/myAccount</p>
  732. <p>Don’t forget, you can also follow us on <a title="Twitter" href="http://twitter.com/nationalrailenq" target="OY-HomVFH_D16cVg8NT3jQ4">Twitter</a> or Find us on <a title="Facebook" href="http://facebook.com/NREDisruption" target="OY-HomVFH_D16cVg8NT3jQ4">Facebook</a> for the latest rail travel news</p>
  733. <p>Please do not reply to this email as it is sent from an unmonitored address. If you need to contact us, you can do so here: http://nationalrail.co.uk/feedback</p></blockquote>
  734. <p>Can you spot the obvious idiocy here?</p>
  735. <p>It’s an HTML email. That’s obvious from the links that appear in it. Links to things like the <a href="http://ojp.nationalrail.co.uk">Online Journey Planner</a> and the <a href="http://ojp.nationalrail.co.uk/service/ldbboard/dep/BAL/SPB/To">Live Departure Boards</a>. But there are a couple of links that are written as plain text URLs – ones that you can’t just click on. And one of them is the most important link in the email – the link to the full information about the problems.</p>
  736. <p>In order to read whatever is on the other end of that link, you’d need to copy it and paste it into the location bar in your browser. That’s simple enough, of course, on a desktop computer. But surely one of the important use cases for these alerts is people standing on a platform trying to work out what’s going on with their train – in which case they’d almost certainly be using a smartphone. And copy and paste isn’t the easiest of things to do on a smartphone.</p>
  737. <p>Someone in the National Rail Travel Alerts department is more than a little confused about how URLs in email work.</p>
  738. <div class="crp_related"><h3>Related Posts:</h3><ul><li><a href="http://blog.dave.org.uk/2013/06/jessica-london.html" class="crp_title">Jessica London</a></li><li><a href="http://blog.dave.org.uk/2014/04/free-web-advice-marvel.html" class="crp_title">Free Web Advice: Marvel</a></li><li><a href="http://blog.dave.org.uk/2014/07/first-direct-passwords.html" class="crp_title">First Direct Passwords</a></li><li><a href="http://blog.dave.org.uk/2012/09/dear-recruiter.html" class="crp_title">Dear Recruiter</a></li><li><a href="http://blog.dave.org.uk/2014/06/sky-broadband-update.html" class="crp_title">Sky Broadband Update</a></li></ul></div><p>The post <a rel="nofollow" href="http://blog.dave.org.uk/2014/05/national-rail-travel-alert.html">National Rail Travel Alert</a> appeared first on <a rel="nofollow" href="http://blog.dave.org.uk">Davblog</a>.</p>
  739. <img src="http://feeds.feedburner.com/~r/realdavblog/~4/xAnxg5S-ajo" height="1" width="1"/></div>
  740.    </content>
  741.    <summary type="html">&lt;p&gt;This is the text of a National Rail travel alert email that I received this morning. Problems have been reported which may affect your journey between Balham (BAL) and Shepherd&amp;#8217;s Bush (SPB) More details of this disruption can be found here: http://nationalrail.co.uk/service_disruptions/76437.aspx To see how this disruption affects your journey and to get alternative options [&amp;#8230;]
  742. &lt;div class="crp_related"&gt;
  743. &lt;h3&gt;Related Posts:&lt;/h3&gt;
  744. &lt;ul&gt;
  745. &lt;li&gt;&lt;a href="http://blog.dave.org.uk/2013/06/jessica-london.html"     class="crp_title"&gt;Jessica London&lt;/a&gt;&lt;/li&gt;
  746. &lt;li&gt;&lt;a href="http://blog.dave.org.uk/2014/04/free-web-advice-marvel.html"     class="crp_title"&gt;Free Web Advice: Marvel&lt;/a&gt;&lt;/li&gt;
  747. &lt;li&gt;&lt;a href="http://blog.dave.org.uk/2014/07/first-direct-passwords.html"     class="crp_title"&gt;First Direct Passwords&lt;/a&gt;&lt;/li&gt;
  748. &lt;li&gt;&lt;a href="http://blog.dave.org.uk/2012/09/dear-recruiter.html"     class="crp_title"&gt;Dear Recruiter&lt;/a&gt;&lt;/li&gt;
  749. &lt;li&gt;&lt;a href="http://blog.dave.org.uk/2014/06/sky-broadband-update.html"     class="crp_title"&gt;Sky Broadband Update&lt;/a&gt;&lt;/li&gt;
  750. &lt;/ul&gt;
  751. &lt;/div&gt;
  752. &lt;p&gt;The post &lt;a rel="nofollow" href="http://blog.dave.org.uk/2014/05/national-rail-travel-alert.html"&gt;National Rail Travel Alert&lt;/a&gt; appeared first on &lt;a rel="nofollow" href="http://blog.dave.org.uk"&gt;Davblog&lt;/a&gt;.&lt;/p&gt;
  753. </summary>
  754.    <author>
  755.      <name>Dave Cross</name>
  756.    </author>
  757.    <id>http://blog.dave.org.uk/?p=3359</id>
  758.    <published>2014-05-12T08:39:47Z</published>
  759.    <updated>2014-05-12T08:39:47Z</updated>
  760.    <category term="tech"/>
  761.    <category term="email"/>
  762.    <category term="links"/>
  763.    <category term="national rail"/>
  764.  </entry>
  765.  <entry>
  766. <id>tag:search.cpan.org,2014-05-06:DAVECROSS:WWW-Shorten-3.05</id>
  767.  
  768. <link rel="alternate" type="text/html" href="http://search.cpan.org/~davecross/WWW-Shorten-3.05/"/>
  769. <updated>2014-05-06T19:19:30Z</updated>
  770. <author>
  771. <name>Dave Cross</name>
  772. <uri>http://search.cpan.org/~davecross/</uri>
  773. </author>
  774. <content>
  775. Interface to URL shortening sites.
  776. </content>
  777. <title>cpan: WWW-Shorten-3.05</title></entry>
  778.  <entry>
  779.    <title>perl hacks: Training in London</title>
  780.    <link rel="alternate" href="http://perlhacks.com/2014/05/training-london/" type="text/html"/>
  781.    <content type="html">&lt;p&gt;For many years now a regular feature of my training calendar has been the annual public courses that I have run in London in conjunction with &lt;a title="Installing Modules" href="http://www.flossuk.org"&gt;FlossUK&lt;/a&gt;. Normally these happen in February, but this year I had to postpone them as I was in the USA for a lot of February.&lt;/p&gt;
  782. &lt;p&gt;But FlossUK still wanted to do them, so we&amp;#8217;ve arranged to run the courses in November instead. There will be two two-day courses which will be held at the Ambassadors Hotel in central London.&lt;/p&gt;
  783. &lt;ul&gt;
  784. &lt;li&gt;&lt;a href="http://learnperl.co.uk/courses/intermediate-perl/"&gt;Intermediate Perl&lt;/a&gt; – 11/12 November&lt;/li&gt;
  785. &lt;li&gt;&lt;a href="http://learnperl.co.uk/courses/advanced-perl-techniques/"&gt;Advanced Perl Techniques&lt;/a&gt; – 13/14 November&lt;/li&gt;
  786. &lt;/ul&gt;
  787. &lt;p&gt;For full details (and soon, I hope, a booking form) see the &lt;a href="http://www.flossuk.org/Events/Perl2014"&gt;FlossUK web site&lt;/a&gt;.&lt;/p&gt;
  788. &lt;p&gt;&amp;nbsp;&lt;/p&gt;
  789. &lt;p&gt;The post &lt;a rel="nofollow" href="http://perlhacks.com/2014/05/training-london/"&gt;Training in London&lt;/a&gt; appeared first on &lt;a rel="nofollow" href="http://perlhacks.com"&gt;Perl Hacks&lt;/a&gt;.&lt;/p&gt;
  790. </content>
  791.    <summary type="xhtml">
  792.      <div xmlns="http://www.w3.org/1999/xhtml"><p>For many years now a regular feature of my training calendar has been the annual public courses that I have run in London in conjunction with FlossUK. Normally these happen in February, but this year I had to postpone them as I was in the USA for a lot of February. But FlossUK still wanted […]</p>
  793. <p>The post <a rel="nofollow" href="http://perlhacks.com/2014/05/training-london/">Training in London</a> appeared first on <a rel="nofollow" href="http://perlhacks.com">Perl Hacks</a>.</p>
  794. </div>
  795.    </summary>
  796.    <author>
  797.      <name>Dave Cross</name>
  798.    </author>
  799.    <id>http://perlhacks.com/?p=907</id>
  800.    <published>2014-05-03T10:29:06Z</published>
  801.    <updated>2014-05-03T10:29:06Z</updated>
  802.    <category term="Training"/>
  803.    <category term="2014"/>
  804.    <category term="advanced"/>
  805.    <category term="intermediate"/>
  806.    <category term="london"/>
  807.    <category term="november"/>
  808.    <category term="perl"/>
  809.    <category term="training"/>
  810.  </entry>
  811. </feed>
  812.  
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda