Sorry

This feed does not validate.

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

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

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <feed xmlns="http://www.w3.org/2005/Atom">
  3.  <title>planet davorg</title>
  4.  <link rel="alternate" href="http://davorg.theplanetarium.org/" type="text/html"/>
  5.  <subtitle>Aggregating Dave's stuff</subtitle>
  6.  <author>
  7.    <name>Dave Cross</name>
  8.    <email>[email protected]</email>
  9.  </author>
  10.  <updated>2018-06-20T07:03:06Z</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.    <summary type="xhtml">
  16.      <div xmlns="http://www.w3.org/1999/xhtml">Everything Now - Arcade Fire</div>
  17.    </summary>
  18.    <link rel="alternate" href="https://www.last.fm/music/Arcade+Fire/_/Everything+Now" type="text/html"/>
  19.    <updated>2018-06-20T06:32:46Z</updated>
  20.    <author>
  21.      <name>Arcade Fire</name>
  22.    </author>
  23.    <id>https://musicbrainz.org/recording/</id>
  24.  <title>last.fm: Everything Now - Arcade Fire</title></entry>
  25.  <entry xmlns:flickr="urn:flickr:user" xmlns:dc="http://purl.org/dc/elements/1.1/">
  26.    
  27.    <link rel="alternate" type="text/html" href="http://www.flickr.com/photos/davorg/42908141041/"/>
  28.    <id>tag:flickr.com,2005:/photo/42908141041</id>
  29.    <published>2018-06-19T22:38:42Z</published>
  30.    <updated>2018-06-19T22:38:42Z</updated>
  31.    <flickr:date_taken>2018-06-19T23:38:42-08:00</flickr:date_taken>
  32.    <dc:date.Taken>2018-06-19T23:38:42-08:00</dc:date.Taken>
  33.    <content type="html"> &lt;p&gt;&lt;a href="http://www.flickr.com/people/davorg/"&gt;Dave Cross&lt;/a&gt; posted a photo:&lt;/p&gt;
  34. &lt;p&gt;&lt;a href="http://www.flickr.com/photos/davorg/42908141041/" title="David Byrne"&gt;&lt;img src="http://farm2.staticflickr.com/1824/42908141041_d829423ba0_m.jpg" width="240" height="240" alt="David Byrne" /&gt;&lt;/a&gt;&lt;/p&gt;
  35.  
  36. &lt;p&gt;via Instagram &lt;a href="https://ift.tt/2MEPdJ2" rel="nofollow"&gt;ift.tt/2MEPdJ2&lt;/a&gt;&lt;/p&gt;</content>
  37.    <author>
  38.      <name>Dave Cross</name>
  39.      <uri>http://www.flickr.com/people/davorg/</uri>
  40.      <flickr:nsid>[email protected]</flickr:nsid>
  41.      <flickr:buddyicon>http://farm5.staticflickr.com/4759/buddyicons/[email protected]?1516110776#[email protected]</flickr:buddyicon>
  42.    </author>
  43.    <link rel="license" type="text/html" href="https://creativecommons.org/licenses/by-nc-sa/2.0/deed.en"/>
  44.    <link rel="enclosure" type="image/jpeg" href="http://farm2.staticflickr.com/1824/42908141041_d829423ba0_b.jpg"/>
  45.    <category term="ifttt" scheme="http://www.flickr.com/photos/tags/"/>
  46.    <category term="instagram" scheme="http://www.flickr.com/photos/tags/"/>
  47.    <displaycategories>
  48.            </displaycategories>
  49.    <title>flickr: David Byrne</title></entry>
  50.  <entry xmlns:flickr="urn:flickr:user" xmlns:dc="http://purl.org/dc/elements/1.1/">
  51.    
  52.    <link rel="alternate" type="text/html" href="http://www.flickr.com/photos/davorg/42859635072/"/>
  53.    <id>tag:flickr.com,2005:/photo/42859635072</id>
  54.    <published>2018-06-19T22:38:40Z</published>
  55.    <updated>2018-06-19T22:38:40Z</updated>
  56.    <flickr:date_taken>2018-06-19T23:38:40-08:00</flickr:date_taken>
  57.    <dc:date.Taken>2018-06-19T23:38:40-08:00</dc:date.Taken>
  58.    <content type="html"> &lt;p&gt;&lt;a href="http://www.flickr.com/people/davorg/"&gt;Dave Cross&lt;/a&gt; posted a photo:&lt;/p&gt;
  59. &lt;p&gt;&lt;a href="http://www.flickr.com/photos/davorg/42859635072/" title="David Byrne"&gt;&lt;img src="http://farm2.staticflickr.com/1762/42859635072_7e3f9fdd15_m.jpg" width="240" height="240" alt="David Byrne" /&gt;&lt;/a&gt;&lt;/p&gt;
  60.  
  61. &lt;p&gt;via Instagram &lt;a href="https://ift.tt/2yqSWXz" rel="nofollow"&gt;ift.tt/2yqSWXz&lt;/a&gt;&lt;/p&gt;</content>
  62.    <author>
  63.      <name>Dave Cross</name>
  64.      <uri>http://www.flickr.com/people/davorg/</uri>
  65.      <flickr:nsid>[email protected]</flickr:nsid>
  66.      <flickr:buddyicon>http://farm5.staticflickr.com/4759/buddyicons/[email protected]?1516110776#[email protected]</flickr:buddyicon>
  67.    </author>
  68.    <link rel="license" type="text/html" href="https://creativecommons.org/licenses/by-nc-sa/2.0/deed.en"/>
  69.    <link rel="enclosure" type="image/jpeg" href="http://farm2.staticflickr.com/1762/42859635072_7e3f9fdd15_b.jpg"/>
  70.    <category term="ifttt" scheme="http://www.flickr.com/photos/tags/"/>
  71.    <category term="instagram" scheme="http://www.flickr.com/photos/tags/"/>
  72.    <displaycategories>
  73.            </displaycategories>
  74.    <title>flickr: David Byrne</title></entry>
  75.  <entry xmlns:flickr="urn:flickr:user" xmlns:dc="http://purl.org/dc/elements/1.1/">
  76.    
  77.    <link rel="alternate" type="text/html" href="http://www.flickr.com/photos/davorg/42189945974/"/>
  78.    <id>tag:flickr.com,2005:/photo/42189945974</id>
  79.    <published>2018-06-19T22:38:38Z</published>
  80.    <updated>2018-06-19T22:38:38Z</updated>
  81.    <flickr:date_taken>2018-06-19T23:38:38-08:00</flickr:date_taken>
  82.    <dc:date.Taken>2018-06-19T23:38:38-08:00</dc:date.Taken>
  83.    <content type="html"> &lt;p&gt;&lt;a href="http://www.flickr.com/people/davorg/"&gt;Dave Cross&lt;/a&gt; posted a photo:&lt;/p&gt;
  84. &lt;p&gt;&lt;a href="http://www.flickr.com/photos/davorg/42189945974/" title="David Byrne"&gt;&lt;img src="http://farm2.staticflickr.com/1807/42189945974_c81e6934aa_m.jpg" width="240" height="240" alt="David Byrne" /&gt;&lt;/a&gt;&lt;/p&gt;
  85.  
  86. &lt;p&gt;via Instagram &lt;a href="https://ift.tt/2taX8G4" rel="nofollow"&gt;ift.tt/2taX8G4&lt;/a&gt;&lt;/p&gt;</content>
  87.    <author>
  88.      <name>Dave Cross</name>
  89.      <uri>http://www.flickr.com/people/davorg/</uri>
  90.      <flickr:nsid>[email protected]</flickr:nsid>
  91.      <flickr:buddyicon>http://farm5.staticflickr.com/4759/buddyicons/[email protected]?1516110776#[email protected]</flickr:buddyicon>
  92.    </author>
  93.    <link rel="license" type="text/html" href="https://creativecommons.org/licenses/by-nc-sa/2.0/deed.en"/>
  94.    <link rel="enclosure" type="image/jpeg" href="http://farm2.staticflickr.com/1807/42189945974_c81e6934aa_b.jpg"/>
  95.    <category term="ifttt" scheme="http://www.flickr.com/photos/tags/"/>
  96.    <category term="instagram" scheme="http://www.flickr.com/photos/tags/"/>
  97.    <displaycategories>
  98.            </displaycategories>
  99.    <title>flickr: David Byrne</title></entry>
  100.  <entry>
  101.    
  102.    <link rel="alternate" href="https://twitter.com/davorg/status/1009200343383793664" type="text/html"/>
  103.    <content type="xhtml">
  104.      <div xmlns="http://www.w3.org/1999/xhtml">David Byrne https://t.co/FnmxrRLlyV https://t.co/xGIpWRsdhB</div>
  105.    </content>
  106.    <updated>2018-06-19T22:24:46Z</updated>
  107.  <title>twitter: David Byrne https://t.co/FnmxrRLlyV https://t.co/xGIpWRsdhB</title></entry>
  108.  <entry>
  109.    
  110.    <link rel="alternate" href="https://twitter.com/davorg/status/1009200335980781568" type="text/html"/>
  111.    <content type="xhtml">
  112.      <div xmlns="http://www.w3.org/1999/xhtml">David Byrne https://t.co/iXOOHOBaro https://t.co/udBROLhyfe</div>
  113.    </content>
  114.    <updated>2018-06-19T22:24:44Z</updated>
  115.  <title>twitter: David Byrne https://t.co/iXOOHOBaro https://t.co/udBROLhyfe</title></entry>
  116.  <entry>
  117.    
  118.    <link rel="alternate" href="https://twitter.com/davorg/status/1009200328250707968" type="text/html"/>
  119.    <content type="xhtml">
  120.      <div xmlns="http://www.w3.org/1999/xhtml">David Byrne https://t.co/U82pnv12UP https://t.co/zuvRqxSJVf</div>
  121.    </content>
  122.    <updated>2018-06-19T22:24:42Z</updated>
  123.  <title>twitter: David Byrne https://t.co/U82pnv12UP https://t.co/zuvRqxSJVf</title></entry>
  124.  <entry>
  125.    
  126.    <summary type="xhtml">
  127.      <div xmlns="http://www.w3.org/1999/xhtml">Everything Now - Arcade Fire</div>
  128.    </summary>
  129.    <link rel="alternate" href="https://www.last.fm/music/Arcade+Fire/_/Everything+Now" type="text/html"/>
  130.    <updated>2018-06-19T22:20:44Z</updated>
  131.    <author>
  132.      <name>Arcade Fire</name>
  133.    </author>
  134.    <id>https://musicbrainz.org/recording/</id>
  135.  <title>last.fm: Everything Now - Arcade Fire</title></entry>
  136.  <entry>
  137.    
  138.    <link rel="alternate" href="https://twitter.com/davorg/status/1009195989390057474" type="text/html"/>
  139.    <content type="xhtml">
  140.      <div xmlns="http://www.w3.org/1999/xhtml">Feels like Trump wants a co-author credit for the flashback scenes in series three of The Handmaid's Tale https://t.co/DcK5i1Z3P6</div>
  141.    </content>
  142.    <updated>2018-06-19T22:07:28Z</updated>
  143.  <title>twitter: Feels like Trump wants a co-author credit for the flashback scenes in series three of The Handmaid's Tale https://t.co/DcK5i1Z3P6</title></entry>
  144.  <entry xmlns:flickr="urn:flickr:user" xmlns:dc="http://purl.org/dc/elements/1.1/">
  145.    
  146.    <link rel="alternate" type="text/html" href="http://www.flickr.com/photos/davorg/42188061644/"/>
  147.    <id>tag:flickr.com,2005:/photo/42188061644</id>
  148.    <published>2018-06-19T20:38:47Z</published>
  149.    <updated>2018-06-19T20:38:47Z</updated>
  150.    <flickr:date_taken>2018-06-19T21:38:47-08:00</flickr:date_taken>
  151.    <dc:date.Taken>2018-06-19T21:38:47-08:00</dc:date.Taken>
  152.    <content type="html"> &lt;p&gt;&lt;a href="http://www.flickr.com/people/davorg/"&gt;Dave Cross&lt;/a&gt; posted a photo:&lt;/p&gt;
  153. &lt;p&gt;&lt;a href="http://www.flickr.com/photos/davorg/42188061644/" title="Stage at the start of the David Byrne show is almost completely bare"&gt;&lt;img src="http://farm2.staticflickr.com/1822/42188061644_64f7de203f_m.jpg" width="240" height="240" alt="Stage at the start of the David Byrne show is almost completely bare" /&gt;&lt;/a&gt;&lt;/p&gt;
  154.  
  155. &lt;p&gt;via Instagram &lt;a href="https://ift.tt/2tlohW8" rel="nofollow"&gt;ift.tt/2tlohW8&lt;/a&gt;&lt;/p&gt;</content>
  156.    <author>
  157.      <name>Dave Cross</name>
  158.      <uri>http://www.flickr.com/people/davorg/</uri>
  159.      <flickr:nsid>[email protected]</flickr:nsid>
  160.      <flickr:buddyicon>http://farm5.staticflickr.com/4759/buddyicons/[email protected]?1516110776#[email protected]</flickr:buddyicon>
  161.    </author>
  162.    <link rel="license" type="text/html" href="https://creativecommons.org/licenses/by-nc-sa/2.0/deed.en"/>
  163.    <link rel="enclosure" type="image/jpeg" href="http://farm2.staticflickr.com/1822/42188061644_64f7de203f_b.jpg"/>
  164.    <category term="ifttt" scheme="http://www.flickr.com/photos/tags/"/>
  165.    <category term="instagram" scheme="http://www.flickr.com/photos/tags/"/>
  166.    <displaycategories>
  167.            </displaycategories>
  168.    <title>flickr: Stage at the start of the David Byrne show is almost completely bare</title></entry>
  169.  <entry>
  170.    
  171.    <link rel="alternate" href="https://twitter.com/davorg/status/1009170180356886529" type="text/html"/>
  172.    <content type="xhtml">
  173.      <div xmlns="http://www.w3.org/1999/xhtml">Stage at the start of the David Byrne show is almost completely bare https://t.co/t0EZr2YxOq https://t.co/ZLOBxtymVA</div>
  174.    </content>
  175.    <updated>2018-06-19T20:24:55Z</updated>
  176.  <title>twitter: Stage at the start of the David Byrne show is almost completely bare https://t.co/t0EZr2YxOq https://t.co/ZLOBxtymVA</title></entry>
  177.  <entry>
  178.    
  179.    <summary type="xhtml">
  180.      <div xmlns="http://www.w3.org/1999/xhtml">And God Created Brixton - Carter The Unstoppable Sex Machine</div>
  181.    </summary>
  182.    <link rel="alternate" href="https://www.last.fm/music/Carter+The+Unstoppable+Sex+Machine/_/And+God+Created+Brixton" type="text/html"/>
  183.    <updated>2018-06-19T17:59:34Z</updated>
  184.    <author>
  185.      <name>Carter The Unstoppable Sex Machine</name>
  186.    </author>
  187.    <id>https://musicbrainz.org/recording/ca3fd5de-e380-460c-ae79-d5f2c1a0a119</id>
  188.  <title>last.fm: And God Created Brixton - Carter The Unstoppable Sex Machine</title></entry>
  189.  <entry>
  190.    
  191.    <summary type="xhtml">
  192.      <div xmlns="http://www.w3.org/1999/xhtml">Space Exploration Disaster - Sunflower Bean</div>
  193.    </summary>
  194.    <link rel="alternate" href="https://www.last.fm/music/Sunflower+Bean/_/Space+Exploration+Disaster" type="text/html"/>
  195.    <updated>2018-06-19T17:54:56Z</updated>
  196.    <author>
  197.      <name>Sunflower Bean</name>
  198.    </author>
  199.    <id>https://musicbrainz.org/recording/</id>
  200.  <title>last.fm: Space Exploration Disaster - Sunflower Bean</title></entry>
  201.  <entry>
  202.    
  203.    <summary type="xhtml">
  204.      <div xmlns="http://www.w3.org/1999/xhtml">What She Did to My Mind - Ian McNabb</div>
  205.    </summary>
  206.    <link rel="alternate" href="https://www.last.fm/music/Ian+McNabb/_/What+She+Did+to+My+Mind" type="text/html"/>
  207.    <updated>2018-06-19T17:48:53Z</updated>
  208.    <author>
  209.      <name>Ian McNabb</name>
  210.    </author>
  211.    <id>https://musicbrainz.org/recording/36c7b5c9-e137-434d-9a7c-110b25bf08db</id>
  212.  <title>last.fm: What She Did to My Mind - Ian McNabb</title></entry>
  213.  <entry xmlns:media="http://search.yahoo.com/mrss/">
  214.    <id>tag:github.com,2008:PushEvent/7846752862</id>
  215.    <published>2018-06-19T16:19:57Z</published>
  216.    <updated>2018-06-19T16:19:57Z</updated>
  217.    <link type="text/html" rel="alternate" href="https://github.com/davorg/succession/compare/c9fe390870...be4ef70e9e"/>
  218.    
  219.    <author>
  220.      <name>davorg</name>
  221.      <email>[email protected]</email>
  222.      <uri>https://github.com/davorg</uri>
  223.    </author>
  224.    <media:thumbnail height="30" width="30" url="https://avatars1.githubusercontent.com/u/24642?s=30&amp;v=4"/>
  225.    <content type="html">&lt;div class="push"&gt;&lt;div class="body"&gt;&lt;!-- push --&gt;
  226. &lt;div class="d-flex border-bottom py-3"&gt;
  227.  &lt;span class="mr-3"&gt;
  228.  &lt;a href="/davorg" rel="noreferrer"&gt;&lt;img class="avatar" src="https://avatars2.githubusercontent.com/u/24642?s=64&amp;amp;v=4" width="32" height="32" alt="@davorg"&gt;&lt;/a&gt;
  229. &lt;/span&gt;
  230.  
  231.  &lt;div class="d-flex flex-column width-full"&gt;
  232.    &lt;div&gt;
  233.      &lt;a class="link-gray-dark no-underline text-bold wb-break-all" href="/davorg" rel="noreferrer"&gt;davorg&lt;/a&gt;
  234.      
  235.      pushed to
  236.  
  237.        &lt;a class="branch-name" href="/davorg/succession/tree/master" rel="noreferrer"&gt;master&lt;/a&gt;
  238.        in
  239.  
  240.      &lt;a class="link-gray-dark no-underline text-bold wb-break-all" href="/davorg/succession" rel="noreferrer"&gt;davorg/succession&lt;/a&gt;
  241.      &lt;span class="f6 text-gray-light no-wrap ml-1"&gt;
  242.        &lt;relative-time datetime="2018-06-19T16:19:57Z"&gt;Jun 19, 2018&lt;/relative-time&gt;
  243.      &lt;/span&gt;
  244.  
  245.        &lt;div class="Box p-3 mt-2"&gt;
  246.          &lt;span&gt;1 commit to&lt;/span&gt;
  247.          &lt;a class="branch-name" href="/davorg/succession/tree/master" rel="noreferrer"&gt;master&lt;/a&gt;
  248.  
  249.          &lt;div class="commits pusher-is-only-committer"&gt;
  250.            &lt;ul&gt;
  251.                &lt;li class="d-flex flex-items-baseline"&gt;
  252.                  &lt;span title="davorg" class="mr-1"&gt;
  253.                    &lt;a class="d-inline-block" href="/davorg" rel="noreferrer"&gt;&lt;img class="mr-1" src="https://avatars1.githubusercontent.com/u/24642?s=32&amp;amp;v=4" width="16" height="16" alt="@davorg"&gt;&lt;/a&gt;
  254.                  &lt;/span&gt;
  255.                  &lt;code&gt;&lt;a class="mr-1" href="/davorg/succession/commit/be4ef70e9eb2333ab90b250fcd720a1ce9252cf6" rel="noreferrer"&gt;be4ef70&lt;/a&gt;&lt;/code&gt;
  256.                  &lt;div class="message"&gt;
  257.                    &lt;blockquote&gt;
  258.                      Added a new change_date record
  259.                    &lt;/blockquote&gt;
  260.                  &lt;/div&gt;
  261.                &lt;/li&gt;
  262.  
  263.  
  264.            &lt;/ul&gt;
  265.          &lt;/div&gt;
  266.        &lt;/div&gt;
  267.    &lt;/div&gt;
  268.  &lt;/div&gt;
  269. &lt;/div&gt;
  270. &lt;/div&gt;&lt;/div&gt;</content>
  271.  <title>github: davorg pushed to master in davorg/succession</title></entry>
  272.  <entry xmlns:media="http://search.yahoo.com/mrss/">
  273.    <id>tag:github.com,2008:PushEvent/7846733481</id>
  274.    <published>2018-06-19T16:16:29Z</published>
  275.    <updated>2018-06-19T16:16:29Z</updated>
  276.    <link type="text/html" rel="alternate" href="https://github.com/davorg/succession/compare/5dd96aacb1...c9fe390870"/>
  277.    
  278.    <author>
  279.      <name>davorg</name>
  280.      <email>[email protected]</email>
  281.      <uri>https://github.com/davorg</uri>
  282.    </author>
  283.    <media:thumbnail height="30" width="30" url="https://avatars1.githubusercontent.com/u/24642?s=30&amp;v=4"/>
  284.    <content type="html">&lt;div class="push"&gt;&lt;div class="body"&gt;&lt;!-- push --&gt;
  285. &lt;div class="d-flex border-bottom py-3"&gt;
  286.  &lt;span class="mr-3"&gt;
  287.  &lt;a href="/davorg" rel="noreferrer"&gt;&lt;img class="avatar" src="https://avatars2.githubusercontent.com/u/24642?s=64&amp;amp;v=4" width="32" height="32" alt="@davorg"&gt;&lt;/a&gt;
  288. &lt;/span&gt;
  289.  
  290.  &lt;div class="d-flex flex-column width-full"&gt;
  291.    &lt;div&gt;
  292.      &lt;a class="link-gray-dark no-underline text-bold wb-break-all" href="/davorg" rel="noreferrer"&gt;davorg&lt;/a&gt;
  293.      
  294.      pushed to
  295.  
  296.        &lt;a class="branch-name" href="/davorg/succession/tree/master" rel="noreferrer"&gt;master&lt;/a&gt;
  297.        in
  298.  
  299.      &lt;a class="link-gray-dark no-underline text-bold wb-break-all" href="/davorg/succession" rel="noreferrer"&gt;davorg/succession&lt;/a&gt;
  300.      &lt;span class="f6 text-gray-light no-wrap ml-1"&gt;
  301.        &lt;relative-time datetime="2018-06-19T16:16:29Z"&gt;Jun 19, 2018&lt;/relative-time&gt;
  302.      &lt;/span&gt;
  303.  
  304.        &lt;div class="Box p-3 mt-2"&gt;
  305.          &lt;span&gt;1 commit to&lt;/span&gt;
  306.          &lt;a class="branch-name" href="/davorg/succession/tree/master" rel="noreferrer"&gt;master&lt;/a&gt;
  307.  
  308.          &lt;div class="commits pusher-is-only-committer"&gt;
  309.            &lt;ul&gt;
  310.                &lt;li class="d-flex flex-items-baseline"&gt;
  311.                  &lt;span title="davorg" class="mr-1"&gt;
  312.                    &lt;a class="d-inline-block" href="/davorg" rel="noreferrer"&gt;&lt;img class="mr-1" src="https://avatars1.githubusercontent.com/u/24642?s=32&amp;amp;v=4" width="16" height="16" alt="@davorg"&gt;&lt;/a&gt;
  313.                  &lt;/span&gt;
  314.                  &lt;code&gt;&lt;a class="mr-1" href="/davorg/succession/commit/c9fe39087067f34bec38ad8fa611af7e9001e094" rel="noreferrer"&gt;c9fe390&lt;/a&gt;&lt;/code&gt;
  315.                  &lt;div class="message"&gt;
  316.                    &lt;blockquote&gt;
  317.                      Added new baby Tindall.
  318.                    &lt;/blockquote&gt;
  319.                  &lt;/div&gt;
  320.                &lt;/li&gt;
  321.  
  322.  
  323.            &lt;/ul&gt;
  324.          &lt;/div&gt;
  325.        &lt;/div&gt;
  326.    &lt;/div&gt;
  327.  &lt;/div&gt;
  328. &lt;/div&gt;
  329. &lt;/div&gt;&lt;/div&gt;</content>
  330.  <title>github: davorg pushed to master in davorg/succession</title></entry>
  331.  <entry xmlns:media="http://search.yahoo.com/mrss/">
  332.    <id>tag:github.com,2008:IssueCommentEvent/7845432338</id>
  333.    <published>2018-06-19T12:56:42Z</published>
  334.    <updated>2018-06-19T12:56:42Z</updated>
  335.    <link type="text/html" rel="alternate" href="https://github.com/Act-Conferences/tpc-2018-glasgow/pull/15#issuecomment-398389010"/>
  336.    
  337.    <author>
  338.      <name>davorg</name>
  339.      <email>[email protected]</email>
  340.      <uri>https://github.com/davorg</uri>
  341.    </author>
  342.    <media:thumbnail height="30" width="30" url="https://avatars1.githubusercontent.com/u/24642?s=30&amp;v=4"/>
  343.    <content type="html">&lt;div class="issues_comment"&gt;&lt;div class="body"&gt;
  344. &lt;!-- issue_comment --&gt;
  345. &lt;div class="d-flex border-bottom border-gray py-3"&gt;
  346.    &lt;span class="mr-3"&gt;
  347.  &lt;a href="/davorg" rel="noreferrer"&gt;&lt;img class="avatar" src="https://avatars2.githubusercontent.com/u/24642?s=64&amp;amp;v=4" width="32" height="32" alt="@davorg"&gt;&lt;/a&gt;
  348. &lt;/span&gt;
  349.  
  350.  &lt;div class="d-flex flex-column width-full"&gt;
  351.      &lt;div class="d-flex flex-items-baseline mb-2"&gt;
  352.        &lt;div&gt;
  353.          &lt;a class="link-gray-dark no-underline text-bold wb-break-all" href="/davorg" rel="noreferrer"&gt;davorg&lt;/a&gt;
  354.          
  355.          commented on
  356.          pull request
  357.          &lt;a class="link-gray-dark text-bold" title="Information about the venue and attending are on top. " href="/Act-Conferences/tpc-2018-glasgow/pull/15#issuecomment-398389010" rel="noreferrer"&gt;Act-Conferences/tpc-2018-glasgow#15&lt;/a&gt;
  358.          &lt;span class="f6 text-gray-light ml-1"&gt;
  359.            &lt;relative-time datetime="2018-06-19T12:56:42Z"&gt;Jun 19, 2018&lt;/relative-time&gt;
  360.          &lt;/span&gt;
  361.        &lt;/div&gt;
  362.      &lt;/div&gt;
  363.    &lt;div class="message markdown-body Box p-3"&gt;
  364.      &lt;div class="f6 mb-1"&gt;
  365.        &lt;a title="Information about the venue and attending are on top. " class="link-gray" href="/Act-Conferences/tpc-2018-glasgow/pull/15#issuecomment-398389010" rel="noreferrer"&gt;&lt;img class="avatar mr-1" src="https://avatars1.githubusercontent.com/u/24642?s=32&amp;amp;v=4" width="16" height="16" alt="@davorg"&gt; &lt;span class="link-gray-dark text-bold"&gt;davorg&lt;/span&gt; commented &lt;relative-time datetime="2018-06-19T12:56:42Z"&gt;Jun 19, 2018&lt;/relative-time&gt;&lt;/a&gt;
  366.      &lt;/div&gt;
  367.        &lt;p&gt;I don't see any problem with this change, but it's a bit change to the front page so I'd like approval from &lt;a class="user-mention" data-hovercard-user-id="756428" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/shadowcat-mdk" rel="noreferrer"&gt;@shadowcat-mdk&lt;/a&gt; before putting it live.&lt;/p&gt;
  368.    &lt;/div&gt;
  369.  &lt;/div&gt;
  370. &lt;/div&gt;
  371. &lt;/div&gt;&lt;/div&gt;</content>
  372.  <title>github: davorg commented on pull request Act-Conferences/tpc-2018-glasgow#15</title></entry>
  373.  <entry xmlns:media="http://search.yahoo.com/mrss/">
  374.    <id>tag:github.com,2008:PushEvent/7840854729</id>
  375.    <published>2018-06-18T17:42:22Z</published>
  376.    <updated>2018-06-18T17:42:22Z</updated>
  377.    <link type="text/html" rel="alternate" href="https://github.com/davorg/worldcup/compare/1c17115172...8740f977d8"/>
  378.    
  379.    <author>
  380.      <name>davorg</name>
  381.      <email>[email protected]</email>
  382.      <uri>https://github.com/davorg</uri>
  383.    </author>
  384.    <media:thumbnail height="30" width="30" url="https://avatars1.githubusercontent.com/u/24642?s=30&amp;v=4"/>
  385.    <content type="html">&lt;div class="push"&gt;&lt;div class="body"&gt;&lt;!-- push --&gt;
  386. &lt;div class="d-flex border-bottom py-3"&gt;
  387.  &lt;span class="mr-3"&gt;
  388.  &lt;a href="/davorg" rel="noreferrer"&gt;&lt;img class="avatar" src="https://avatars2.githubusercontent.com/u/24642?s=64&amp;amp;v=4" width="32" height="32" alt="@davorg"&gt;&lt;/a&gt;
  389. &lt;/span&gt;
  390.  
  391.  &lt;div class="d-flex flex-column width-full"&gt;
  392.    &lt;div&gt;
  393.      &lt;a class="link-gray-dark no-underline text-bold wb-break-all" href="/davorg" rel="noreferrer"&gt;davorg&lt;/a&gt;
  394.      
  395.      pushed to
  396.  
  397.        &lt;a class="branch-name" href="/davorg/worldcup/tree/master" rel="noreferrer"&gt;master&lt;/a&gt;
  398.        in
  399.  
  400.      &lt;a class="link-gray-dark no-underline text-bold wb-break-all" href="/davorg/worldcup" rel="noreferrer"&gt;davorg/worldcup&lt;/a&gt;
  401.      &lt;span class="f6 text-gray-light no-wrap ml-1"&gt;
  402.        &lt;relative-time datetime="2018-06-18T17:42:22Z"&gt;Jun 18, 2018&lt;/relative-time&gt;
  403.      &lt;/span&gt;
  404.  
  405.        &lt;div class="Box p-3 mt-2"&gt;
  406.          &lt;span&gt;1 commit to&lt;/span&gt;
  407.          &lt;a class="branch-name" href="/davorg/worldcup/tree/master" rel="noreferrer"&gt;master&lt;/a&gt;
  408.  
  409.          &lt;div class="commits pusher-is-only-committer"&gt;
  410.            &lt;ul&gt;
  411.                &lt;li class="d-flex flex-items-baseline"&gt;
  412.                  &lt;span title="davorg" class="mr-1"&gt;
  413.                    &lt;a class="d-inline-block" href="/davorg" rel="noreferrer"&gt;&lt;img class="mr-1" src="https://avatars1.githubusercontent.com/u/24642?s=32&amp;amp;v=4" width="16" height="16" alt="@davorg"&gt;&lt;/a&gt;
  414.                  &lt;/span&gt;
  415.                  &lt;code&gt;&lt;a class="mr-1" href="/davorg/worldcup/commit/8740f977d8fbb24b81f8ce2260f31d3746cfac6b" rel="noreferrer"&gt;8740f97&lt;/a&gt;&lt;/code&gt;
  416.                  &lt;div class="message"&gt;
  417.                    &lt;blockquote&gt;
  418.                      Add toggle to show past games.
  419.                    &lt;/blockquote&gt;
  420.                  &lt;/div&gt;
  421.                &lt;/li&gt;
  422.  
  423.  
  424.            &lt;/ul&gt;
  425.          &lt;/div&gt;
  426.        &lt;/div&gt;
  427.    &lt;/div&gt;
  428.  &lt;/div&gt;
  429. &lt;/div&gt;
  430. &lt;/div&gt;&lt;/div&gt;</content>
  431.  <title>github: davorg pushed to master in davorg/worldcup</title></entry>
  432.  <entry xmlns:media="http://search.yahoo.com/mrss/">
  433.    <id>tag:github.com,2008:PushEvent/7840777854</id>
  434.    <published>2018-06-18T17:27:14Z</published>
  435.    <updated>2018-06-18T17:27:14Z</updated>
  436.    <link type="text/html" rel="alternate" href="https://github.com/davorg/worldcup/compare/e66c97bfb2...1c17115172"/>
  437.    
  438.    <author>
  439.      <name>davorg</name>
  440.      <email>[email protected]</email>
  441.      <uri>https://github.com/davorg</uri>
  442.    </author>
  443.    <media:thumbnail height="30" width="30" url="https://avatars1.githubusercontent.com/u/24642?s=30&amp;v=4"/>
  444.    <content type="html">&lt;div class="push"&gt;&lt;div class="body"&gt;&lt;!-- push --&gt;
  445. &lt;div class="d-flex border-bottom py-3"&gt;
  446.  &lt;span class="mr-3"&gt;
  447.  &lt;a href="/davorg" rel="noreferrer"&gt;&lt;img class="avatar" src="https://avatars2.githubusercontent.com/u/24642?s=64&amp;amp;v=4" width="32" height="32" alt="@davorg"&gt;&lt;/a&gt;
  448. &lt;/span&gt;
  449.  
  450.  &lt;div class="d-flex flex-column width-full"&gt;
  451.    &lt;div&gt;
  452.      &lt;a class="link-gray-dark no-underline text-bold wb-break-all" href="/davorg" rel="noreferrer"&gt;davorg&lt;/a&gt;
  453.      
  454.      pushed to
  455.  
  456.        &lt;a class="branch-name" href="/davorg/worldcup/tree/master" rel="noreferrer"&gt;master&lt;/a&gt;
  457.        in
  458.  
  459.      &lt;a class="link-gray-dark no-underline text-bold wb-break-all" href="/davorg/worldcup" rel="noreferrer"&gt;davorg/worldcup&lt;/a&gt;
  460.      &lt;span class="f6 text-gray-light no-wrap ml-1"&gt;
  461.        &lt;relative-time datetime="2018-06-18T17:27:14Z"&gt;Jun 18, 2018&lt;/relative-time&gt;
  462.      &lt;/span&gt;
  463.  
  464.        &lt;div class="Box p-3 mt-2"&gt;
  465.          &lt;span&gt;1 commit to&lt;/span&gt;
  466.          &lt;a class="branch-name" href="/davorg/worldcup/tree/master" rel="noreferrer"&gt;master&lt;/a&gt;
  467.  
  468.          &lt;div class="commits pusher-is-only-committer"&gt;
  469.            &lt;ul&gt;
  470.                &lt;li class="d-flex flex-items-baseline"&gt;
  471.                  &lt;span title="davorg" class="mr-1"&gt;
  472.                    &lt;a class="d-inline-block" href="/davorg" rel="noreferrer"&gt;&lt;img class="mr-1" src="https://avatars1.githubusercontent.com/u/24642?s=32&amp;amp;v=4" width="16" height="16" alt="@davorg"&gt;&lt;/a&gt;
  473.                  &lt;/span&gt;
  474.                  &lt;code&gt;&lt;a class="mr-1" href="/davorg/worldcup/commit/1c171151729ce97fe2bbe8e019fbd051f8b05cde" rel="noreferrer"&gt;1c17115&lt;/a&gt;&lt;/code&gt;
  475.                  &lt;div class="message"&gt;
  476.                    &lt;blockquote&gt;
  477.                      Fix asynchronous idiocy.
  478.                    &lt;/blockquote&gt;
  479.                  &lt;/div&gt;
  480.                &lt;/li&gt;
  481.  
  482.  
  483.            &lt;/ul&gt;
  484.          &lt;/div&gt;
  485.        &lt;/div&gt;
  486.    &lt;/div&gt;
  487.  &lt;/div&gt;
  488. &lt;/div&gt;
  489. &lt;/div&gt;&lt;/div&gt;</content>
  490.  <title>github: davorg pushed to master in davorg/worldcup</title></entry>
  491.  <entry>
  492.    <title>goodreads: Json at Work: Practical Data Integration for the Web</title>
  493.    <link rel="alternate" href="https://www.goodreads.com/review/show/2427624923?utm_medium=api&amp;utm_source=rss" type="text/html"/>
  494.    <content type="xhtml">
  495.      <div xmlns="http://www.w3.org/1999/xhtml">
  496.      
  497.      <a href="https://www.goodreads.com/book/show/28388269-json-at-work?utm_medium=api&amp;utm_source=rss"><img alt="Json at Work: Practical Data Integration for the Web" src="https://images.gr-assets.com/books/1498869315s/28388269.jpg"/></a><br/>
  498.                                      author: Tom Marrs<br/>
  499.                                      name: David<br/>
  500.                                      average rating: 3.00<br/>
  501.                                      book published: <br/>
  502.                                      rating: 0<br/>
  503.                                      read at: <br/>
  504.                                      date added: 2018/06/18<br/>
  505.                                      shelves: currently-reading<br/>
  506.                                      review: <br/><br/>
  507.                                      
  508.    </div>
  509.    </content>
  510.    <id>https://www.goodreads.com/review/show/2427624923?utm_medium=api&amp;utm_source=rss</id>
  511.    <published>2018-06-18T01:59:31-07:00</published>
  512.    <updated>2018-06-18T01:59:31-07:00</updated>
  513.  </entry>
  514.  <entry xmlns:flickr="urn:flickr:user" xmlns:dc="http://purl.org/dc/elements/1.1/">
  515.    
  516.    <link rel="alternate" type="text/html" href="http://www.flickr.com/photos/davorg/28979581498/"/>
  517.    <id>tag:flickr.com,2005:/photo/28979581498</id>
  518.    <published>2018-06-17T11:38:39Z</published>
  519.    <updated>2018-06-17T11:38:39Z</updated>
  520.    <flickr:date_taken>2018-06-17T12:38:39-08:00</flickr:date_taken>
  521.    <dc:date.Taken>2018-06-17T12:38:39-08:00</dc:date.Taken>
  522.    <content type="html"> &lt;p&gt;&lt;a href="http://www.flickr.com/people/davorg/"&gt;Dave Cross&lt;/a&gt; posted a photo:&lt;/p&gt;
  523. &lt;p&gt;&lt;a href="http://www.flickr.com/photos/davorg/28979581498/" title="Found this chap dead in my garden."&gt;&lt;img src="http://farm2.staticflickr.com/1823/28979581498_7b24be4e11_m.jpg" width="240" height="240" alt="Found this chap dead in my garden." /&gt;&lt;/a&gt;&lt;/p&gt;
  524.  
  525. &lt;p&gt;via Instagram &lt;a href="https://ift.tt/2LUslnR" rel="nofollow"&gt;ift.tt/2LUslnR&lt;/a&gt;&lt;/p&gt;</content>
  526.    <author>
  527.      <name>Dave Cross</name>
  528.      <uri>http://www.flickr.com/people/davorg/</uri>
  529.      <flickr:nsid>[email protected]</flickr:nsid>
  530.      <flickr:buddyicon>http://farm5.staticflickr.com/4759/buddyicons/[email protected]?1516110776#[email protected]</flickr:buddyicon>
  531.    </author>
  532.    <link rel="license" type="text/html" href="https://creativecommons.org/licenses/by-nc-sa/2.0/deed.en"/>
  533.    <link rel="enclosure" type="image/jpeg" href="http://farm2.staticflickr.com/1823/28979581498_7b24be4e11_b.jpg"/>
  534.    <category term="ifttt" scheme="http://www.flickr.com/photos/tags/"/>
  535.    <category term="instagram" scheme="http://www.flickr.com/photos/tags/"/>
  536.    <displaycategories>
  537.            </displaycategories>
  538.    <title>flickr: Found this chap dead in my garden.</title></entry>
  539.  <entry>
  540.    <title>davblog: Monzo &amp; IFTTT</title>
  541.    <link rel="alternate" href="http://feedproxy.google.com/~r/realdavblog/~3/_Jzrd25PBDc/monzo-ifttt.html" type="text/html"/>
  542.    <content type="xhtml">
  543.      <div xmlns="http://www.w3.org/1999/xhtml"><p>When I signed up for my <a href="//monzo.com/">Monzo</a> bank account last year, one of the things that really excited me was the <a href="//docs.monzo.com/">API they made available</a>. Of course, as is so often the way with these things, my time was taken up with other things and I never really got any further than installing the <a href="//metacpan.org/pod/Business::Monzo">Perl module</a> that wrapped the API.</p>
  544. <p>The problem is that writing code against an API takes too long. Oh, it’s generally not particularly difficult, but there’s always something that’s more complicated than you think it’s going to be.</p>
  545. <p>So I was really interested to read last week that <a href="//monzo.com/blog/2018/06/07/monzo-on-ifttt/">Monzo now works with IFTTT</a>. IFTTT (“If This Then That”) is a service which removes the complexity from API programming. You basically plug services together to do something useful. I’ve dabbled with IFTTT before. I have “applets” which automatically post my Instagram photos to Twitter, change my phone’s wallpaper to NASA’s photo of the day, tell me when the ISS is overhead – things like that) so I knew this would be an easier way to do interesting things with the Monzo API – without all that tedious programming.</p>
  546. <p>An IFTTT applet has two parts. There’s a “trigger” (something that tells the applet to run) and an “action” (what you want it to do). Monzo offers both triggers and actions. The triggers are mostly fired when you make a purchase with your card (optionally filtered on things like the merchant or the amount). The actions are moving money into or out of a pot (a pot in a Monzo account is a named, ring-fenced area in your account where you can put money that you want to set aside for a particular purpose).</p>
  547. <p>You can use a Monzo trigger and action together (when I buy something at McDonald’s, move £5 to my “Sin Bin” pot) but more interesting things happen if you combine them with triggers and actions from other providers (move £5 into my “Treats” pot when I do a 5K run – there are dozens of providers).</p>
  548. <p>I needed an example to try it out. I decided to make a Twitter Swear Box. The idea is simple. If I tweet a bad word, I move £1 from my main account into my Swear Box pot.</p>
  549. <p>The action part is simple enough. Monzo provides an action to move money out of a pot. You just need to give it the name of the pot and the amount to move.</p>
  550. <p>The trigger part is a little harder. Twitter provides a trigger that fires whenever I tweet, but that doesn’t let me filter it to look for rude words. But there’s also a Twitter Search trigger which fires whenever a Twitter search finds a tweet which matches a particular search criterion. I used <a href="//twitter.com/search-advanced">https://twitter.com/search-advanced</a> to work out the search string to use and ended up with “fudge OR pish OR shirt from:davorg”. There’s a slight problem here – it doesn’t find other versions of the words like “fudging” or “shirty” – but this is good enough for a proof of concept.</p>
  551. <p>Creating the applet is a simple as choosing the services you want to use, selecting the correct trigger and action and then filling in a few (usually pretty obvious) details. Within fifteen minutes I had it up and running. I sent a tweet containing the word “fudge” and seconds later there was a pound in my Swear Box pot.</p>
  552. <p>Tonight, I was at a meeting at Monzo’s offices where they talked about how they developed the IFTTT integration and what directions it might go in the future. I asked for the latitude and longitude of a transaction to be included in the details that IFTTT gets – I have a plan to plot my transactions on a map.</p>
  553. <p>Monzo is the first bank to release an integration with IFTTT and it really feels like we’re on the verge of something really useful here. I’ll be great to see where they take the service in the future.</p>
  554. <p>The post <a rel="nofollow" href="//blog.dave.org.uk/2018/06/monzo-ifttt.html">Monzo &amp; IFTTT</a> appeared first on <a rel="nofollow" href="//blog.dave.org.uk">Davblog</a>.</p>
  555. <img src="http://feeds.feedburner.com/~r/realdavblog/~4/_Jzrd25PBDc" height="1" width="1" alt=""/></div>
  556.    </content>
  557.    <summary type="xhtml">
  558.      <div xmlns="http://www.w3.org/1999/xhtml"><p>When I signed up for my Monzo bank account last year, one of the things that really excited me was the API they made available. Of course, as is so often the way with these things, my time was taken up with other things and I never really got any further than installing the Perl … </p>
  559. <p class="link-more"><a href="//blog.dave.org.uk/2018/06/monzo-ifttt.html" class="more-link">Continue reading<span class="screen-reader-text"> "Monzo &amp; IFTTT"</span></a></p>
  560. <p>The post <a rel="nofollow" href="//blog.dave.org.uk/2018/06/monzo-ifttt.html">Monzo &amp; IFTTT</a> appeared first on <a rel="nofollow" href="//blog.dave.org.uk">Davblog</a>.</p>
  561. </div>
  562.    </summary>
  563.    <author>
  564.      <name>Dave Cross</name>
  565.    </author>
  566.    <id>https://blog.dave.org.uk/?p=3674</id>
  567.    <published>2018-06-14T20:47:46Z</published>
  568.    <updated>2018-06-14T20:47:46Z</updated>
  569.    <category term="tech"/>
  570.    <category term="fintech"/>
  571.    <category term="ifttt"/>
  572.    <category term="monzo"/>
  573.  </entry>
  574.  <entry>
  575.    <title>perl hacks: Training in Glasgow</title>
  576.    <link rel="alternate" href="http://feedproxy.google.com/~r/PerlHacks/~3/vm7oOJd8VOA/" type="text/html"/>
  577.    <content type="xhtml">
  578.      <div xmlns="http://www.w3.org/1999/xhtml"><p>It’s June, which means it’s only a couple of months until the Europe Perl community descends en masse on Glasgow for this year’s <a href="http://act.perlconference.org/tpc-2018-glasgow/">Perl Conference</a> (formerly known as YAPC). For me, that also means I need to start planning the training courses I’ll be running before the conference. And for you, it means you need to start deciding which training courses you want to come to before the conference</p>
  579. <p>This year, it looks like there will be one day of training courses on the day before the main conference starts (that’s Tuesday 14th August). There are a number of courses being offered – details are in a <a href="http://act.perlconference.org/tpc-2018-glasgow/news/1557">recent conference newsletter</a>.</p>
  580. <p>I’ll be giving two half-day courses and, unusually, there will be little or no Perl content in either of them. Here are the details:</p>
  581. <h2>Web Site Tune-Up: Improve Your Googlejuice</h2>
  582. <p>Many of us have web sites and for most web sites, success is measured by the number of visitors you get. And, in most of the western world, getting your web site to rank higher in Google’s search results is one powerful tool for bringing in more visitors.</p>
  583. <p>In this half-day course, I’ll be introducing a number of simple tips that will make your site more attractive to Google which will, hopefully, improve your search ranking. If you make it easier for Google to understand the contents and structure of your site, then Google is more likely to want to send visitors to your site. (Other search engines are, of course, available but if you keep Google happy, you’ll be keeping them happy too.)</p>
  584. <p>I ran a short version of this course at the London Perl Workshop last year. This version will be twice as long (and twice as detailed).</p>
  585. <h2>The Professional Programmer</h2>
  586. <p>Some people seem surprised that being really good at programming isn’t the only skill you need in order to have a successful career in software development.</p>
  587. <p>I’ve been working in this industry for thirty years and I like to think I’ve been pretty successful. In this half-day course, I’ll look at some of the other skills that you need in order to do well in this industry. We’ll look at a range of skills from more technical areas like source code control and devops, to softer areas like software development methodologies and just working well with others.</p>
  588. <p>I ran a two-hour version of this course at a London Perl Workshop in the dim and distant past. This version will be updated and expanded.</p>
  589. <p> </p>
  590. <p>Both courses will be taking place on the same day. I’m not sure where they will be held, but I’ll let you know as soon as I have that information. Each half-day session costs £75 and you can <a href="http://act.perlconference.org/tpc-2018-glasgow/purchase">book places on the conference </a>web site. Places on the courses will be limited, so I recommend booking as soon as possible.</p>
  591. <p>Do these courses sound interesting? Please let me know your thoughts in the comments.</p>
  592. <p>The post <a rel="nofollow" href="https://perlhacks.com/2018/06/training-in-glasgow/">Training in Glasgow</a> appeared first on <a rel="nofollow" href="https://perlhacks.com">Perl Hacks</a>.</p>
  593. <img src="http://feeds.feedburner.com/~r/PerlHacks/~4/vm7oOJd8VOA" height="1" width="1" alt=""/></div>
  594.    </content>
  595.    <summary type="xhtml">
  596.      <div xmlns="http://www.w3.org/1999/xhtml"><p>It’s June, which means it’s only a couple of months until the Europe Perl community descends en masse on Glasgow for this year’s Perl Conference (formerly known as YAPC). For me, that also means I need to start planning the training courses I’ll be running before the conference. And for you, it means you need to … </p>
  597. <p class="link-more"><a href="https://perlhacks.com/2018/06/training-in-glasgow/" class="more-link">Continue reading<span class="screen-reader-text"> "Training in Glasgow"</span></a></p>
  598. <p>The post <a rel="nofollow" href="https://perlhacks.com/2018/06/training-in-glasgow/">Training in Glasgow</a> appeared first on <a rel="nofollow" href="https://perlhacks.com">Perl Hacks</a>.</p>
  599. </div>
  600.    </summary>
  601.    <author>
  602.      <name>Dave Cross</name>
  603.    </author>
  604.    <id>https://perlhacks.com/?p=1834</id>
  605.    <published>2018-06-03T08:06:38Z</published>
  606.    <updated>2018-06-03T08:06:38Z</updated>
  607.    <category term="Training"/>
  608.    <category term="glasgow"/>
  609.    <category term="tpc"/>
  610.    <category term="training"/>
  611.    <category term="yapc"/>
  612.  </entry>
  613.  <entry>
  614.    <title>cpan: DAVECROSS has released MooX-Role-JSON_LD-0.0.13</title>
  615.    <link rel="alternate" href="https://metacpan.org/release/DAVECROSS/MooX-Role-JSON_LD-0.0.13" type="text/html"/>
  616.    <content type="xhtml">
  617.      <div xmlns="http://www.w3.org/1999/xhtml">Easily provide JSON-LD mark-up for your objects.</div>
  618.    </content>
  619.    <author>
  620.      <name>DAVECROSS</name>
  621.    </author>
  622.    <id>https://metacpan.org/release/DAVECROSS/MooX-Role-JSON_LD-0.0.13</id>
  623.    <published>2018-06-02T18:35:40</published>
  624.    <updated>2018-06-02T18:35:40</updated>
  625.  </entry>
  626.  <entry>
  627.    <title>perl hacks: Selenium and Perl</title>
  628.    <link rel="alternate" href="http://feedproxy.google.com/~r/PerlHacks/~3/lbaPvnc2No4/" type="text/html"/>
  629.    <content type="xhtml">
  630.      <div xmlns="http://www.w3.org/1999/xhtml"><p>Some of you might remember the lightning talk I gave at the London Perl Workshop last year (it’s <a href="https://www.youtube.com/watch?v=E6ZJFE_Knz8">available on YouTube</a>, I’ll wait if you want to watch it). In it, I said I planned to resurrect the <a href="https://perlschool.com/">Perl School</a> brand, using it to publish Perl ebooks. One book, <em><a href="https://perlschool.com/books/perl-taster">Perl Taster</a></em>, was already available and I had plans to write and publish several more. Those plans are still ongoing…</p>
  631. <p>Also in the talk, I asked if anyone else wanted to write a book for the series. I offered to help out with the hard parts of getting your text into the Amazon system (it’s actually nowhere near as hard as you might think). Three people approached me later to discuss the possibility of writing something, but only one followed through with something more concrete. That was John Davies, who has been a regular attendee at London Perl Mongers for a pretty long time. At the LPW, John had helped Martin Berends to run a training course on using Selenium with Perl. As part of that help, John had written some notes on the course which had been distributed to the attendees. John wondered if those notes would be worth publishing as a Perl School ebook. I said that it was certainly worth pursuing the idea.</p>
  632. <p>Over the last few months, John has expanded his original notes considerably and I’ve been doing the work needed to convert his input into an ebook. And I’m happy to say that the book was published on Amazon yesterday. It’s called <a href="https://perlschool.com/books/selenium-perl/">Selenium and Perl</a> and you should be able to find it on your local Kindle store. If you want to test your Perl web applications using Selenium, then I hope that you find it useful.</p>
  633. <p>It’s been the first time I’ve edited someone else’s work and converted it into an ebook. I think the process has gone well (perhaps someone should ask John for his opinion!)</p>
  634. <p>But I’m confident enough of the process to renew the offer I made at the LPW. If you’re interested in writing an ebook as part of the Perl School range, please get in touch and we can discuss it.</p>
  635. <p>The post <a rel="nofollow" href="https://perlhacks.com/2018/05/selenium-and-perl/">Selenium and Perl</a> appeared first on <a rel="nofollow" href="https://perlhacks.com">Perl Hacks</a>.</p>
  636. <img src="http://feeds.feedburner.com/~r/PerlHacks/~4/lbaPvnc2No4" height="1" width="1" alt=""/></div>
  637.    </content>
  638.    <summary type="xhtml">
  639.      <div xmlns="http://www.w3.org/1999/xhtml"><p>Some of you might remember the lightning talk I gave at the London Perl Workshop last year (it’s available on YouTube, I’ll wait if you want to watch it). In it, I said I planned to resurrect the Perl School brand, using it to publish Perl ebooks. One book, Perl Taster, was already available and … </p>
  640. <p class="link-more"><a href="https://perlhacks.com/2018/05/selenium-and-perl/" class="more-link">Continue reading<span class="screen-reader-text"> "Selenium and Perl"</span></a></p>
  641. <p>The post <a rel="nofollow" href="https://perlhacks.com/2018/05/selenium-and-perl/">Selenium and Perl</a> appeared first on <a rel="nofollow" href="https://perlhacks.com">Perl Hacks</a>.</p>
  642. </div>
  643.    </summary>
  644.    <author>
  645.      <name>Dave Cross</name>
  646.    </author>
  647.    <id>https://perlhacks.com/?p=1824</id>
  648.    <published>2018-05-20T09:50:53Z</published>
  649.    <updated>2018-05-20T09:50:53Z</updated>
  650.    <category term="Books"/>
  651.    <category term="books"/>
  652.    <category term="ebooks"/>
  653.    <category term="perl school"/>
  654.    <category term="selenium"/>
  655.  </entry>
  656.  <entry>
  657.    <title>davblog: Brighton SEO – April 2018</title>
  658.    <link rel="alternate" href="http://feedproxy.google.com/~r/realdavblog/~3/50ZTEmLmQwY/brighton-seo-april-2018.html" type="text/html"/>
  659.    <content type="html">&lt;p&gt;Yesterday I was at my second &lt;a href="//www.brightonseo.com/"&gt;Brighton SEO&lt;/a&gt; conference. I enjoyed it every bit as much as the last one and I’m already looking forward to the next. Here are my notes about the talks I saw.&lt;/p&gt;
  660. &lt;h2&gt;Technical SEO&lt;/h2&gt;
  661. &lt;h3&gt;Command Line Hacks For SEO&lt;/h3&gt;
  662. &lt;p&gt;&lt;a href="//twitter.com/cptntommy"&gt;Tom Pool&lt;/a&gt; / &lt;a href="//www.slideshare.net/TomPool/command-line-hacks-for-seo-brighton-april-2018-tom-pool"&gt;Slides&lt;/a&gt;&lt;/p&gt;
  663. &lt;p&gt;I misread the description for this. I thought it would be about clever ways to use command-line tools for SEO purposes. But, actually, it was a basic introduction to Unix command-line text processing tools for people who were previously unaware of them. I wasn’t really the target audience, but it’s always good to see a largely non-technical audience being introduced to the powerful tools that I use ever day.&lt;/p&gt;
  664. &lt;h3&gt;Diving into HTTP/2 – a Guide for SEOs&lt;/h3&gt;
  665. &lt;p&gt;&lt;a href="//twitter.com/TomAnthonySEO"&gt;Tom Anthony&lt;/a&gt; / &lt;a href="//www.slideshare.net/TomAnthony/http2-brightonseo-2018"&gt;Slides&lt;/a&gt;&lt;/p&gt;
  666. &lt;p&gt;A good introduction to why HTTP/2 is good news for web traffic (it’s faster) and a great trucking analogy explaining what HTTP is and how HTTP/2 improves on current systems. I would have liked more technical detail, but I realise most of the audience wouldn’t.&lt;/p&gt;
  667. &lt;h3&gt;Diagnosing Common Hreflang tag issues on page and in sitemaps&lt;/h3&gt;
  668. &lt;p&gt;&lt;a href="//twitter.com/iamthelaserhawk"&gt;Emily Mace&lt;/a&gt; / &lt;a href="//www.slideshare.net/OBAN-IDForum/hreflang-tags-brighton-seo-april-2018-emily-mace-95224630"&gt;Slides&lt;/a&gt;&lt;/p&gt;
  669. &lt;p&gt;To be honest, I was only here because it was the last talk in the session and I didn’t have time to move elsewhere. I have never worked on a site with pages that are translated into other languages, so this was of limited interest to me. But Emily certainly seemed to know her stuff and I’m sure that people who use “hreflang” would have found it very interesting and useful.&lt;/p&gt;
  670. &lt;p&gt;One thing bothered me slightly about the talk. A couple of times, Emily referred to developers in slightly disparaging ways. And I realised that I’ve heard similar sentiments before at SEO events. It’s like developers are people that SEO analysts are constantly battling with to get their work done. As a developer myself (and one who has spend the last year implementing SEO fixes on one of the UK’s best-known sites) I don’t really understand this attitude – as it’s something I’ve never come across.&lt;/p&gt;
  671. &lt;p&gt;It’s annoyed me enough that I’m considering proposing a talk called “I Am Developer” to the next Brighton SEO in order to try to get to the bottom of this issue.&lt;/p&gt;
  672. &lt;h1&gt;Onsite SEO&lt;/h1&gt;
  673. &lt;h3&gt;Optimizing for Search Bots&lt;/h3&gt;
  674. &lt;p&gt;&lt;a href="//twitter.com/filiwiese"&gt;Fili Wiese&lt;/a&gt; / &lt;a href="//www.slideshare.net/FiliWiese/link-building-2018"&gt;Slides&lt;/a&gt;&lt;/p&gt;
  675. &lt;p&gt;Fili is a former Google Search Quality Engineer, so he certainly knows his stuff. But this talk seemed a bit scattershot to me – it didn’t seem to have a particularly clear focus.&lt;/p&gt;
  676. &lt;h3&gt;Advanced and Practical Structured Data with Schema.org&lt;/h3&gt;
  677. &lt;p&gt;&lt;a href="//twitter.com/AlexisKSanders"&gt;Alexis K Sanders&lt;/a&gt; / &lt;a href="//www.slideshare.net/sandersal1/brightonseo-structured-data-by-alexis-sanders"&gt;Slides&lt;/a&gt;&lt;/p&gt;
  678. &lt;p&gt;This was probably the talk I was looking forward to most. I’ve been dabbling in JSON-LD on a few sites recently and I’m keen to get deeper into to. Alexis didn’t disappoint – this was a great introduction to the subject and (unlike some other speakers) she wasn’t afraid to go deeper when it was justified.&lt;/p&gt;
  679. &lt;p&gt;Here first slide showed some JSON-LD and she asked us to spot the five errors in it. I’m disappointed to report that I only caught two of them.&lt;/p&gt;
  680. &lt;h3&gt;Cut the Crap: Next Level Content Audits With Crawlers&lt;/h3&gt;
  681. &lt;p&gt;&lt;a href="//twitter.com/sam_marsden"&gt;Sam Marsden&lt;/a&gt; / &lt;a href="//www.slideshare.net/DeepCrawl/cut-the-crap-next-level-content-audits-with-crawlers-sam-marsden-technical-seo-deepcrawl/1"&gt;Slides&lt;/a&gt;&lt;/p&gt;
  682. &lt;p&gt;This started well. A good crawling strategy is certainly important for auditing your site and ensuring that everything still works as expected. However, I was slightly put off by Sam’s insistence that a cloud-based crawling tool was an essential part of this strategy. Sam works for Deep Crawl who just happen to have a cloud-based crawling tool that they would love to sell you.&lt;/p&gt;
  683. &lt;p&gt;Conferences like this are at their best when the experts are sharing their knowledge with the audience without explicitly trying to sell their services. Sadly, this talk fell just on the wrong side of that line.&lt;/p&gt;
  684. &lt;h2&gt;Lunch&lt;/h2&gt;
  685. &lt;p&gt;Then it was lunchtime and my colleagues and I retired just around the corner to eat far too much pizza that was supplied by the nice people at &lt;a href="//twitter.com/PiDatametrics"&gt;PI Datametrics&lt;/a&gt;.&lt;/p&gt;
  686. &lt;h2&gt;SERPs&lt;/h2&gt;
  687. &lt;h3&gt;Featured snippets: From then to now, volatility, and voice search&lt;/h3&gt;
  688. &lt;p&gt;&lt;a href="//twitter.com/STATRob"&gt;Rob Bucci&lt;/a&gt; / &lt;a href="//www.slideshare.net/DistilledSEO/searchlove-san-diego-rob-bucci-featured-snippets-from-then-to-now-volatility-and-voice-search?qid=504cf7af-0167-4e91-b87b-dd028bfb9fcd&amp;v=&amp;b=&amp;from_search=2"&gt;Slides&lt;/a&gt;&lt;/p&gt;
  689. &lt;p&gt;This was really interesting. Rob says that featured snippets are on the rise and had some interesting statistics that will help you get your pages into a featured snippet. He then went on to explain how featured are forming the basis of Google’s Voice Search – that is, if you ask Google Home or Google Assistant a question, the reply is very likely to be the featured snippet that you’d get in response to the same query on the Google Search Engine. This makes it an ever better idea to aim at getting your content into featured snippets.&lt;/p&gt;
  690. &lt;h3&gt;From Black Friday to iPhones – how to rank for big terms on big days&lt;/h3&gt;
  691. &lt;p&gt;&lt;a href="//twitter.com/Sam_Robson"&gt;Sam Robson&lt;/a&gt; / Slides&lt;/p&gt;
  692. &lt;p&gt;Sam works for Future Publishing, on their Tech Radar site. He had some interesting war stories about dealing with Google algorithm changes and coming out the other side with a stronger site that is well-placed to capitalise on big technical keywords.&lt;/p&gt;
  693. &lt;p&gt;[I can’t find his slides online. I’ll update this post if I find them.]&lt;/p&gt;
  694. &lt;h3&gt;A Universal Strategy for Answer Engine Optimisation (beyond position 0)&lt;/h3&gt;
  695. &lt;p&gt;&lt;a href="//twitter.com/jasonmbarnard"&gt;Jason Barnard&lt;/a&gt; / &lt;a href="//www.slideshare.net/JasonBarnard2/a-universal-strategy-for-answer-engine-optimisation-beyond-position-0"&gt;Slides&lt;/a&gt;&lt;/p&gt;
  696. &lt;p&gt;This tied in really well with the other talks in  the session. Jason has good ideas about how to get Google to trust your site more by convincing Google that you are the most credible source for information on the topics you cover. He also talked a lot about the machine learning that Google are currently using and where that might lead in the future.&lt;/p&gt;
  697. &lt;h2&gt;Reporting&lt;/h2&gt;
  698. &lt;p&gt;I was at a bit of a loose end for the final session. Nothing really grabbed me. In  the end I just stayed in the same room I’d been in for the previous session. I’m glad I did.&lt;/p&gt;
  699. &lt;h3&gt;How to report on SEO in 2018&lt;/h3&gt;
  700. &lt;p&gt;&lt;a href="//twitter.com/stekenwright"&gt;Stephen Kenwright&lt;/a&gt; / &lt;a href="//www.slideshare.net/Branded3/how-to-report-on-seo-in-2018-brightonseo"&gt;Slides&lt;/a&gt;&lt;/p&gt;
  701. &lt;p&gt;All too often, I’ve seen companies who don’t really know how to report effectively on how successfully (or otherwise!) their web sites are performing. And that’s usually because they don’t know what metrics are important or useful to them. Stephen had some good ideas about identifying the best metrics to track and ensuring that the right numbers are seen by the right people.&lt;/p&gt;
  702. &lt;h3&gt;Top GA customisations everyone should be using&lt;/h3&gt;
  703. &lt;p&gt;&lt;a href="//twitter.com/annatlewis"&gt;Anna Lewis&lt;/a&gt; / &lt;a href="//www.slideshare.net/anna_lewis/top-google-analytics-customisations-brighton-seo-april-2018"&gt;Slides&lt;/a&gt;&lt;/p&gt;
  704. &lt;p&gt;Having following Stephen’s advice and chosen the metrics that you need to track, Anna can show you how to record those metrics and how to also capture other useful information. As a good example, she mentioned a client who was an amusement park. Alongside the usual kinds of metrics, they had also been able to track the weather conditions at the time someone visited the site and had used that data to corroborate ticket sales with the weather.&lt;/p&gt;
  705. &lt;p&gt;Anna seemed to be a big fan of Google Tag Manager which I had previously dismissed. Perhaps I need to revisit that.&lt;/p&gt;
  706. &lt;h3&gt;The Math Behind Effective Reporting&lt;/h3&gt;
  707. &lt;p&gt;&lt;a href="//twitter.com/danaditomaso"&gt;Dana DiTomaso&lt;/a&gt; / Slides&lt;/p&gt;
  708. &lt;p&gt;And once you have all of your data squirrelled away in Google Analytics, you need a good tool to turn it into compelling and useful reports. Dana showed us how we could to that with Google Data Studio – another tool I need to investigate in more detail.&lt;/p&gt;
  709. &lt;p&gt;[I can’t find her slides online. I’ll update this post if I find them.]&lt;/p&gt;
  710. &lt;h2&gt;Keynote&lt;/h2&gt;
  711. &lt;h3&gt;Live Google Webmasters Hangout&lt;/h3&gt;
  712. &lt;p&gt;&lt;a href="//twitter.com/JohnMu"&gt;John Mueller&lt;/a&gt; &amp; &lt;a href="//twitter.com/aleyda"&gt;Aleyda Solis&lt;/a&gt;&lt;/p&gt;
  713. &lt;p&gt;Two things struck me while watching the keynote conversation between John Mueller and Aleyda Solis. Firstly, I though that Aleyda was the wrong person to be running the session. I know that Brighton SEO tries hard not to be the usual stuffy, corporate type of conference, but I thought her over-familiar and jokey style didn’t go well in a conversation with Google’s John Mueller.&lt;/p&gt;
  714. &lt;p&gt;Secondly, I had a bit of an epiphany about the SEO industry. All day, I’d been watching people trying to explain how to get your site to do well in Google (other search engines are, of course, available but, honestly, who cares about them?) but they’re doing so without any real knowledge of how the Mighty God of Search really works.&lt;/p&gt;
  715. &lt;p&gt;Oh, sure, Google gives us tools like &lt;a href="//analytics.google.com/"&gt;Google Analytics&lt;/a&gt; which allow us so see how well we’re doing and &lt;a href="//www.google.com/webmasters/tools/home"&gt;Google Search Console&lt;/a&gt; which will give us clues about ways we might be doing better. But, ultimately, this whole industry is trying to understand the inner working of a company that tells us next to nothing.&lt;/p&gt;
  716. &lt;p&gt;This was really obvious in the conversation with John Mueller. Pretty much every question was answered with a variation on “well, I don’t think we’d talk publicly about the details of that algorithm” or “this is controlled by a variety of factors that will change frequently, so I don’t think it’s useful to list them”.&lt;/p&gt;
  717. &lt;p&gt;The industry is largely stumbling about in the dark. We can apply the scientific method – we propose a hypothesis, run experiments, measure the results, adjust our hypothesis and repeat. Sometimes we might get close to a consensus on how something works. But then (and this is where SEO differs from real science) Google change their algorithms and everything we thought we knew has now changed.&lt;/p&gt;
  718. &lt;p&gt;Don’t get me wrong, it’s a fascinating process to watch. And, to a lesser extent, to be involved in. And there’s a lot riding on getting the results right. But in many ways, it’s all ultimately futile.&lt;/p&gt;
  719. &lt;p&gt;Wow, that got dark quickly! I should finish by saying that, despite what I wrote above, Brighton SEO is a great conference. If you want more people to visit your web site, you should be interested in SEO. And if you’re interested in SEO, you should be at Brighton SEO.&lt;/p&gt;
  720. &lt;p&gt;See you at the next one – it’s on September 28th.&lt;/p&gt;
  721. &lt;p&gt;The post &lt;a rel="nofollow" href="//blog.dave.org.uk/2018/04/brighton-seo-april-2018.html"&gt;Brighton SEO &amp;#8211; April 2018&lt;/a&gt; appeared first on &lt;a rel="nofollow" href="//blog.dave.org.uk"&gt;Davblog&lt;/a&gt;.&lt;/p&gt;
  722. &lt;img src="http://feeds.feedburner.com/~r/realdavblog/~4/50ZTEmLmQwY" height="1" width="1" alt=""/&gt;</content>
  723.    <summary type="xhtml">
  724.      <div xmlns="http://www.w3.org/1999/xhtml"><p>Yesterday I was at my second Brighton SEO conference. I enjoyed it every bit as much as the last one and I’m already looking forward to the next. Here are my notes about the talks I saw. Technical SEO Command Line Hacks For SEO Tom Pool / Slides I misread the description for this. I … </p>
  725. <p class="link-more"><a href="//blog.dave.org.uk/2018/04/brighton-seo-april-2018.html" class="more-link">Continue reading<span class="screen-reader-text"> "Brighton SEO – April 2018"</span></a></p>
  726. <p>The post <a rel="nofollow" href="//blog.dave.org.uk/2018/04/brighton-seo-april-2018.html">Brighton SEO – April 2018</a> appeared first on <a rel="nofollow" href="//blog.dave.org.uk">Davblog</a>.</p>
  727. </div>
  728.    </summary>
  729.    <author>
  730.      <name>Dave Cross</name>
  731.    </author>
  732.    <id>https://blog.dave.org.uk/?p=3669</id>
  733.    <published>2018-04-28T10:28:39Z</published>
  734.    <updated>2018-04-28T10:28:39Z</updated>
  735.    <category term="tech"/>
  736.    <category term="brightonseo"/>
  737.    <category term="conference"/>
  738.    <category term="seo"/>
  739.  </entry>
  740.  <entry>
  741.    <title>perl hacks: Two New Modules</title>
  742.    <link rel="alternate" href="http://feedproxy.google.com/~r/PerlHacks/~3/ZQ4yNddEbcc/" type="text/html"/>
  743.    <content type="xhtml">
  744.      <div xmlns="http://www.w3.org/1999/xhtml"><p>There was a London Perl Mongers meeting at ZPG about ten days ago. I gave a short talk explaining why (and how) a republican like me came to be running a site about the <a href="https://lineofsuccession.co.uk/">Line of Succession to the British Throne</a>. The meeting was great (as they always are) and I think my talk went well (I’m told the videos are imminent). The photo shows the final slide from my talk. I left it up so it was a backdrop for a number of announcements that various people gave just before the break.</p>
  745. <p>In order to write my talk, I revisited the <a href="https://github.com/davorg/succession">source code for my site</a> and, in doing so, I realised that there were a couple of chunks of logic that I could (and should) carve out into separate distributions that I could put on CPAN. I’ve done that over the last couple of days and the modules are now available.</p>
  746. <h2>MooX::Role::JSON_LD</h2>
  747. <p>The first is called <a href="https://metacpan.org/release/MooX-Role-JSON_LD">MooX::Role::JSON_LD</a>. It’s a Moo role that you can add to your classes in order to make it easy to generate JSON-LD from your objects. What’s JSON-LD? I hear you ask. Well, it’s <a href="https://en.wikipedia.org/wiki/JSON-LD">JavaScript Object Notation for Linked Data</a>. The most popular use for it is to add structured data to web sites. Adding structured data to your web site makes it easy for Google (other search engines are available) to understand what your web site is about and that, in turn, will hopefully persuade Google to list your site higher than it otherwise would. You can see JSON-LD in action on a couple of my recent projects – <a href="https://lineofsuccession.co.uk/">https://lineofsuccession.co.uk/</a> and <a href="https://towerbridge.dave.org.uk/">https://towerbridge.dave.org.uk/</a> (you’ll need to look at the source to see it).</p>
  748. <p>I’ve written the module as a Moo role, which means it should be usable in Moose classes too. To add JSON-LD to your class, you need to do three things:</p>
  749. <ul>
  750. <li>Add the role to your class</li>
  751. <li>Define a method called <tt>json_ld_type()</tt> which defines the type of JSON-LD object that you want to generate (see <a href="https://schema.org/">Schema.Org</a> for a list of types)</li>
  752. <li>Define a method called <tt>json_ld_fields()</tt> which defines the fields that you want to include in your JSON-LD. There are a few ways to define that which allow you to do things like mapping an output field to a method of a different name. The details are <a href="https://metacpan.org/pod/MooX::Role::JSON_LD">in the documentation</a>.</li>
  753. </ul>
  754. <p>Your class inherits two methods from the role – <tt>json_ld_data()</tt> returns the data structure which will be encoded into JSON (it’s provided in case you want to massage the data before encoding it) and <tt>json_ld()</tt> which returns the actual encoded JSON in a format that’s suitable for embedding in a web page.</p>
  755. <h2>Genealogy::Relationship</h2>
  756. <p>One of the most satisfying parts of the Line of Succession site to write was the code that shows the relationship between a person in the line and the current sovereign. Prince Charles (currently first in line) is the son of the sovereign and Tāne Lewis (currently thirtieth in line) is the first cousin twice removed of the sovereign.</p>
  757. <p>That code might be useful to other people, so it’s now on CPAN as <a href="https://metacpan.org/release/Genealogy-Relationship">Genealogy::Relationship</a>. To be honest, I’m not sure exactly how useful it will be. The Line of Succession is a rather specialised version of a family tree – because we’re tracing a bloodline, we’re only interested in one parent (which is unlike normal genealogy where we’d be interested in both). It also might be too closely tied to the data model I use on my site – but I have plans to fix that soon.</p>
  758. <p>Currently, because of the requirements of my site, it only goes as far as third cousins (that’s people who share the same great, great grandparents). That’s five generations. But I have an idea to build a site which shows the relationship between any two English or British monarchs back to 1066. I think that’s around forty generations – so I’ll need to expand the coverage somewhat!</p>
  759. <p>But anyway, it’s there and I’d be happy if you tried it and let me know whether it works for you. <a href="https://metacpan.org/pod/Genealogy::Relationship">The documentation</a> should explain all you need to know.</p>
  760. <p>The Line of Succession site doesn’t get much traffic yet – I really need to do more marketing for it. So it’s satisfying to know that some of the code might, at least, be useful outside of the project.</p>
  761. <p>The post <a rel="nofollow" href="https://perlhacks.com/2018/03/two-new-modules/">Two New Modules</a> appeared first on <a rel="nofollow" href="https://perlhacks.com">Perl Hacks</a>.</p>
  762. <img src="http://feeds.feedburner.com/~r/PerlHacks/~4/ZQ4yNddEbcc" height="1" width="1" alt=""/></div>
  763.    </content>
  764.    <summary type="xhtml">
  765.      <div xmlns="http://www.w3.org/1999/xhtml"><p>There was a London Perl Mongers meeting at ZPG about ten days ago. I gave a short talk explaining why (and how) a republican like me came to be running a site about the Line of Succession to the British Throne. The meeting was great (as they always are) and I think my talk went well … </p>
  766. <p class="link-more"><a href="https://perlhacks.com/2018/03/two-new-modules/" class="more-link">Continue reading<span class="screen-reader-text"> "Two New Modules"</span></a></p>
  767. <p>The post <a rel="nofollow" href="https://perlhacks.com/2018/03/two-new-modules/">Two New Modules</a> appeared first on <a rel="nofollow" href="https://perlhacks.com">Perl Hacks</a>.</p>
  768. </div>
  769.    </summary>
  770.    <author>
  771.      <name>Dave Cross</name>
  772.    </author>
  773.    <id>https://perlhacks.com/?p=1812</id>
  774.    <published>2018-03-31T10:57:49Z</published>
  775.    <updated>2018-03-31T10:57:49Z</updated>
  776.    <category term="CPAN"/>
  777.    <category term="cpan"/>
  778.    <category term="genealogy"/>
  779.    <category term="json-ld"/>
  780.    <category term="modules"/>
  781.  </entry>
  782.  <entry>
  783.    <title>cpan: DAVECROSS has released Genealogy-Relationship-0.0.1</title>
  784.    <link rel="alternate" href="https://metacpan.org/release/DAVECROSS/Genealogy-Relationship-0.0.1" type="text/html"/>
  785.    <content type="xhtml">
  786.      <div xmlns="http://www.w3.org/1999/xhtml">calculate the relationship between two people</div>
  787.    </content>
  788.    <author>
  789.      <name>DAVECROSS</name>
  790.    </author>
  791.    <id>https://metacpan.org/release/DAVECROSS/Genealogy-Relationship-0.0.1</id>
  792.    <published>2018-03-31T06:49:07</published>
  793.    <updated>2018-03-31T06:49:07</updated>
  794.  </entry>
  795.  <entry>
  796.    <title>cpan: DAVECROSS has released Array-Compare-v3.0.1</title>
  797.    <link rel="alternate" href="https://metacpan.org/release/DAVECROSS/Array-Compare-v3.0.1" type="text/html"/>
  798.    <content type="xhtml">
  799.      <div xmlns="http://www.w3.org/1999/xhtml">Perl extension for comparing arrays.</div>
  800.    </content>
  801.    <author>
  802.      <name>DAVECROSS</name>
  803.    </author>
  804.    <id>https://metacpan.org/release/DAVECROSS/Array-Compare-v3.0.1</id>
  805.    <published>2018-03-24T11:22:25</published>
  806.    <updated>2018-03-24T11:22:25</updated>
  807.  </entry>
  808.  <entry>
  809.    <title>slideshare: I'm A Republic (Honest!)</title>
  810.    <link rel="alternate" href="https://www.slideshare.net/davorg/im-a-republic-honest" type="text/html"/>
  811.    <content type="html">
  812.        &lt;img alt="" src="//cdn.slidesharecdn.com/ss_thumbnails/succession-180323080646-thumbnail-2.jpg?cb=1521792524" style="border:1px solid #C3E6D8;float:right;" /&gt;&lt;br&gt; A (not entirely serious) talk that I gave at the London Perl Mongers technical meeting in March 2018.
  813.  
  814. It talks about how and why I build a web site listing the line of succession to the British throne back through history.
  815.      </content>
  816.    <summary type="html">
  817.        &lt;img alt="" src="//cdn.slidesharecdn.com/ss_thumbnails/succession-180323080646-thumbnail-2.jpg?cb=1521792524" style="border:1px solid #C3E6D8;float:right;" /&gt;&lt;br&gt; A (not entirely serious) talk that I gave at the London Perl Mongers technical meeting in March 2018.
  818.  
  819. It talks about how and why I build a web site listing the line of succession to the British throne back through history.
  820.      </summary>
  821.    <author>
  822.      <name>[email protected](davorg)</name>
  823.    </author>
  824.    <id>https://www.slideshare.net/davorg/im-a-republic-honest</id>
  825.    <published>2018-03-23T08:06:46Z</published>
  826.    <updated>2018-03-23T08:06:46Z</updated>
  827.  </entry>
  828. </feed>
  829.  
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda