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-10-23T02:03:26Z</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/524922493820469248" type="text/html"/>
  16.    <content type="xhtml">
  17.      <div xmlns="http://www.w3.org/1999/xhtml">See, I thought Microsoft bought Nokia so they could sell phones without the (damaged) Microsoft branding.</div>
  18.    </content>
  19.    <updated>2014-10-22T13:57:29Z</updated>
  20.  <title>twitter: See, I thought Microsoft bought Nokia so they could sell phones without the (damaged) Microsoft branding.</title></entry>
  21.  <entry>
  22.    
  23.    <link rel="alternate" href="https://twitter.com/davorg/status/524920418013315072" type="text/html"/>
  24.    <content type="xhtml">
  25.      <div xmlns="http://www.w3.org/1999/xhtml">Microsoft ditching the Nokia brand name - http://t.co/7MUDFCfz41</div>
  26.    </content>
  27.    <updated>2014-10-22T13:49:14Z</updated>
  28.  <title>twitter: Microsoft ditching the Nokia brand name - http://t.co/7MUDFCfz41</title></entry>
  29.  <entry>
  30.    
  31.    <link rel="alternate" href="https://twitter.com/davorg/status/524882602629799938" type="text/html"/>
  32.    <content type="xhtml">
  33.      <div xmlns="http://www.w3.org/1999/xhtml">RT @richardosman: The Feminist Society at my daughter's 6th Form had their first meeting today. They optimistically booked a room for 20. 4…</div>
  34.    </content>
  35.    <updated>2014-10-22T11:18:59Z</updated>
  36.  <title>twitter: RT @richardosman: The Feminist Society at my daughter's 6th Form had their first meeting today. They optimistically booked a room for 20. 4…</title></entry>
  37.  <entry>
  38.    
  39.    <link rel="alternate" href="https://twitter.com/davorg/status/524680455615164416" type="text/html"/>
  40.    <content type="xhtml">
  41.      <div xmlns="http://www.w3.org/1999/xhtml">Excellent show from @AnnieEvemusic tonight. I cannot emphasise enough how much you should be listening to her</div>
  42.    </content>
  43.    <updated>2014-10-21T21:55:43Z</updated>
  44.  <title>twitter: Excellent show from @AnnieEvemusic tonight. I cannot emphasise enough how much you should be listening to her</title></entry>
  45.  <entry>
  46.    
  47.    <link rel="alternate" href="https://twitter.com/davorg/status/524592388623187969" type="text/html"/>
  48.    <content type="xhtml">
  49.      <div xmlns="http://www.w3.org/1999/xhtml">RT @mizzlecrizzle: URGENT: Brian Harvey currently outside of Downing Street with a ring binder demanding to see the prime minister http://t…</div>
  50.    </content>
  51.    <updated>2014-10-21T16:05:46Z</updated>
  52.  <title>twitter: RT @mizzlecrizzle: URGENT: Brian Harvey currently outside of Downing Street with a ring binder demanding to see the prime minister http://t…</title></entry>
  53.  <entry>
  54.    <title>last.fm: CHVRCHES – Science/Visions</title>
  55.    <link rel="alternate" href="http://www.last.fm/music/CHVRCHES/_/Science%2FVisions" type="text/html"/>
  56.    <content type="xhtml">
  57.      <div xmlns="http://www.w3.org/1999/xhtml">http://www.last.fm/music/CHVRCHES</div>
  58.    </content>
  59.    <id>http://www.last.fm/user/davorg#1413907061</id>
  60.    <published>2014-10-21T15:57:41Z</published>
  61.    <updated>2014-10-21T15:57:41Z</updated>
  62.  </entry>
  63.  <entry>
  64.    <title>last.fm: CHVRCHES – Night Sky</title>
  65.    <link rel="alternate" href="http://www.last.fm/music/CHVRCHES/_/Night+Sky" type="text/html"/>
  66.    <content type="xhtml">
  67.      <div xmlns="http://www.w3.org/1999/xhtml">http://www.last.fm/music/CHVRCHES</div>
  68.    </content>
  69.    <id>http://www.last.fm/user/davorg#1413906831</id>
  70.    <published>2014-10-21T15:53:51Z</published>
  71.    <updated>2014-10-21T15:53:51Z</updated>
  72.  </entry>
  73.  <entry>
  74.    <title>last.fm: CHVRCHES – Recover</title>
  75.    <link rel="alternate" href="http://www.last.fm/music/CHVRCHES/_/Recover" type="text/html"/>
  76.    <content type="xhtml">
  77.      <div xmlns="http://www.w3.org/1999/xhtml">http://www.last.fm/music/CHVRCHES</div>
  78.    </content>
  79.    <id>http://www.last.fm/user/davorg#1413906347</id>
  80.    <published>2014-10-21T15:45:47Z</published>
  81.    <updated>2014-10-21T15:45:47Z</updated>
  82.  </entry>
  83.  <entry>
  84.    <title>last.fm: CHVRCHES – Under The Tide</title>
  85.    <link rel="alternate" href="http://www.last.fm/music/CHVRCHES/_/Under+The+Tide" type="text/html"/>
  86.    <content type="xhtml">
  87.      <div xmlns="http://www.w3.org/1999/xhtml">http://www.last.fm/music/CHVRCHES</div>
  88.    </content>
  89.    <id>http://www.last.fm/user/davorg#1413906074</id>
  90.    <published>2014-10-21T15:41:14Z</published>
  91.    <updated>2014-10-21T15:41:14Z</updated>
  92.  </entry>
  93.  <entry>
  94.    <title>last.fm: CHVRCHES – Lies</title>
  95.    <link rel="alternate" href="http://www.last.fm/music/CHVRCHES/_/Lies" type="text/html"/>
  96.    <content type="xhtml">
  97.      <div xmlns="http://www.w3.org/1999/xhtml">http://www.last.fm/music/CHVRCHES</div>
  98.    </content>
  99.    <id>http://www.last.fm/user/davorg#1413905854</id>
  100.    <published>2014-10-21T15:37:34Z</published>
  101.    <updated>2014-10-21T15:37:34Z</updated>
  102.  </entry>
  103.  <entry xmlns:media="http://search.yahoo.com/mrss/">
  104.    <id>tag:github.com,2008:PushEvent/2335549945</id>
  105.    <published>2014-10-09T20:58:26Z</published>
  106.    <updated>2014-10-09T20:58:26Z</updated>
  107.    <link type="text/html" rel="alternate" href="https://github.com/davorg/hipsterperl/compare/2c57660cfc...df94ad49a4"/>
  108.    
  109.    <author>
  110.      <name>davorg</name>
  111.      <email>dave@perlhacks.com</email>
  112.      <uri>https://github.com/davorg</uri>
  113.    </author>
  114.    <media:thumbnail height="30" width="30" url="https://avatars0.githubusercontent.com/u/24642?v=2&amp;s=30"/>
  115.    <content type="html">&lt;!-- push --&gt;
  116. &lt;span class="mega-octicon octicon-git-commit"&gt;&lt;/span&gt;
  117.  
  118. &lt;div class="time"&gt;
  119.  &lt;time datetime="2014-10-09T20:58:26Z" is="relative-time"&gt;Oct 9, 2014&lt;/time&gt;
  120. &lt;/div&gt;
  121.  
  122. &lt;div class="title"&gt;
  123.  &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;
  124. &lt;/div&gt;
  125.  
  126. &lt;div class="details"&gt;
  127.  &lt;a href="https://github.com/davorg"&gt;&lt;img alt="Dave Cross" class="gravatar" data-user="24642" height="30" src="https://avatars1.githubusercontent.com/u/24642?v=2&amp;amp;s=60" width="30" /&gt;&lt;/a&gt;
  128.  
  129.    &lt;div class="commits pusher-is-only-committer"&gt;
  130.      &lt;ul&gt;
  131.        &lt;li&gt;
  132.          &lt;span title="davorg"&gt;
  133.            &lt;img alt="Dave Cross" data-user="24642" height="16" src="https://avatars0.githubusercontent.com/u/24642?v=2&amp;amp;s=32" width="16" /&gt;
  134.          &lt;/span&gt;
  135.          &lt;code&gt;&lt;a href="/davorg/hipsterperl/commit/df94ad49a4f200b7c1cb3025c078cd41c8ec1953"&gt;df94ad4&lt;/a&gt;&lt;/code&gt;
  136.          &lt;div class="message"&gt;
  137.            &lt;blockquote&gt;
  138.              Starting to fill in details.
  139.            &lt;/blockquote&gt;
  140.          &lt;/div&gt;
  141.        &lt;/li&gt;
  142.        &lt;li&gt;
  143.          &lt;span title="davorg"&gt;
  144.            &lt;img alt="Dave Cross" data-user="24642" height="16" src="https://avatars0.githubusercontent.com/u/24642?v=2&amp;amp;s=32" width="16" /&gt;
  145.          &lt;/span&gt;
  146.          &lt;code&gt;&lt;a href="/davorg/hipsterperl/commit/224e2899ffd6ada951b0450d85a4ceea301be1b7"&gt;224e289&lt;/a&gt;&lt;/code&gt;
  147.          &lt;div class="message"&gt;
  148.            &lt;blockquote&gt;
  149.              Changed the logos to onions.
  150.            &lt;/blockquote&gt;
  151.          &lt;/div&gt;
  152.        &lt;/li&gt;
  153.        &lt;li class="more"&gt;&lt;a href="https://github.com/davorg/hipsterperl/compare/2c57660cfc...df94ad49a4"&gt;View comparison for these 2 commits &amp;raquo;&lt;/a&gt;&lt;/li&gt;
  154.      &lt;/ul&gt;
  155.    &lt;/div&gt;
  156. &lt;/div&gt;
  157. </content>
  158.  <title>github: davorg pushed to gh-pages at davorg/hipsterperl</title></entry>
  159.  <entry xmlns:media="http://search.yahoo.com/mrss/">
  160.    <id>tag:github.com,2008:IssueCommentEvent/2326760477</id>
  161.    <published>2014-10-06T08:34:56Z</published>
  162.    <updated>2014-10-06T08:34:56Z</updated>
  163.    <link type="text/html" rel="alternate" href="https://github.com/THEMA-MEDIA/CPAN-foolishness/issues/1#issuecomment-57988086"/>
  164.    
  165.    <author>
  166.      <name>davorg</name>
  167.      <email>dave@perlhacks.com</email>
  168.      <uri>https://github.com/davorg</uri>
  169.    </author>
  170.    <media:thumbnail height="30" width="30" url="https://avatars0.githubusercontent.com/u/24642?v=2&amp;s=30"/>
  171.    <content type="html">&lt;!-- issue_comment --&gt;
  172. &lt;span class="mega-octicon octicon-comment-discussion"&gt;&lt;/span&gt;
  173.  
  174. &lt;div class="time"&gt;
  175.  &lt;time datetime="2014-10-06T08:34:56Z" is="relative-time"&gt;Oct 6, 2014&lt;/time&gt;
  176. &lt;/div&gt;
  177.  
  178. &lt;div class="title"&gt;
  179.  &lt;a href="https://github.com/davorg"&gt;davorg&lt;/a&gt; &lt;span&gt;commented&lt;/span&gt; on issue &lt;a href="https://github.com/THEMA-MEDIA/CPAN-foolishness/issues/1#issuecomment-57988086" title="This looks like spam"&gt;THEMA-MEDIA/CPAN-foolishness#1&lt;/a&gt;
  180. &lt;/div&gt;
  181.  
  182. &lt;div class="details"&gt;
  183.  &lt;a href="https://github.com/davorg"&gt;&lt;img alt="Dave Cross" class="gravatar" data-user="24642" height="30" src="https://avatars1.githubusercontent.com/u/24642?v=2&amp;amp;s=60" width="30" /&gt;&lt;/a&gt;
  184.  &lt;div class="message markdown-body"&gt;
  185.    &lt;blockquote&gt;
  186.      &lt;p&gt;Theo, Probably best to just remove this until you have something useful to put there. Currently, you jsut seem to run the risk of annoying people. …&lt;/p&gt;
  187.    &lt;/blockquote&gt;
  188.  &lt;/div&gt;
  189. &lt;/div&gt;
  190. </content>
  191.  <title>github: davorg commented on issue THEMA-MEDIA/CPAN-foolishness#1</title></entry>
  192.  <entry>
  193.    <title>books read: How I Live Now</title>
  194.    <link rel="alternate" href="http://www.goodreads.com/review/show/1070782885?utm_medium=api&amp;utm_source=rss" type="text/html"/>
  195.    <content type="xhtml">
  196.      <div xmlns="http://www.w3.org/1999/xhtml">
  197.      
  198.      <a href="http://www.goodreads.com/book/show/18485426-how-i-live-now?utm_medium=api&amp;utm_source=rss"><img alt="How I Live Now" src="http://d.gr-assets.com/books/1379062723s/18485426.jpg"/></a><br/>
  199.                                      author: Meg Rosoff<br/>
  200.                                      name: David<br/>
  201.                                      average rating: 3.49<br/>
  202.                                      book published: 2004<br/>
  203.                                      rating: 0<br/>
  204.                                      read at: <br/>
  205.                                      date added: 2014/10/03<br/>
  206.                                      shelves: currently-reading<br/>
  207.                                      review: <br/><br/>
  208.                                      
  209.    </div>
  210.    </content>
  211.    <id>http://www.goodreads.com/review/show/1070782885?utm_medium=api&amp;utm_source=rss</id>
  212.    <published>2014-10-03T01:29:40-07:00</published>
  213.    <updated>2014-10-03T01:29:40-07:00</updated>
  214.  </entry>
  215.  <entry>
  216. <id>tag:search.cpan.org,2014-10-01:DAVECROSS:Array-Compare-2.11</id>
  217.  
  218. <link rel="alternate" type="text/html" href="http://search.cpan.org/~davecross/Array-Compare-2.11/"/>
  219. <updated>2014-10-01T20:25:16Z</updated>
  220. <author>
  221. <name>Dave Cross</name>
  222. <uri>http://search.cpan.org/~davecross/</uri>
  223. </author>
  224. <content>
  225. Perl extension for comparing arrays.
  226. </content>
  227. <title>cpan: Array-Compare-2.11</title></entry>
  228.  <entry xmlns:media="http://search.yahoo.com/mrss/">
  229.    <id>tag:github.com,2008:CreateEvent/2319763196</id>
  230.    <published>2014-10-01T20:23:04Z</published>
  231.    <updated>2014-10-01T20:23:04Z</updated>
  232.    <link type="text/html" rel="alternate" href="https://github.com/davorg/array-compare/tree/RELEASE_2.11"/>
  233.    
  234.    <author>
  235.      <name>davorg</name>
  236.      <email>dave@perlhacks.com</email>
  237.      <uri>https://github.com/davorg</uri>
  238.    </author>
  239.    <media:thumbnail height="30" width="30" url="https://avatars0.githubusercontent.com/u/24642?v=2&amp;s=30"/>
  240.    <content type="html">&lt;!-- create --&gt;
  241. &lt;div class="simple"&gt;
  242.  &lt;span class="octicon octicon-tag"&gt;&lt;/span&gt;
  243.  
  244.  &lt;div class="title"&gt;
  245.    &lt;a href="https://github.com/davorg"&gt;davorg&lt;/a&gt; &lt;span&gt;created&lt;/span&gt; tag &lt;a href="/davorg/array-compare/tree/RELEASE_2.11" class="css-truncate css-truncate-target" title="RELEASE_2.11"&gt;RELEASE_2.11&lt;/a&gt; at &lt;a href="https://github.com/davorg/array-compare" class="css-truncate css-truncate-target"&gt;davorg/array-compare&lt;/a&gt;
  246.  &lt;/div&gt;
  247.  
  248.  &lt;div class="time"&gt;
  249.    &lt;time datetime="2014-10-01T20:23:04Z" is="relative-time"&gt;Oct 1, 2014&lt;/time&gt;
  250.  &lt;/div&gt;
  251. &lt;/div&gt;
  252. </content>
  253.  <title>github: davorg created tag RELEASE_2.11 at davorg/array-compare</title></entry>
  254.  <entry xmlns:media="http://search.yahoo.com/mrss/">
  255.    <id>tag:github.com,2008:PushEvent/2319762747</id>
  256.    <published>2014-10-01T20:22:51Z</published>
  257.    <updated>2014-10-01T20:22:51Z</updated>
  258.    <link type="text/html" rel="alternate" href="https://github.com/davorg/array-compare/compare/753a3c7b02...8fbbf7a95e"/>
  259.    
  260.    <author>
  261.      <name>davorg</name>
  262.      <email>dave@perlhacks.com</email>
  263.      <uri>https://github.com/davorg</uri>
  264.    </author>
  265.    <media:thumbnail height="30" width="30" url="https://avatars0.githubusercontent.com/u/24642?v=2&amp;s=30"/>
  266.    <content type="html">&lt;!-- push --&gt;
  267. &lt;span class="mega-octicon octicon-git-commit"&gt;&lt;/span&gt;
  268.  
  269. &lt;div class="time"&gt;
  270.  &lt;time datetime="2014-10-01T20:22:51Z" is="relative-time"&gt;Oct 1, 2014&lt;/time&gt;
  271. &lt;/div&gt;
  272.  
  273. &lt;div class="title"&gt;
  274.  &lt;a href="https://github.com/davorg"&gt;davorg&lt;/a&gt; &lt;span&gt;pushed&lt;/span&gt; to &lt;a href="/davorg/array-compare/tree/master"&gt;master&lt;/a&gt; at &lt;a href="https://github.com/davorg/array-compare" class="css-truncate css-truncate-target"&gt;davorg/array-compare&lt;/a&gt;
  275. &lt;/div&gt;
  276.  
  277. &lt;div class="details"&gt;
  278.  &lt;a href="https://github.com/davorg"&gt;&lt;img alt="Dave Cross" class="gravatar" data-user="24642" height="30" src="https://avatars1.githubusercontent.com/u/24642?v=2&amp;amp;s=60" width="30" /&gt;&lt;/a&gt;
  279.  
  280.    &lt;div class="commits pusher-is-only-committer"&gt;
  281.      &lt;ul&gt;
  282.        &lt;li&gt;
  283.          &lt;span title="davorg"&gt;
  284.            &lt;img alt="Dave Cross" data-user="24642" height="16" src="https://avatars0.githubusercontent.com/u/24642?v=2&amp;amp;s=32" width="16" /&gt;
  285.          &lt;/span&gt;
  286.          &lt;code&gt;&lt;a href="/davorg/array-compare/commit/8fbbf7a95e2878b41520a26c7b901d57c40cbad0"&gt;8fbbf7a&lt;/a&gt;&lt;/code&gt;
  287.          &lt;div class="message"&gt;
  288.            &lt;blockquote&gt;
  289.              Finish removing Moose
  290.            &lt;/blockquote&gt;
  291.          &lt;/div&gt;
  292.        &lt;/li&gt;
  293.        &lt;li&gt;
  294.          &lt;span title="davorg"&gt;
  295.            &lt;img alt="Dave Cross" data-user="24642" height="16" src="https://avatars0.githubusercontent.com/u/24642?v=2&amp;amp;s=32" width="16" /&gt;
  296.          &lt;/span&gt;
  297.          &lt;code&gt;&lt;a href="/davorg/array-compare/commit/d03c3fac2a2a3f436448d277eaa06dfdcbd1c08a"&gt;d03c3fa&lt;/a&gt;&lt;/code&gt;
  298.          &lt;div class="message"&gt;
  299.            &lt;blockquote&gt;
  300.              File permission fixes
  301.            &lt;/blockquote&gt;
  302.          &lt;/div&gt;
  303.        &lt;/li&gt;
  304.        &lt;li class="more"&gt;&lt;a href="https://github.com/davorg/array-compare/compare/753a3c7b02...8fbbf7a95e"&gt;View comparison for these 2 commits &amp;raquo;&lt;/a&gt;&lt;/li&gt;
  305.      &lt;/ul&gt;
  306.    &lt;/div&gt;
  307. &lt;/div&gt;
  308. </content>
  309.  <title>github: davorg pushed to master at davorg/array-compare</title></entry>
  310.  <entry xmlns:media="http://search.yahoo.com/mrss/">
  311.    <id>tag:github.com,2008:PushEvent/2318840219</id>
  312.    <published>2014-10-01T13:43:15Z</published>
  313.    <updated>2014-10-01T13:43:15Z</updated>
  314.    <link type="text/html" rel="alternate" href="https://github.com/davorg/array-compare/compare/98b520e305...753a3c7b02"/>
  315.    
  316.    <author>
  317.      <name>davorg</name>
  318.      <email>dave@perlhacks.com</email>
  319.      <uri>https://github.com/davorg</uri>
  320.    </author>
  321.    <media:thumbnail height="30" width="30" url="https://avatars0.githubusercontent.com/u/24642?v=2&amp;s=30"/>
  322.    <content type="html">&lt;!-- push --&gt;
  323. &lt;span class="mega-octicon octicon-git-commit"&gt;&lt;/span&gt;
  324.  
  325. &lt;div class="time"&gt;
  326.  &lt;time datetime="2014-10-01T13:43:15Z" is="relative-time"&gt;Oct 1, 2014&lt;/time&gt;
  327. &lt;/div&gt;
  328.  
  329. &lt;div class="title"&gt;
  330.  &lt;a href="https://github.com/davorg"&gt;davorg&lt;/a&gt; &lt;span&gt;pushed&lt;/span&gt; to &lt;a href="/davorg/array-compare/tree/master"&gt;master&lt;/a&gt; at &lt;a href="https://github.com/davorg/array-compare" class="css-truncate css-truncate-target"&gt;davorg/array-compare&lt;/a&gt;
  331. &lt;/div&gt;
  332.  
  333. &lt;div class="details"&gt;
  334.  &lt;a href="https://github.com/davorg"&gt;&lt;img alt="Dave Cross" class="gravatar" data-user="24642" height="30" src="https://avatars1.githubusercontent.com/u/24642?v=2&amp;amp;s=60" width="30" /&gt;&lt;/a&gt;
  335.  
  336.    &lt;div class="commits pusher-is-only-committer"&gt;
  337.      &lt;ul&gt;
  338.        &lt;li&gt;
  339.          &lt;span title="davorg"&gt;
  340.            &lt;img alt="Dave Cross" data-user="24642" height="16" src="https://avatars0.githubusercontent.com/u/24642?v=2&amp;amp;s=32" width="16" /&gt;
  341.          &lt;/span&gt;
  342.          &lt;code&gt;&lt;a href="/davorg/array-compare/commit/753a3c7b02bf2d5e8f3293231416abbf5535eb60"&gt;753a3c7&lt;/a&gt;&lt;/code&gt;
  343.          &lt;div class="message"&gt;
  344.            &lt;blockquote&gt;
  345.              Ported from Moose to Moo
  346.            &lt;/blockquote&gt;
  347.          &lt;/div&gt;
  348.        &lt;/li&gt;
  349.      &lt;/ul&gt;
  350.    &lt;/div&gt;
  351. &lt;/div&gt;
  352. </content>
  353.  <title>github: davorg pushed to master at davorg/array-compare</title></entry>
  354.  <entry>
  355. <id>tag:search.cpan.org,2014-10-01:DAVECROSS:Array-Compare-2.10</id>
  356.  
  357. <link rel="alternate" type="text/html" href="http://search.cpan.org/~davecross/Array-Compare-2.10/"/>
  358. <updated>2014-10-01T13:42:56Z</updated>
  359. <author>
  360. <name>Dave Cross</name>
  361. <uri>http://search.cpan.org/~davecross/</uri>
  362. </author>
  363. <content>
  364. Perl extension for comparing arrays.
  365. </content>
  366. <title>cpan: Array-Compare-2.10</title></entry>
  367.  <entry>
  368.    <title>perl hacks: Perl’s Problems</title>
  369.    <link rel="alternate" href="http://perlhacks.com/2014/09/perls-problems/" type="text/html"/>
  370.    <content type="xhtml">
  371.      <div xmlns="http://www.w3.org/1999/xhtml"><p>It’s been over six weeks since I wrote my blog post on <a href="http://perlhacks.com/2014/08/perl-usage/">Perl usage</a>. I really didn’t mean to leave it so long to write the follow-up. But real life intervened and I haven’t had time for much blogging. That’s still the case (I should be writing a talk right now) but I thought it was worth jotting down some quick notes about what I think is causing Perl’s decline.</p>
  372. <h2>Reputation</h2>
  373. <p>We have a lot to thank Matt Wright for. And I don’t mean that sarcastically. A lot of the popularity of Perl in the mid-90s stems directly from people like Matt and Selena Sol making their collections  of CGI programs available really early on. The popularity of their programs made Perl the de-facto standard for CGI programming.</p>
  374. <p>But that was a double-edged sword. People searching the web for examples of CGI programming found Matt or Selena’s code and assumed they represented best practice. Which, of course, they didn’t. While people were blithely copying Matt’s programming style, good Perl programmers were using CGI.pm to parse their incoming parameters and separating their HTML generation out into templates.</p>
  375. <p>In my previous post, I mentioned that fifteen or twenty years ago Perl was the programming language of choice for internet start-ups. That’s true, but a lot of the code written at that time was in the Matt Wright style. Matt’s style just about works for a guestbook or a form mailer. But when you try to build a business on top of code like that, it quickly becomes obvious that it’s an unmaintainable mess.</p>
  376. <p>Many of the technical architects and CTOs who are making decisions about technology in companies today are the programmers who spent too many late nights battling those balls of mud in the 1990s. They were never really Perl programmers, they were only using it because it was fashionable, and they haven’t been keeping up with recent advances in Perl so it’s not surprising that they often choose to avoid using Perl.</p>
  377. <h2>Complexity</h2>
  378. <p>A lot of Perl’s reputation as executable line noise is completely unwarranted. The people who were writing those 1990s balls of mud were under such pressure to deliver that they would have almost certainly delivered something just as unmaintainable whatever language they were using. But some of that reputation is fair. I’ve been teaching Perl for almost fifteen years and I know that there are some parts of Perl that people find confusing. Here are some examples:</p>
  379. <p><em>Sigils</em> – I can explain things like <tt>@array</tt>, <tt>$array[$key]</tt> and even <tt>@array[@keys]</tt> to people. And most of them get it. But it takes them a while. And then it all goes to pieces again when I have to explain the difference between <tt>$array[$key]</tt> and <tt>$array-&gt;[$key]</tt>.</p>
  380. <p><em>Context</em> – Does any other programming language have the concept of context? Yes, when used correctly it’s a powerful tool. But it’s hard to explain and a good source of hard-to-find bugs. Can anyone honestly say that they haven’t been bitten by a context bug at some point in the last years?</p>
  381. <p><em>Data Structures</em> – Is the difference between arrays and array references really necessary? Think of all the complexity that is added because you can’t just pass arrays and hashes into subroutines without being bitten by list flattening. As experienced Perl programmers we know the problems and our brains are hard-wired to work around it. But other languages treat all aggregate data structures as references and it all becomes a lot easier.</p>
  382. <p>I know that each of these features (and half a dozen other examples I could list) makes Perl a richer and more expressive language. But this comes at the cost of learnability and readability. Perhaps that trade-off once seemed like a good idea. When you’re trying to encourage people to look at your language then the advantages seem less obvious.</p>
  383. <p>Of course, none of these features can be changed as they would break pretty much every existing Perl codebase. Which would be a terrible idea. But you can get away with a lot more breakage when you increase your major version number. Which Perl hasn’t been able to do for fourteen years.</p>
  384. <h2>Perl 6</h2>
  385. <p>I need to be clear here. I think that Perl 6 looks like a great language. I am really looking forward to using on production systems. And it looks like the current Perl 6 team are doing great work towards making that possible. In fact I think that our best approach to reviving Perl’s fortunes is to get a production-ready version of Perl 6 out and to make a big noise about that.</p>
  386. <p>However, that name has been a big problem.</p>
  387. <p>Looking from outside the Perl echo chamber, it’s easy to believe that Perl hasn’t had a major release for twenty years. And that can probably explain a lot of Perl’s current problems.</p>
  388. <p>I know that people who believe that are wrong. The current version of Perl (5.20.1 as I write this) is a lot different to the version that was current when Perl 6 was first announced (which was 5.6.0, I think). Perl has gone through huge changes in the last fourteen years. But the version number hides that.</p>
  389. <p>I also know that we no longer tell people that Perl 6 is the next version of Perl. The <a href="http://en.wikipedia.org/wiki/Perl_6">Wikipedia page</a> makes it clear in its first sentence that “Perl 6 is a member of the <a title="Perl" href="http://en.wikipedia.org/wiki/Perl">Perl</a> family of <a title="Programming language" href="http://en.wikipedia.org/wiki/Programming_language">programming languages</a>“. So why do people continue to think it’s the next version of Perl? Well, probably because people assume that they know how software version numbers work and don’t bother to check the web site to see it a particular project has changed the standard meaning that has worked well for decades.</p>
  390. <p>So Perl 6 has been simultaneously both good and bad for Perl. Good because a lot of Perl 6 ideas have been backported into Perl 5. But bad because Perl 5 has been unable to change its major version number in order to advertise these improvements to the wider software-using world.</p>
  391. <p>Nothing can be done about this now. The damage is done. As I said at the start of this section, it’s likely that the only thing we can do is to bet heavily on Perl 6 and get it out as soon as possible. Perl 5 will continue to exist. People will continue to maintain and improve it. Some companies will continue to use it. But it’s usage will continue to fall. I really think it’s too late to do anything about that.</p>
  392. <p>The post <a rel="nofollow" href="http://perlhacks.com/2014/09/perls-problems/">Perl’s Problems</a> appeared first on <a rel="nofollow" href="http://perlhacks.com">Perl Hacks</a>.</p>
  393. </div>
  394.    </content>
  395.    <summary type="xhtml">
  396.      <div xmlns="http://www.w3.org/1999/xhtml"><p>It’s been over six weeks since I wrote my blog post on Perl usage. I really didn’t mean to leave it so long to write the follow-up. But real life intervened and I haven’t had time for much blogging. That’s still the case (I should be writing a talk right now) but I thought it […]</p>
  397. <p>The post <a rel="nofollow" href="http://perlhacks.com/2014/09/perls-problems/">Perl’s Problems</a> appeared first on <a rel="nofollow" href="http://perlhacks.com">Perl Hacks</a>.</p>
  398. </div>
  399.    </summary>
  400.    <author>
  401.      <name>Dave Cross</name>
  402.    </author>
  403.    <id>http://perlhacks.com/?p=972</id>
  404.    <published>2014-09-28T10:22:36Z</published>
  405.    <updated>2014-09-28T10:22:36Z</updated>
  406.    <category term="Programming"/>
  407.    <category term="perl"/>
  408.    <category term="problems"/>
  409.    <category term="usage"/>
  410.  </entry>
  411.  <entry>
  412.    <title>perl hacks: “I Do Not Want To Use Any Modules”</title>
  413.    <link rel="alternate" href="http://perlhacks.com/2014/09/want-use-modules/" type="text/html"/>
  414.    <content type="xhtml">
  415.      <div xmlns="http://www.w3.org/1999/xhtml"><p>Almost every day on the Perl groups on LinkedIn (or Facebook, or StackOverflow, or somewhere like that) I see a question that includes the restriction “I do not want to use any modules”.</p>
  416. <p>There was one on LinkedIn yesterday. He wanted to create a MIME message to pass to sendmail, but he didn’t want to install any modules. Because “getting a module installed will have to go though a long long process of approvals”.</p>
  417. <p>And I understand that. I really do. We’ve all seen places where getting new software installed is a problem. But I see that problem as a bug in the development process. A bug that needs to be fixed before anything can get done in a reasonable manner. Here’s what I’ve just written in reply:</p>
  418. <blockquote><p>Of course it can be achieved without modules. Just create an email in the correct format and pass it to sendmail.</p>
  419. <p>Ah, but what’s the right format? Well, that is (of course) the tricky bit. I have no idea what the correct format is. Oh, I could Google a bit and come up with some ideas. I might even find the RFC that defines the MIME format. And then I’d be able to knock up some code that created something that looked like it would work. But would I be sure that it works? In every case? With all the weird corner-cases that people might throw at it?</p>
  420. <p>This is where CPAN modules come in handy. You’re using someone else’s knowledge. Someone who is (hopefully) an expert in the field. And because modules are used by lots of people, bugs get found and fixed.</p>
  421. <p>A lot of modern Perl programming is about choosing the right set of CPAN modules and plumbing them together. That’s what makes Perl so powerful. That’s what makes Perl programmers so efficient. We’re standing on the shoulders of giants and re-using other people’s code.</p>
  422. <p>If you’re not going to use CPAN then you might as well use shell-scripting or awk.</p>
  423. <p>If you’re in a situation where getting CPAN modules installed is hard, then fixing that problem should be your first priority. Because that’s a big impediment to your Perl programming. And investing time in fixing that will be massively beneficial to you in a very short amount of time.</p></blockquote>
  424. <p>The obvious solution is to install your own module tree (alongside your own Perl) as part of your application. But that might be overkill in some situations, so you could also consider using the system Perl and asking your sysadmin to <a href="http://perlhacks.com/2014/03/installing-modules/">install packages from your distribution’s repositories</a>. Of course, that might need a change in process. But it’s a change that is well worth making; a change that will improve your (programming) life immensely.</p>
  425. <p><strong>Update:</strong> Some very interesting discussion about this <a href="http://www.reddit.com/r/perl/comments/2h1z7i/i_do_not_want_to_use_any_modules/">over on Reddit</a>.</p>
  426. <p>The post <a rel="nofollow" href="http://perlhacks.com/2014/09/want-use-modules/">“I Do Not Want To Use Any Modules”</a> appeared first on <a rel="nofollow" href="http://perlhacks.com">Perl Hacks</a>.</p>
  427. </div>
  428.    </content>
  429.    <summary type="xhtml">
  430.      <div xmlns="http://www.w3.org/1999/xhtml"><p>Almost every day on the Perl groups on LinkedIn (or Facebook, or StackOverflow, or somewhere like that) I see a question that includes the restriction “I do not want to use any modules”. There was one on LinkedIn yesterday. He wanted to create a MIME message to pass to sendmail, but he didn’t want to install […]</p>
  431. <p>The post <a rel="nofollow" href="http://perlhacks.com/2014/09/want-use-modules/">“I Do Not Want To Use Any Modules”</a> appeared first on <a rel="nofollow" href="http://perlhacks.com">Perl Hacks</a>.</p>
  432. </div>
  433.    </summary>
  434.    <author>
  435.      <name>Dave Cross</name>
  436.    </author>
  437.    <id>http://perlhacks.com/?p=967</id>
  438.    <published>2014-09-21T10:33:48Z</published>
  439.    <updated>2014-09-21T10:33:48Z</updated>
  440.    <category term="Programming"/>
  441.    <category term="cpan"/>
  442.    <category term="programming"/>
  443.  </entry>
  444.  <entry>
  445. <id>tag:search.cpan.org,2014-09-15:DAVECROSS:WWW-Shorten-3.06</id>
  446.  
  447. <link rel="alternate" type="text/html" href="http://search.cpan.org/~davecross/WWW-Shorten-3.06/"/>
  448. <updated>2014-09-15T20:43:08Z</updated>
  449. <author>
  450. <name>Dave Cross</name>
  451. <uri>http://search.cpan.org/~davecross/</uri>
  452. </author>
  453. <content>
  454. Interface to URL shortening sites.
  455. </content>
  456. <title>cpan: WWW-Shorten-3.06</title></entry>
  457.  <entry>
  458.    <title>perl hacks: Perl Usage</title>
  459.    <link rel="alternate" href="http://perlhacks.com/2014/08/perl-usage/" type="text/html"/>
  460.    <content type="html">&lt;p&gt;In my last blog post, I &lt;a href="http://perlhacks.com/2014/07/programming-language-usage/"&gt;posted a graph&lt;/a&gt; showing that out of 135 companies at a recent &lt;a href="https://www.siliconmilkroundabout.com/"&gt;Silicon MilkRoundabout&lt;/a&gt; recruitment event, only one said that they were using Perl. That has led to some interesting discussions that I&amp;#8217;d like to address here.&lt;/p&gt;
  461. &lt;p&gt;I should make it clear that I wasn&amp;#8217;t presenting my graph as evidence that Perl is dead. Of course you can&amp;#8217;t leap to conclusions like that from what I learned at one recruitment event. I do, however, think that the situation is pretty grim.&lt;/p&gt;
  462. &lt;p&gt;But firstly, a few points that people made to me in response to my post.&lt;/p&gt;
  463. &lt;p&gt;&lt;strong&gt;We know that Perl isn&amp;#8217;t used in start-ups&lt;/strong&gt;&lt;br /&gt;
  464. Yes. I think we do know that. But I don&amp;#8217;t think we&amp;#8217;re as worried about that as we should be. Imagine if that job fair was held fifteen years ago. Or twenty years ago. Perl used to be the language of choice for internet start-ups. What happened to change that? (I have some theories that I&amp;#8217;ll cover in another blog post) Can this trend be reversed? (Honestly, I don&amp;#8217;t think so &amp;#8211; but I&amp;#8217;m open to arguments to the contrary)&lt;/p&gt;
  465. &lt;p&gt;&lt;strong&gt;Every programmer I know uses Perl in some way&lt;/strong&gt;&lt;br /&gt;
  466. I think this might have been true fifteen years ago, but it hasn&amp;#8217;t been the case for some time. If it&amp;#8217;s really true that all programmers that you know still use Perl, then I think you only know a really bizarre cross-section of programmers.&lt;/p&gt;
  467. &lt;p&gt;&lt;strong&gt;All companies use Perl, but the HR department or management often don&amp;#8217;t know&lt;/strong&gt;&lt;br /&gt;
  468. This is similar to the last point. And, again, I think it&amp;#8217;s something that used to be true and hasn&amp;#8217;t really been true this millennium. But there&amp;#8217;s also the idea of Perl being the programmers &amp;#8220;secret weapon&amp;#8221; that the suits don&amp;#8217;t know about. Even if it&amp;#8217;s true (and I don&amp;#8217;t think it is), then going underground like that is likely to be harmful to Perl&amp;#8217;s popularity in the long term.&lt;/p&gt;
  469. &lt;p&gt;I think we should stop fooling ourselves here. Perl usage has been declining for over a decade. To a first level of of approximation, Perl is already a dead language.&lt;/p&gt;
  470. &lt;p&gt;Of course, The Perl community has spent a lot of the last few years actively denying that. I&amp;#8217;ve been responsible for some of that drum-beating myself. But we need to accept that it&amp;#8217;s true. For most people outside of the Perl bubble, Perl is a language that they last considered using back in the last millennium.&lt;/p&gt;
  471. &lt;p&gt;So, if Perl is dead, why has everyone spent the last five years demonstrating that this isn&amp;#8217;t the case? Have they been lying to us? No, I don&amp;#8217;t think they have. I just think that they have been looking at the wrong measures of success. Let&amp;#8217;s look at some of the arguments I&amp;#8217;ve seen.&lt;/p&gt;
  472. &lt;p&gt;&lt;strong&gt;CPAN is growing faster than ever&lt;/strong&gt;&lt;br /&gt;
  473. &lt;strong&gt;We have regular releases of Perl&lt;/strong&gt;&lt;br /&gt;
  474. &lt;strong&gt;Some great new features have been added to Perl&lt;/strong&gt;&lt;br /&gt;
  475. These all essentially boil down to the same argument &amp;#8211; &amp;#8220;Perl isn&amp;#8217;t dead because some part of Perl (or its ecosystem) is improving&amp;#8221;. I can&amp;#8217;t argue with any of those facts, but do they really say anything useful about the long-term viability of the language. It&amp;#8217;s great that Perl is constantly improving, but unless the people who are currently ignoring Perl can be persuaded to investigate these improvements, then they do little or nothing to stop Perl&amp;#8217;s decline.&lt;/p&gt;
  476. &lt;p&gt;Moose might be the most powerful object system in the world. DBIx::Class might be the most flexible ORM available. Projects like these are great. But they don&amp;#8217;t seem to be doing much to bring new people to Perl.&lt;/p&gt;
  477. &lt;p&gt;&lt;strong&gt;There are more YAPCs and Perl Workshops every year&lt;/strong&gt;&lt;br /&gt;
  478. &lt;strong&gt;Perl Mongers groups are starting all the time&lt;/strong&gt;&lt;br /&gt;
  479. &lt;strong&gt;We get dozens of people to our meetings every month&lt;/strong&gt;&lt;br /&gt;
  480. These arguments all boil down to &amp;#8220;the Perl community is growing&amp;#8221;. Again, I can&amp;#8217;t argue with those facts (well, to be honest, I think the rate of Perl Monger group creation has slowed over the last ten years) but, again, I don&amp;#8217;t think they prove what their proponents think they prove.&lt;/p&gt;
  481. &lt;p&gt;There is a difference between the Perl community and Perl programmers. Everywhere that I work, I find people who I already know from the community. But I always find far more people who I don&amp;#8217;t know because they aren&amp;#8217;t at all engaged with the Perl community. And I think it&amp;#8217;s that large, untapped, number of non-community Perl programmers who make up the increased numbers of people attending meetings or conferences. This means that we are getting better at bringing our colleagues along to meetings. It doesn&amp;#8217;t mean that more people are using Perl.&lt;/p&gt;
  482. &lt;p&gt;&lt;strong&gt;The number of Perl jobs is rising&lt;/strong&gt;&lt;br /&gt;
  483. &lt;strong&gt;Our company can never find enough Perl programmers&lt;/strong&gt;&lt;br /&gt;
  484. &lt;strong&gt;We just started a major new project using Perl&lt;/strong&gt;&lt;br /&gt;
  485. Most of the companies who use Perl continue to use Perl. That&amp;#8217;s not really news. And some of those companies have grown really big and therefore need lots of Perl programmers to maintain and enhance their Perl programs. And that&amp;#8217;s great. But it&amp;#8217;s not really evidence of a grow in Perl usage.&lt;/p&gt;
  486. &lt;p&gt;Not all the companies who have historically used Perl continue to do so. Over the last five years I know of at least four big Perl-using companies in London who have started to move away from it for new development.&lt;/p&gt;
  487. &lt;p&gt;And one reason why people are always looking for Perl programmers is because many programmers have chosen to move away from Perl. I know plenty of people who were regulars at London Perl Mongers meetings ten to fifteen years ago but who haven&amp;#8217;t written a line of Perl for over five years. This means, of course, that there is more work to go round those of us who are left. I could probably go through to my retirement maintaining existing Perl codebases. Those of you who are younger than me might not be so lucky.&lt;/p&gt;
  488. &lt;p&gt;&amp;nbsp;&lt;/p&gt;
  489. &lt;p&gt;So, to summarise, people who say that Perl is thriving point to three things &amp;#8211; technical advances in Perl, the vibrant Perl community and the number of unfilled Perl jobs that always seem to be around. All of these things are great and are, of course, necessary for a living and growing language.&lt;/p&gt;
  490. &lt;p&gt;But they aren&amp;#8217;t sufficient. You also need people outside of the community to take notice. And that&amp;#8217;s not happening.&lt;/p&gt;
  491. &lt;p&gt;Ask yourself three questions.&lt;/p&gt;
  492. &lt;ol&gt;
  493. &lt;li&gt;When did you last read a book on general programming techniques that contained examples written in Perl?&lt;/li&gt;
  494. &lt;li&gt;When did you last read documentation for a web site&amp;#8217;s API that included examples written in Perl?&lt;/li&gt;
  495. &lt;li&gt;When did you last hear of a company using Perl that you didn&amp;#8217;t previously know about?&lt;/li&gt;
  496. &lt;/ol&gt;
  497. &lt;p&gt;This is why I published that graph a couple of weeks ago. Looking at that data, it really hit home to me just how badly we&amp;#8217;re doing.&lt;/p&gt;
  498. &lt;p&gt;I have a couple of theories about why most of the world started ignoring Perl. I&amp;#8217;ll get to those in my next blog posts. But, annoyingly, I don&amp;#8217;t have any good ideas about how we might reverse the situation.&lt;/p&gt;
  499. &lt;p&gt;To be honest, currently my best advice (and the course I&amp;#8217;ll be taking) is &amp;#8220;brush up your Javascript&amp;#8221;.&lt;/p&gt;
  500. &lt;p&gt;&amp;nbsp;&lt;/p&gt;
  501. &lt;p&gt;The post &lt;a rel="nofollow" href="http://perlhacks.com/2014/08/perl-usage/"&gt;Perl Usage&lt;/a&gt; appeared first on &lt;a rel="nofollow" href="http://perlhacks.com"&gt;Perl Hacks&lt;/a&gt;.&lt;/p&gt;
  502. </content>
  503.    <summary type="xhtml">
  504.      <div xmlns="http://www.w3.org/1999/xhtml"><p>In my last blog post, I posted a graph showing that out of 135 companies at a recent Silicon MilkRoundabout recruitment event, only one said that they were using Perl. That has led to some interesting discussions that I’d like to address here. I should make it clear that I wasn’t presenting my graph as […]</p>
  505. <p>The post <a rel="nofollow" href="http://perlhacks.com/2014/08/perl-usage/">Perl Usage</a> appeared first on <a rel="nofollow" href="http://perlhacks.com">Perl Hacks</a>.</p>
  506. </div>
  507.    </summary>
  508.    <author>
  509.      <name>Dave Cross</name>
  510.    </author>
  511.    <id>http://perlhacks.com/?p=953</id>
  512.    <published>2014-08-10T16:43:11Z</published>
  513.    <updated>2014-08-10T16:43:11Z</updated>
  514.    <category term="Programming"/>
  515.    <category term="perl"/>
  516.    <category term="usage"/>
  517.  </entry>
  518.  <entry>
  519.    <title>perl hacks: Programming Language Usage</title>
  520.    <link rel="alternate" href="http://perlhacks.com/2014/07/programming-language-usage/" type="text/html"/>
  521.    <content type="xhtml">
  522.      <div xmlns="http://www.w3.org/1999/xhtml"><p>Back in May, I spent an afternoon at <a href="https://www.siliconmilkroundabout.com/">Silicon MilkRoundabout</a>. Silicon MilkRoundabout is a recruitment fair for techies. It’s specifically aimed at people who want to work for start-ups around the Old Street area (although they aren’t particularly stringent about sticking to that – for example, the BBC were there).</p>
  523. <p>We were given a booklet containing details of all of the companies who were recruiting. Those details usually included information about the tech stack that the companies used.</p>
  524. <p>Over the weekend, I went through that booklet and listed the programming languages mentioned by the companies. The results speak for themselves.</p>
  525. <p>There were 135 companies at the event. About twenty of them unhelpfully listed their tech stack as “ask us for details”.</p>
  526. <p>Here’s the graph:<a href="http://perlhacks.com/wp-content/uploads/2014/07/graph.png"><img class="wp-image-949 size-full" src="http://perlhacks.com/wp-content/uploads/2014/07/graph.png" alt="Usage of Programming Languages by Companies at Silicon MilkRoundabout" width="600" height="500"/></a></p>
  527. <p style="text-align: center;"><em>Usage of Programming Languages by Companies at Silicon MilkRoundabout</em></p>
  528. <p>I’ll obviously have some more to say about this over the next few days. But I wanted to get the raw data out there as soon as possible.</p>
  529. <p>The post <a rel="nofollow" href="http://perlhacks.com/2014/07/programming-language-usage/">Programming Language Usage</a> appeared first on <a rel="nofollow" href="http://perlhacks.com">Perl Hacks</a>.</p>
  530. </div>
  531.    </content>
  532.    <summary type="xhtml">
  533.      <div xmlns="http://www.w3.org/1999/xhtml"><p>Back in May, I spent an afternoon at Silicon MilkRoundabout. Silicon MilkRoundabout is a recruitment fair for techies. It’s specifically aimed at people who want to work for start-ups around the Old Street area (although they aren’t particularly stringent about sticking to that – for example, the BBC were there). We were given a booklet […]</p>
  534. <p>The post <a rel="nofollow" href="http://perlhacks.com/2014/07/programming-language-usage/">Programming Language Usage</a> appeared first on <a rel="nofollow" href="http://perlhacks.com">Perl Hacks</a>.</p>
  535. </div>
  536.    </summary>
  537.    <author>
  538.      <name>Dave Cross</name>
  539.    </author>
  540.    <id>http://perlhacks.com/?p=948</id>
  541.    <published>2014-07-28T12:36:21Z</published>
  542.    <updated>2014-07-28T12:36:21Z</updated>
  543.    <category term="Programming"/>
  544.    <category term="languages"/>
  545.    <category term="programming"/>
  546.    <category term="silicon milkroundabout"/>
  547.  </entry>
  548.  <entry>
  549.    <title>perl hacks: Github, Travis-CI and Perl</title>
  550.    <link rel="alternate" href="http://perlhacks.com/2014/07/github-travis-ci-perl/" type="text/html"/>
  551.    <content type="xhtml">
  552.      <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>
  553. <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>
  554. <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>
  555. <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>
  556. <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>
  557. <p>Thanks to everyone for organising, speaking or just coming along.</p>
  558. <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>
  559. </div>
  560.    </content>
  561.    <summary type="xhtml">
  562.      <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>
  563. <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>
  564. </div>
  565.    </summary>
  566.    <author>
  567.      <name>Dave Cross</name>
  568.    </author>
  569.    <id>http://perlhacks.com/?p=935</id>
  570.    <published>2014-07-25T16:14:39Z</published>
  571.    <updated>2014-07-25T16:14:39Z</updated>
  572.    <category term="Speaking"/>
  573.    <category term="continuous integration"/>
  574.    <category term="github"/>
  575.    <category term="london"/>
  576.    <category term="london.pm"/>
  577.    <category term="techmeet"/>
  578.    <category term="travis-ci"/>
  579.  </entry>
  580.  <entry>
  581.    <title>slideshare: Github, Travis-CI and Perl</title>
  582.    <link rel="alternate" href="http://www.slideshare.net/davorg/github-travisci-and-perl" type="text/html"/>
  583.    <content type="html">
  584.        &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
  585.      </content>
  586.    <summary type="html">
  587.        &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
  588.      </summary>
  589.    <author>
  590.      <name>davorg@slideshare.net(davorg)</name>
  591.    </author>
  592.    <id>http://www.slideshare.net/davorg/github-travisci-and-perl</id>
  593.    <published>2014-07-25T10:56:17Z</published>
  594.    <updated>2014-07-25T10:56:17Z</updated>
  595.  </entry>
  596.  <entry>
  597.    <title>davblog: First Direct Update</title>
  598.    <link rel="alternate" href="http://feedproxy.google.com/~r/realdavblog/~3/NJ-sXTgM-yo/first-direct-update.html" type="text/html"/>
  599.    <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;
  600. &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;
  601. &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;
  602. &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;
  603. &lt;p&gt;&lt;script async src="//platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;&lt;/p&gt;
  604. &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;
  605. &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;
  606. &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;
  607. &lt;p&gt;&lt;script async src="//platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;&lt;/p&gt;
  608. &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;
  609. &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;
  610. &lt;p&gt;&lt;script async src="//platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;&lt;/p&gt;
  611. &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;
  612. &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;
  613. &lt;p&gt;&lt;script async src="//platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;&lt;/p&gt;
  614. &lt;p&gt;To which, I replied&lt;/p&gt;
  615. &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;
  616. &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;
  617. &lt;p&gt;&lt;script async src="//platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;&lt;/p&gt;
  618. &lt;p&gt;And got the response&lt;/p&gt;
  619. &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;
  620. &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;
  621. &lt;p&gt;&lt;script async src="//platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;&lt;/p&gt;
  622. &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;
  623. &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;
  624. &lt;p&gt;&lt;script async src="//platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;&lt;/p&gt;
  625. &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;
  626. &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;
  627. &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;
  628. &lt;p&gt;&lt;script async src="//platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;&lt;/p&gt;
  629. &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;
  630. &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;
  631. &lt;p&gt;&lt;script async src="//platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;&lt;/p&gt;
  632. &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;
  633. &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;
  634. &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;
  635. &lt;p&gt;&lt;script async src="//platform.twitter.com/widgets.js" charset="utf-8"&gt;&lt;/script&gt;&lt;/p&gt;
  636. &lt;p&gt;So, to summarise what we know.&lt;/p&gt;
  637. &lt;ul&gt;
  638. &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;
  639. &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;
  640. &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;
  641. &lt;/ul&gt;
  642. &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;
  643. &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;
  644. &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 style="clear:both"&gt;&lt;/div&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;
  645. &lt;img src="http://feeds.feedburner.com/~r/realdavblog/~4/NJ-sXTgM-yo" height="1" width="1"/&gt;</content>
  646.    <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;]
  647. &lt;div class="crp_related"&gt;
  648. &lt;h3&gt;Related Posts:&lt;/h3&gt;
  649. &lt;ul&gt;
  650. &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;
  651. &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;
  652. &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;
  653. &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;
  654. &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;
  655. &lt;/ul&gt;
  656. &lt;div style="clear:both"&gt;&lt;/div&gt;
  657. &lt;/div&gt;
  658. &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;
  659. </summary>
  660.    <author>
  661.      <name>Dave Cross</name>
  662.    </author>
  663.    <id>http://blog.dave.org.uk/?p=3378</id>
  664.    <published>2014-07-19T11:02:07Z</published>
  665.    <updated>2014-07-19T11:02:07Z</updated>
  666.    <category term="tech"/>
  667.    <category term="banking"/>
  668.    <category term="first direct"/>
  669.    <category term="passwords"/>
  670.    <category term="security"/>
  671.  </entry>
  672.  <entry>
  673.    <title>davblog: First Direct Passwords</title>
  674.    <link rel="alternate" href="http://feedproxy.google.com/~r/realdavblog/~3/VLTr8OXPipg/first-direct-passwords.html" type="text/html"/>
  675.    <content type="xhtml">
  676.      <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>
  677. <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>
  678. <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>
  679. <ol>
  680. <li>The traditional small dongle to carry around with you</li>
  681. <li>An extension to their smartphone app</li>
  682. <li>No secure key at all</li>
  683. </ol>
  684. <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>
  685. <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>
  686. <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>
  687. <p>And that’s where I think First Direct have slipped up a bit.</p>
  688. <p>When they asked my for my new password, they told me that it needed to be between 6 and 10 characters long.</p>
  689. <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>
  690. <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>
  691. <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>
  692. <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>
  693. <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>
  694. <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>
  695. <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>
  696. <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>
  697. <p>I’ve send them a message asking for clarification. I’ll update this post with any response that I get.</p>
  698. <p><strong>Update (17 July):</strong> I got a reply from First Direct. This is what they said.</p>
  699. <blockquote><p>Thank you for your message dated 16-Jul-2014 regarding the security of your password for your Digital Secure Key.</p>
  700. <p>Ensuring the security of our systems is, and will continue to be, our number one priority.</p>
  701. <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>
  702. <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>
  703. <p>Please let us know if you have any further questions, and we’ll be happy to discuss.</p></blockquote>
  704. <p>Which isn’t very helpful and doesn’t address my question. I’ve tried explaining it to them again.</p>
  705. <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 style="clear:both"/></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>
  706. <img src="http://feeds.feedburner.com/~r/realdavblog/~4/VLTr8OXPipg" height="1" width="1"/></div>
  707.    </content>
  708.    <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;]
  709. &lt;div class="crp_related"&gt;
  710. &lt;h3&gt;Related Posts:&lt;/h3&gt;
  711. &lt;ul&gt;
  712. &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;
  713. &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;
  714. &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;
  715. &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;
  716. &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;
  717. &lt;/ul&gt;
  718. &lt;div style="clear:both"&gt;&lt;/div&gt;
  719. &lt;/div&gt;
  720. &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;
  721. </summary>
  722.    <author>
  723.      <name>Dave Cross</name>
  724.    </author>
  725.    <id>http://blog.dave.org.uk/?p=3372</id>
  726.    <published>2014-07-16T12:37:36Z</published>
  727.    <updated>2014-07-16T12:37:36Z</updated>
  728.    <category term="tech"/>
  729.    <category term="banking"/>
  730.    <category term="first direct"/>
  731.    <category term="password"/>
  732.    <category term="security"/>
  733.  </entry>
  734.  <entry>
  735.    <title>slideshare: Object-Oriented Programming with Perl and Moose</title>
  736.    <link rel="alternate" href="http://www.slideshare.net/davorg/objectoriented-programming-with-perl-and-moose" type="text/html"/>
  737.    <content type="html">
  738.        &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;
  739.      </content>
  740.    <summary type="html">
  741.        &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;
  742.      </summary>
  743.    <author>
  744.      <name>davorg@slideshare.net(davorg)</name>
  745.    </author>
  746.    <id>http://www.slideshare.net/davorg/objectoriented-programming-with-perl-and-moose</id>
  747.    <published>2014-07-01T10:38:12Z</published>
  748.    <updated>2014-07-01T10:38:12Z</updated>
  749.  </entry>
  750.  <entry>
  751.    <title>slideshare: Database Programming with Perl and DBIx::Class</title>
  752.    <link rel="alternate" href="http://www.slideshare.net/davorg/database-programming-with-perl-and-dbixclass" type="text/html"/>
  753.    <content type="html">
  754.        &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;
  755.      </content>
  756.    <summary type="html">
  757.        &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;
  758.      </summary>
  759.    <author>
  760.      <name>davorg@slideshare.net(davorg)</name>
  761.    </author>
  762.    <id>http://www.slideshare.net/davorg/database-programming-with-perl-and-dbixclass</id>
  763.    <published>2014-07-01T10:34:49Z</published>
  764.    <updated>2014-07-01T10:34:49Z</updated>
  765.  </entry>
  766.  <entry>
  767.    <title>books read: The Complete Works of H.P. Lovecraft</title>
  768.    <link rel="alternate" href="http://www.goodreads.com/review/show/965111614?utm_medium=api&amp;utm_source=rss" type="text/html"/>
  769.    <content type="xhtml">
  770.      <div xmlns="http://www.w3.org/1999/xhtml">
  771.      
  772.      <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/>
  773.                                      author: H.P. Lovecraft<br/>
  774.                                      name: David<br/>
  775.                                      average rating: 4.28<br/>
  776.                                      book published: 2011<br/>
  777.                                      rating: 0<br/>
  778.                                      read at: <br/>
  779.                                      date added: 2014/06/12<br/>
  780.                                      shelves: currently-reading<br/>
  781.                                      review: <br/><br/>
  782.                                      
  783.    </div>
  784.    </content>
  785.    <id>http://www.goodreads.com/review/show/965111614?utm_medium=api&amp;utm_source=rss</id>
  786.    <published>2014-06-12T01:50:30-07:00</published>
  787.    <updated>2014-06-12T01:50:30-07:00</updated>
  788.  </entry>
  789. </feed>
  790.  
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda