<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.jockcoats.org.uk" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>blogging tools</title>
 <link>http://www.jockcoats.org.uk/taxonomy/term/85/feed</link>
 <description>The taxonomy view with a depth of 0.</description>
 <language>en</language>
<item>
 <title>Interruption of service - for some of you</title>
 <link>http://www.jockcoats.org.uk/interruption_service_some_you</link>
 <description>&lt;p&gt; The 27.6% of you trying to access this site with Internet Explorer 7 (at least - I&amp;#39;m not sure about the other 35.2% using IE6) may have been experiencing problems access my site recently.  It appears that when I added a module to make the list of blogs down the left hand side collapsable so as not to take up so much space IE7 didn&amp;#39;t like some of its Javascript. &lt;/p&gt;
&lt;p&gt; Only one of you contacted me to say there was a problem but since I could reproduce the error 100% of the time when I did look at the site using Internet Exploder 7 on M$ Windoze I presume you will all have been suffering in silence, or at the very least, indifference. &lt;/p&gt;
&lt;p&gt; So I&amp;#39;ve disabled the collapsable side bars for the moment at least and will check whether there&amp;#39;s an update to the relevant modules to cope with IE&amp;#39;s failings. &lt;/p&gt;
&lt;p&gt; However, since most of you come this way from Lib Dem sites, I recommend you upgrade to a more co-operatively developed browser, &lt;a href=&quot;http://www.mozilla.com/&quot; target=&quot;_blank&quot;&gt;such as Firefox&lt;/a&gt;, which would be more fitting for supporters the party of anti-monopoly and free trade. &lt;/p&gt;
</description>
 <comments>http://www.jockcoats.org.uk/interruption_service_some_you#comments</comments>
 <category domain="http://www.jockcoats.org.uk/jocks_categories/blogging_tools">blogging tools</category>
 <category domain="http://www.jockcoats.org.uk/jocks_categories/firefox">Firefox</category>
 <category domain="http://www.jockcoats.org.uk/jocks_categories/ie7">IE7</category>
 <pubDate>Sun, 28 Oct 2007 11:46:06 +0000</pubDate>
 <dc:creator>Jock</dc:creator>
 <guid isPermaLink="false">687 at http://www.jockcoats.org.uk</guid>
</item>
<item>
 <title>Discovering Trackbacks</title>
 <link>http://www.jockcoats.org.uk/discovering_trackbacks</link>
 <description>&lt;p&gt; Though this is not a techno-blog, I do do a fair amount of work behind the scenes myself in php, css and html to get it looking like it does (not a winner I notice!).  But one thing has bugged me for some time... &lt;/p&gt;
&lt;p&gt; The observant amongst you may have noticed that it is developed using the Drupal content management system.  This has lots of add-on modules contributed by nice people all over the world.  One of these is supposed to process &amp;quot;trackbacks&amp;quot;.  You&amp;#39;ll have seen these on others&amp;#39; blogs - where if someone on another site posts something about a story you&amp;#39;ve written, you get a magical little line saying &amp;quot;Such and such a site or blog refers to this post&amp;quot;. &lt;/p&gt;
&lt;p&gt; Well with the Drupal trackback module this only appear to work if people have explicitly &amp;quot;pinged&amp;quot; the trackback URL for the post of mine they are referring to.  And nowadays it seems that very few people actually do this.  When I post on my blog it does ping each site I&amp;#39;ve linked to in the posting, I think (it certainly does at least the first site I refer to) without me having to explicitly tell it to. &lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;/files/u1/uc_large16.gif&quot; alt=&quot;Under construction&quot; hspace=&quot;10&quot; vspace=&quot;10&quot; width=&quot;169&quot; height=&quot;235&quot; align=&quot;right&quot; /&gt; So others see when I have referred to them and can put a link back in to my blog if they want.  But I don&amp;#39;t see automatically when they do, so they don&amp;#39;t get a link back to their post underneath mine.  But I know I am being linked to - I&amp;#39;ve been mentioned in the Lib Dem Voice &amp;quot;Golden Dozen&amp;quot; a few times, and in the Brit Blog Round-up and so on. &lt;/p&gt;
&lt;p&gt; The trackback module claims to be able to discover a site that is referring to mine just from someone clicking on the link in another blog&amp;#39;s article that refers to a post of mine.  But it doesn&amp;#39;t appear to work.  So, while you&amp;#39;ve all been to conference, I&amp;#39;ve been trying my hand at rewriting that module to enable my blog to discover when someone refers to my blog just from click-throughs.  And that&amp;#39;s why I&amp;#39;ve been &amp;quot;blogging lite&amp;quot; this week. &lt;/p&gt;
&lt;p&gt; I&amp;#39;ve not actually got very far yet.  Just setting up a debugging environment took long enough.  And now that I sit down to think about how to do it, I find it much harder than I first thought.  I can see why the module authors have not implemented it yet!  For example - how do I distinguish between a referrer that is a search engine results page, a &amp;quot;real&amp;quot; article that refers to me, or just a &amp;quot;blogroll&amp;quot; type link in a sidebar.  Incidentally - I notice that Lib Dem Voice picks up these sidebar links, as I&amp;#39;ve seen my pages listed as referring to some of their articles when actually they seem to have picked up the feed from the Lib Dem Blogs aggregator I put in my sidebar. &lt;/p&gt;
&lt;p&gt; However, if you&amp;#39;ve stumbled on this because you are also looking for this feature in the Drupal Trackback module, you might be interested in having a look at the logic I think I have finally settled on in the following specification to achieve this: &lt;/p&gt;
&lt;p&gt; Note:  I am going to do this as a Drupal cron job in the trackback module using entries in the Drupal access_log database table.  This is because the processing of each one to check whether it is a real &amp;quot;referral&amp;quot; or a search engine page or a link outside an article like a blogroll will take a little processing time for each page load if I do it when each page is requested by a user agent.  So I guess I&amp;#39;m doing something similar to what Technorati does when it indexes your site when it has received a ping.  Except it won&amp;#39;t be triggered by a ping, but a referrer record in the access_log table.  So here&amp;#39;s the logic in crude &amp;quot;pseudo code&amp;quot;. &lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;START processing:&lt;/li&gt;
&lt;li&gt;When cron runs,&lt;/li&gt;
&lt;li&gt;For each row in the access_log table that accesses a Drupal node and has a referrer URL since the last time cron ran&lt;/li&gt;
&lt;li&gt;Try to fetch an RSS type feed url from the referrer site.  &lt;/li&gt;
&lt;li&gt;If the site doesn&amp;#39;t provide a feed url, then it&amp;#39;s likely it&amp;#39;s not a blog or news type site and we can stop processing.&lt;/li&gt;
&lt;li&gt;If it does provide a feed url, fetch the feed and parse it.&lt;/li&gt;
&lt;li&gt;For each article in that feed check whether it contains a reference to the Drupal node referred to in the access_log record.&lt;/li&gt;
&lt;li&gt;If it does not contain a reference to said Drupal node we can stop processing.&lt;/li&gt;
&lt;li&gt;If it does, extract an excerpt and title from the article in the feed and save the whole lot into the trackbacks_received table.  It should then appear under the node on my site when it is viewed.&lt;/li&gt;
&lt;li&gt;STOP processing.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt; As a slight aside, I&amp;#39;m wondering how to check comments on others&amp;#39; posts as well.  I&amp;#39;m not quite clear whether all types of feed have a way of discovering the comment feed, if one is available, for each article in the main feed.  If so it can probably be done. &lt;/p&gt;
</description>
 <comments>http://www.jockcoats.org.uk/discovering_trackbacks#comments</comments>
 <category domain="http://www.jockcoats.org.uk/jocks_categories/blogging_tools">blogging tools</category>
 <category domain="http://www.jockcoats.org.uk/jocks_categories/drupal">drupal</category>
 <category domain="http://www.jockcoats.org.uk/jocks_categories/trackback_module">trackback module</category>
 <pubDate>Wed, 19 Sep 2007 23:58:45 +0000</pubDate>
 <dc:creator>Jock</dc:creator>
 <guid isPermaLink="false">631 at http://www.jockcoats.org.uk</guid>
</item>
<item>
 <title>Ecto 3 Alpha</title>
 <link>http://www.jockcoats.org.uk/ecto_3_alpha</link>
 <description>&lt;p&gt;I rarely post about computer toys and goodies, but I have been using &lt;a href=&quot;http://infinite-sushi.com/software/ecto/&quot; target=&quot;_blank&quot;&gt;ecto&lt;/a&gt; as my blogging client for ages now and I just suddenly wondered tonight how things were going with the upgrade to ecto version 3. And lo and behold I found that this very day Adriaan has put out an &lt;a href=&quot;http://infinite-sushi.com/software/ecto/news/2007/08/ecto3_alpha.php&quot; target=&quot;_blank&quot;&gt;alpha release&lt;/a&gt; of version 3 for Mac OS X.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m a techie, and I don&amp;#39;t mind playing around with alpha software, though it&amp;#39;s not for everyone, but I&amp;#39;ve downloaded it and at first site it looks great. A real improvement on an already very good tool. And this is the first post with ecto 3.&lt;/p&gt;
&lt;p&gt;extended &lt;!--extended--&gt; &lt;/p&gt;
</description>
 <comments>http://www.jockcoats.org.uk/ecto_3_alpha#comments</comments>
 <category domain="http://www.jockcoats.org.uk/jocks_categories/blogging_tools">blogging tools</category>
 <category domain="http://www.jockcoats.org.uk/jocks_categories/ecto">ecto</category>
 <pubDate>Tue, 14 Aug 2007 02:27:29 +0000</pubDate>
 <dc:creator>Jock</dc:creator>
 <guid isPermaLink="false">557 at http://www.jockcoats.org.uk</guid>
</item>
</channel>
</rss>
