<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>rant</title>
  <link rel="alternate" type="text/html" href="http://tumbleweed.org.za/tags/rant"/>
  <link rel="self" type="application/atom+xml" href="http://tumbleweed.org.za/taxonomy/term/134/atom/feed"/>
  <id>http://tumbleweed.org.za/taxonomy/term/134/atom/feed</id>
  <updated>2008-02-10T12:43:49+00:00</updated>
  <entry>
    <title>International 419-SMS</title>
    <link rel="alternate" type="text/html" href="http://tumbleweed.org.za/2008/09/30/international-419-sms" />
    <id>http://tumbleweed.org.za/2008/09/30/international-419-sms</id>
    <published>2008-09-30T09:54:43+00:00</published>
    <updated>2008-12-10T16:37:44+00:00</updated>
    <author>
      <name>tumbleweed</name>
    </author>
    <category term="419" />
    <category term="cell-phone" />
    <category term="rant" />
    <category term="sms" />
    <category term="spam" />
    <summary type="html"><![CDATA[<p>I don&#8217;t know if I get more spam than other people because my phone numbers <a href="/me/contact">are public</a>, or if I&#8217;m just more of a touchy, grouchy git than other people and just react to every spam&nbsp;I&nbsp;get.</p>

<p>So, here is another <span class="caps"><span class="caps">SPAM</span></span>-related&nbsp;post.</p>

<p>I just got an <span class="caps"><span class="caps">SMS</span></span> from&nbsp;+256715316646&nbsp;saying:</p>

<blockquote>
  <p><span class="caps"><span class="caps">CONGRATULATION</span></span>- You have won a <span class="caps"><span class="caps">TOYOTA</span></span> <span class="caps"><span class="caps">LANDCRUISER</span></span> <span class="caps"><span class="caps">VX</span></span> worth $80,000 <span class="caps"><span class="caps">US</span></span> <span class="caps"><span class="caps">DOLLARS</span></span>.Contact the manager <span class="caps"><span class="caps">DR</span></span>: <span class="caps"><span class="caps">STEPHEN</span></span> through +254720043297 (<span class="caps"><span class="caps">JAPAN</span></span> <span class="caps"><span class="caps">INT</span></span>. <span class="caps"><span class="caps">MOTORS</span></span>)&nbsp;<span class="caps"><span class="caps">THANKS</span></span>.</p>
</blockquote>

<p>Look closely. Firstly, it&#8217;s a 419-scam via <span class="caps"><span class="caps">SMS</span></span>. I&#8217;ve never seen one of those before. 2nd, it&#8217;s from Uganda (a Uganda Telecom cellphone number). Third, it wants me to call someone in Kenya (a Safaricom&nbsp;cell&nbsp;number).</p>

<p>What on earth does one do to stop such things? Either this is run by a group with people on the ground in both countries, or they are using online bulk-<span class="caps"><span class="caps">SMS</span></span> services. But International SMSs aren&#8217;t cheap. And I have no idea who to complain to about this. Let&#8217;s hope that this kind of spam doesn&#8217;t become common, because it&#8217;s virtually unstoppable if it does (like International&nbsp;e-mail&nbsp;spam).</p>

<p><strong>Update</strong>: This page seems to have become a rant-board for people getting this spam. If it isn&#8217;t plainly obvious, here&#8217;s what to do: <strong>nothing</strong>. Don&#8217;t respond, don&#8217;t give them details, <strong>it&#8217;s a scam!</strong>.</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>I don&#8217;t know if I get more spam than other people because my phone numbers <a href="/me/contact">are public</a>, or if I&#8217;m just more of a touchy, grouchy git than other people and just react to every spam I&nbsp;get.</p>

<p>So, here is another <span class="caps">SPAM</span>-related&nbsp;post.</p>

<p>I just got an <span class="caps">SMS</span> from +256715316646&nbsp;saying:</p>

<blockquote>
  <p><span class="caps">CONGRATULATION</span>- You have won a <span class="caps">TOYOTA</span> <span class="caps">LANDCRUISER</span> <span class="caps">VX</span> worth $80,000 <span class="caps">US</span> <span class="caps">DOLLARS</span>.Contact the manager <span class="caps">DR</span>: <span class="caps">STEPHEN</span> through +254720043297 (<span class="caps">JAPAN</span> <span class="caps">INT</span>. <span class="caps">MOTORS</span>)&nbsp;<span class="caps">THANKS</span>.</p>
</blockquote>

<p>Look closely. Firstly, it&#8217;s a 419-scam via <span class="caps">SMS</span>. I&#8217;ve never seen one of those before. 2nd, it&#8217;s from Uganda (a Uganda Telecom cellphone number). Third, it wants me to call someone in Kenya (a Safaricom cell&nbsp;number).</p>

<p>What on earth does one do to stop such things? Either this is run by a group with people on the ground in both countries, or they are using online bulk-<span class="caps">SMS</span> services. But International SMSs aren&#8217;t cheap. And I have no idea who to complain to about this. Let&#8217;s hope that this kind of spam doesn&#8217;t become common, because it&#8217;s virtually unstoppable if it does (like International e-mail&nbsp;spam).</p>

<p><strong>Update</strong>: This page seems to have become a rant-board for people getting this spam. If it isn&#8217;t plainly obvious, here&#8217;s what to do: <strong>nothing</strong>. Don&#8217;t respond, don&#8217;t give them details, <strong>it&#8217;s a scam!</strong>.</p>
    ]]></content>
  </entry>
  <entry>
    <title>Ctrl-Alt-shortcuts considered harmful</title>
    <link rel="alternate" type="text/html" href="http://tumbleweed.org.za/2008/09/26/ctrl-alt-shortcuts-considered-harmful" />
    <id>http://tumbleweed.org.za/2008/09/26/ctrl-alt-shortcuts-considered-harmful</id>
    <published>2008-09-26T18:32:12+00:00</published>
    <updated>2008-09-26T23:02:41+00:00</updated>
    <author>
      <name>tumbleweed</name>
    </author>
    <category term="gnome" />
    <category term="linux" />
    <category term="rant" />
    <category term="ubuntu" />
    <summary type="html"><![CDATA[<p>I&#8217;ve <a href="/2007/11/10/gnome-virtual-desktop-bindings">written about this before</a>, but Ctrl-Alt-workspace switching key-presses nail&nbsp;me&nbsp;routinely.</p>

<p>Let&#8217;s go through&nbsp;some&nbsp;history:</p>

<p>We have Ctrl-Alt-Delete, the &#8220;three-fingered-salute&#8221;, meaning reboot, right? That combination was designed to <em><span class="caps"><span class="caps">NEVER</span></span></em> be pressed by accident. And it never used&nbsp;to&nbsp;be.</p>

<p>The X guys needed a kill-X key-press, as things can sometimes get broken in X. So they chose Ctrl-Alt-Backspace, which is also a pretty sensible combination. It&#8217;s very similar to Ctrl-Alt-Delete, so we remember it, and backspace has milder connotations than delete, so we understand it to mean that it&#8217;ll only kill a <em>part</em> of&nbsp;the&nbsp;system.</p>

<p>X also has some other Ctl-Alt- shortcuts. Some of these are also suitably obscure, i.e. NumPad+ and NumPad-. Others like Ctrl-Alt-F1 mean change to virtual console 1. That one might do by accident, if you are an old WordPerfect user, but should be safe enough otherwise. They were designed to look like big brothers of (and even work as) standard <span class="caps"><span class="caps">VT</span></span>-changing&nbsp;behaviour.</p>

<p>For changing workspaces, Alt-F1 style key-presses were used, mimicing <span class="caps"><span class="caps">VT</span></span>-changing key-presses. This is great for *nix users, but people coming from Windows expect Alt-F4 to close a program, not take them to&nbsp;workspace&nbsp;4.</p>

<p>So <span class="caps"><span class="caps">GNOME</span></span> came along, and decided that instead, they&#8217;d use Ctrl-Alt-Arrow key-presses to change workspace. That&#8217;s fine, but it&#8217;s a pretty common action, so I&#8217;m often holding down Ctrl-Alt without even thinking about it. If I start editing something and press delete/backspace, before I&#8217;ve released Ctrl-Alt, <strong>boom</strong>! And I run screaming and write a&nbsp;blog&nbsp;post.</p>

<p>Now, I know that Ctl-Alt-{Delete,Backspace} can be disabled (even if the latter is a little tricky to do), but I&#8217;d really like to <em>change</em> them. I <em>like</em> to be able to kill X without using another machine and ssh, I just <em>don&#8217;t like</em> this to happen by accident. And no, the solution isn&#8217;t for me to change my workspace-changing keys, because this problem must affect every <span class="caps"><span class="caps">GNOME</span></span> user, not&nbsp;just&nbsp;me.</p>

<p>Dangerous key-presses should be really unlikely key-presses. Alt-SysRq- key-presses are good in this regard, they&#8217;ll <em>always</em> be unlikely. (Oh, and they are&nbsp;insanely&nbsp;useful.)</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>I&#8217;ve <a href="/2007/11/10/gnome-virtual-desktop-bindings">written about this before</a>, but Ctrl-Alt-workspace switching key-presses nail me&nbsp;routinely.</p>

<p>Let&#8217;s go through some&nbsp;history:</p>

<p>We have Ctrl-Alt-Delete, the &#8220;three-fingered-salute&#8221;, meaning reboot, right? That combination was designed to <em><span class="caps">NEVER</span></em> be pressed by accident. And it never used to&nbsp;be.</p>

<p>The X guys needed a kill-X key-press, as things can sometimes get broken in X. So they chose Ctrl-Alt-Backspace, which is also a pretty sensible combination. It&#8217;s very similar to Ctrl-Alt-Delete, so we remember it, and backspace has milder connotations than delete, so we understand it to mean that it&#8217;ll only kill a <em>part</em> of the&nbsp;system.</p>

<p>X also has some other Ctl-Alt- shortcuts. Some of these are also suitably obscure, i.e. NumPad+ and NumPad-. Others like Ctrl-Alt-F1 mean change to virtual console 1. That one might do by accident, if you are an old WordPerfect user, but should be safe enough otherwise. They were designed to look like big brothers of (and even work as) standard <span class="caps">VT</span>-changing&nbsp;behaviour.</p>

<p>For changing workspaces, Alt-F1 style key-presses were used, mimicing <span class="caps">VT</span>-changing key-presses. This is great for *nix users, but people coming from Windows expect Alt-F4 to close a program, not take them to workspace&nbsp;4.</p>

<p>So <span class="caps">GNOME</span> came along, and decided that instead, they&#8217;d use Ctrl-Alt-Arrow key-presses to change workspace. That&#8217;s fine, but it&#8217;s a pretty common action, so I&#8217;m often holding down Ctrl-Alt without even thinking about it. If I start editing something and press delete/backspace, before I&#8217;ve released Ctrl-Alt, <strong>boom</strong>! And I run screaming and write a blog&nbsp;post.</p>

<p>Now, I know that Ctl-Alt-{Delete,Backspace} can be disabled (even if the latter is a little tricky to do), but I&#8217;d really like to <em>change</em> them. I <em>like</em> to be able to kill X without using another machine and ssh, I just <em>don&#8217;t like</em> this to happen by accident. And no, the solution isn&#8217;t for me to change my workspace-changing keys, because this problem must affect every <span class="caps">GNOME</span> user, not just&nbsp;me.</p>

<p>Dangerous key-presses should be really unlikely key-presses. Alt-SysRq- key-presses are good in this regard, they&#8217;ll <em>always</em> be unlikely. (Oh, and they are insanely&nbsp;useful.)</p>
    ]]></content>
  </entry>
  <entry>
    <title>Spelunking in M&amp;G&#039;s Zapiro Archive</title>
    <link rel="alternate" type="text/html" href="http://tumbleweed.org.za/2008/09/13/spelunking-mgs-zapiro-archive" />
    <id>http://tumbleweed.org.za/2008/09/13/spelunking-mgs-zapiro-archive</id>
    <published>2008-09-13T00:24:32+00:00</published>
    <updated>2008-09-18T12:40:34+00:00</updated>
    <author>
      <name>tumbleweed</name>
    </author>
    <category term="mg" />
    <category term="rant" />
    <category term="web-design" />
    <category term="zapiro" />
    <summary type="html"><![CDATA[<p>Those who follow me will know that I used to maintain a <a href="http://zapiro.rivera.za.net/">web frontend</a> to the <a href="http://www.mg.co.za/">Mail <span class="amp">&amp;</span> Guardian Online</a>&nbsp;Zapiro&nbsp;archive.</p>

<p>M&amp;G used to have a rather crufty website. Subscriber-only content was trivial to access (for non-subscribers), URLs were ugly, and dinosaurs roamed in the far corners of the site.
It had <span class="caps"><span class="caps">RSS</span></span> feeds, but not an <span class="caps"><span class="caps">RSS</span></span> feed for the zapiro archive (or any specific-interest <span class="caps"><span class="caps">RSS</span></span> feeds for that matter).
I don&#8217;t check websites, I read <span class="caps"><span class="caps">RSS</span></span>&nbsp;feeds.</p>

<p>Me being a young geek with a little too much spare time, I put together <a href="http://zapiro.rivera.za.net/">zapiro.rivera.za.net</a>, as a ~200-line <span class="caps"><span class="caps">PHP</span></span> script (with no <span class="caps"><span class="caps">SQL</span></span> <span class="caps"><span class="caps">DB</span></span>) that was really nice to use (in my books) and gave me a Zapiro <span class="caps"><span class="caps">RSS</span></span>&nbsp;feed.</p>

<p>When they noticed, the powers at be at M&amp;G weren&#8217;t too impressed with it, because it deprived them of eyeballs (and hot-linked <em>their</em> Zapiro images).
However I felt satisfied that I was merely providing a fair-use access to their content and allowing people to follow it who wouldn&#8217;t have been able to otherwise.
The site never got much traffic, so thus far it&#8217;s not been a&nbsp;serious&nbsp;problem.</p>

<p>Around June this year, M&amp;G redesigned their website, and I don&#8217;t think I even noticed (did I say something about them not having decent feeds?).
This redesign broke the machinery in <a href="http://zapiro.rivera.za.net/">zapiro.rivera.za.net</a> but I didn&#8217;t notice that because Zapiro had taken a sabbatical earlier this year, and was going weeks without&nbsp;posting&nbsp;cartoons.</p>

<p>Enough back-story.
Point is I took a look at the new <a href="http://www.mg.co.za/cartoons/zapiro">M&amp;G Zapiro Archive</a> this evening and was shocked. Before I go into all my problems with it, let me just disclaim that they are rather nit-picky but if these problems weren&#8217;t there they site would be a hell of a lot&nbsp;more&nbsp;usable:</p>

<ul>
<li>There are still no useful <span class="caps"><span class="caps">RSS</span></span> feeds. There is a rather terse selection of <a href="http://www.mg.co.za/page/rss-feeds">general feeds</a>.</li>
<li>The Archive menu only goes back to 2001. M&amp;G has zapiro cartoons going back&nbsp;to&nbsp;1999.</li>
<li>Archive menu URLs are in /Month/Year format. Did anyone even think about <span class="caps"><span class="caps">URL</span></span>-scheme when they&nbsp;were&nbsp;designing?</li>
<li>Their tagging feature while using multi-select widgets only allows single tags to be selected (oh, and it&nbsp;requires&nbsp;Javascript)</li>
<li>Each cartoon has two URLs. Ok, I guess they weren&#8217;t thinking about <span class="caps"><span class="caps">URL</span></span>&nbsp;scheme.</li>
</ul>

<blockquote>
  <ol>
  <li>Today&#8217;s cartoon has the <a href="http://www.mg.co.za/zapiro/all/">/zapiro/all/</a> <span class="caps"><span class="caps">URL</span></span>. Yesterdays <a href="http://www.mg.co.za/zapiro/all/1">/zapiro/all/1</a>, etc. going back to the begging of time (currently residing at <a href="http://www.mg.co.za/zapiro/all/1870">/zapiro/all/1870</a>). Way to go with <a href="http://en.wikipedia.org/wiki/Permalink">permalinks</a> guys. Oh and did you notice that they are all titled&nbsp;&#8220;Latest&nbsp;Zapiro&#8221;?</li>
  <li>Clicking on the &#8220;Comments&#8221; link or using the &#8220;Archive&#8221; menu below takes you to something like <a href="http://www.mg.co.za/zapiro/fullcartoon/1">/zapiro/fullcartoon/1</a>. Oh, except <a href="http://www.mg.co.za/zapiro/fullcartoon/1">1</a> gives us a non-existent cartoon at the beginning of this Unix Epoch. But take a closer look: it has tags associated. Can anyone say&nbsp;<span class="caps"><span class="caps">WTF</span></span>?.</li>
  </ol>
</blockquote>

<p>The insanity continues: <a href="http://www.mg.co.za/zapiro/fullcartoon/2">2</a> gives us a cartoon from September 1999. <a href="http://www.mg.co.za/zapiro/fullcartoon/3">3</a>-<a href="http://www.mg.co.za/zapiro/fullcartoon/25">25</a> are more non-existent wonders, and then things go backwards in time until <a href="http://www.mg.co.za/zapiro/fullcartoon/36">36</a> which jumps us to June 3 2008. (Hmm, I think that may have been around the M&amp;G redesign&nbsp;launch&nbsp;date.)</p>

<p>We move forward in time until <a href="http://www.mg.co.za/zapiro/fullcartoon/40">40</a>, when we start moving backwards from May 2008, through many seas of well-tagged gaps, to &#8230; <em>well somewhere</em>. (<span class="caps"><span class="caps">OK</span></span>, so I got bored and didn&#8217;t manually crawl 2000 pages, but would you?)
Some cartoons are in totally the wrong position, we randomly move backwards and forwards&nbsp;and&nbsp;sideways.</p>

<p><em>Finally</em> things settle down, and we go forwards again (with gaps of course) from <a href="http://www.mg.co.za/zapiro/fullcartoon/2054">2054</a> to today&#8217;s cartoon at <a href="http://www.mg.co.za/zapiro/fullcartoon/2101">2101</a>&nbsp;&mdash; a fine Zapiro specimen if every I&nbsp;saw&nbsp;one.</p>

<p>Why was I doing all this mind-numbing crawling you ask?
Well I wanted to know if I could do anything to make my Zapiro scraper work again.
The answer? <em>Not simply</em>.
They don&#8217;t have any sensible way to locate the cartoon from a specific day, short of crawling the entire archive and recording the URLs found.
I don&#8217;t think there <em>is</em> any logic to this <span class="caps"><span class="caps">LSD</span></span>-induced <span class="caps"><span class="caps">URL</span></span>&nbsp;scheme.</p>

<p><span class="caps"><span class="caps">URL</span></span> schemes matter.
This seems to be something that the big guns haven&#8217;t noticed.
I don&#8217;t think it&#8217;s a co-incidence that the most expensive CMSs out there have the worst URLs, whereas Wordpress and Drupal (with pathauto) encourage sensible URLs and are&nbsp;Open&nbsp;Source.</p>

<p>Sure, most users don&#8217;t change what they see in the address bar, but if people are going to link into your site, you should provide nice permalinks.
Then, if you want anyone to build anything on top of your site (where anyone includes yourself), it would really help if you had a sane <span class="caps"><span class="caps">URL</span></span> scheme.
Finally, it gives you&nbsp;geek-cred.&nbsp;:-)</p>

<p>While I think of a better way to get my scraper working again,&nbsp;Happy&nbsp;Spelunking!</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>Those who follow me will know that I used to maintain a <a href="http://zapiro.rivera.za.net/">web frontend</a> to the <a href="http://www.mg.co.za/">Mail <span class="amp">&amp;</span> Guardian Online</a> Zapiro&nbsp;archive.</p>

<p>M&amp;G used to have a rather crufty website. Subscriber-only content was trivial to access (for non-subscribers), URLs were ugly, and dinosaurs roamed in the far corners of the site.
It had <span class="caps">RSS</span> feeds, but not an <span class="caps">RSS</span> feed for the zapiro archive (or any specific-interest <span class="caps">RSS</span> feeds for that matter).
I don&#8217;t check websites, I read <span class="caps">RSS</span>&nbsp;feeds.</p>

<p>Me being a young geek with a little too much spare time, I put together <a href="http://zapiro.rivera.za.net/">zapiro.rivera.za.net</a>, as a ~200-line <span class="caps">PHP</span> script (with no <span class="caps">SQL</span> <span class="caps">DB</span>) that was really nice to use (in my books) and gave me a Zapiro <span class="caps">RSS</span>&nbsp;feed.</p>

<p>When they noticed, the powers at be at M&amp;G weren&#8217;t too impressed with it, because it deprived them of eyeballs (and hot-linked <em>their</em> Zapiro images).
However I felt satisfied that I was merely providing a fair-use access to their content and allowing people to follow it who wouldn&#8217;t have been able to otherwise.
The site never got much traffic, so thus far it&#8217;s not been a serious&nbsp;problem.</p>

<p>Around June this year, M&amp;G redesigned their website, and I don&#8217;t think I even noticed (did I say something about them not having decent feeds?).
This redesign broke the machinery in <a href="http://zapiro.rivera.za.net/">zapiro.rivera.za.net</a> but I didn&#8217;t notice that because Zapiro had taken a sabbatical earlier this year, and was going weeks without posting&nbsp;cartoons.</p>

<p>Enough back-story.
Point is I took a look at the new <a href="http://www.mg.co.za/cartoons/zapiro">M&amp;G Zapiro Archive</a> this evening and was shocked. Before I go into all my problems with it, let me just disclaim that they are rather nit-picky but if these problems weren&#8217;t there they site would be a hell of a lot more&nbsp;usable:</p>

<ul>
<li>There are still no useful <span class="caps">RSS</span> feeds. There is a rather terse selection of <a href="http://www.mg.co.za/page/rss-feeds">general feeds</a>.</li>
<li>The Archive menu only goes back to 2001. M&amp;G has zapiro cartoons going back to&nbsp;1999.</li>
<li>Archive menu URLs are in /Month/Year format. Did anyone even think about <span class="caps">URL</span>-scheme when they were&nbsp;designing?</li>
<li>Their tagging feature while using multi-select widgets only allows single tags to be selected (oh, and it requires&nbsp;Javascript)</li>
<li>Each cartoon has two URLs. Ok, I guess they weren&#8217;t thinking about <span class="caps">URL</span>&nbsp;scheme.</li>
</ul>

<blockquote>
  <ol>
  <li>Today&#8217;s cartoon has the <a href="http://www.mg.co.za/zapiro/all/">/zapiro/all/</a> <span class="caps">URL</span>. Yesterdays <a href="http://www.mg.co.za/zapiro/all/1">/zapiro/all/1</a>, etc. going back to the begging of time (currently residing at <a href="http://www.mg.co.za/zapiro/all/1870">/zapiro/all/1870</a>). Way to go with <a href="http://en.wikipedia.org/wiki/Permalink">permalinks</a> guys. Oh and did you notice that they are all titled &#8220;Latest&nbsp;Zapiro&#8221;?</li>
  <li>Clicking on the &#8220;Comments&#8221; link or using the &#8220;Archive&#8221; menu below takes you to something like <a href="http://www.mg.co.za/zapiro/fullcartoon/1">/zapiro/fullcartoon/1</a>. Oh, except <a href="http://www.mg.co.za/zapiro/fullcartoon/1">1</a> gives us a non-existent cartoon at the beginning of this Unix Epoch. But take a closer look: it has tags associated. Can anyone say&nbsp;<span class="caps">WTF</span>?.</li>
  </ol>
</blockquote>

<p>The insanity continues: <a href="http://www.mg.co.za/zapiro/fullcartoon/2">2</a> gives us a cartoon from September 1999. <a href="http://www.mg.co.za/zapiro/fullcartoon/3">3</a>-<a href="http://www.mg.co.za/zapiro/fullcartoon/25">25</a> are more non-existent wonders, and then things go backwards in time until <a href="http://www.mg.co.za/zapiro/fullcartoon/36">36</a> which jumps us to June 3 2008. (Hmm, I think that may have been around the M&amp;G redesign launch&nbsp;date.)</p>

<p>We move forward in time until <a href="http://www.mg.co.za/zapiro/fullcartoon/40">40</a>, when we start moving backwards from May 2008, through many seas of well-tagged gaps, to &#8230; <em>well somewhere</em>. (<span class="caps">OK</span>, so I got bored and didn&#8217;t manually crawl 2000 pages, but would you?)
Some cartoons are in totally the wrong position, we randomly move backwards and forwards and&nbsp;sideways.</p>

<p><em>Finally</em> things settle down, and we go forwards again (with gaps of course) from <a href="http://www.mg.co.za/zapiro/fullcartoon/2054">2054</a> to today&#8217;s cartoon at <a href="http://www.mg.co.za/zapiro/fullcartoon/2101">2101</a>&nbsp;&mdash; a fine Zapiro specimen if every I saw&nbsp;one.</p>

<p>Why was I doing all this mind-numbing crawling you ask?
Well I wanted to know if I could do anything to make my Zapiro scraper work again.
The answer? <em>Not simply</em>.
They don&#8217;t have any sensible way to locate the cartoon from a specific day, short of crawling the entire archive and recording the URLs found.
I don&#8217;t think there <em>is</em> any logic to this <span class="caps">LSD</span>-induced <span class="caps">URL</span>&nbsp;scheme.</p>

<p><span class="caps">URL</span> schemes matter.
This seems to be something that the big guns haven&#8217;t noticed.
I don&#8217;t think it&#8217;s a co-incidence that the most expensive CMSs out there have the worst URLs, whereas Wordpress and Drupal (with pathauto) encourage sensible URLs and are Open&nbsp;Source.</p>

<p>Sure, most users don&#8217;t change what they see in the address bar, but if people are going to link into your site, you should provide nice permalinks.
Then, if you want anyone to build anything on top of your site (where anyone includes yourself), it would really help if you had a sane <span class="caps">URL</span> scheme.
Finally, it gives you geek-cred.&nbsp;:-)</p>

<p>While I think of a better way to get my scraper working again, Happy&nbsp;Spelunking!</p>
    ]]></content>
  </entry>
  <entry>
    <title>An open letter to NatWest bank</title>
    <link rel="alternate" type="text/html" href="http://tumbleweed.org.za/2008/05/28/natwest-letter" />
    <id>http://tumbleweed.org.za/2008/05/28/natwest-letter</id>
    <published>2008-05-28T16:27:30+00:00</published>
    <updated>2008-06-03T16:15:15+00:00</updated>
    <author>
      <name>tumbleweed</name>
    </author>
    <category term="banking" />
    <category term="natwest" />
    <category term="rant" />
    <summary type="html"><![CDATA[<blockquote>
  <p>Subject: Strict&nbsp;Browser&nbsp;restrictions</p>
  
  <p>Hi, I&#8217;m a customer of yours, and a <span class="caps"><span class="caps">GNU</span></span>/Linux user who gets frequently
  frustrated by your&nbsp;browser&nbsp;detection.</p>
  
  <p>Basically, the problem is that very few web browsers have been
  certified with your website. Now, I have no real issue with that,
  nobody has enough time to try <em>every</em> web browser in the world, and
  adjust their websites to fit around every browser&#8217;s bugs. <em>But</em> that
  doesn&#8217;t mean it&#8217;s acceptable to reject your users with a message like
  &#8220;The Internet browser you are using is not supported by online banking.
  Use the link below to see the complete list of browsers&nbsp;we&nbsp;support.&#8221;</p>
  
  <p>Firstly, the browsers I use <em>are</em> listed as being supported on your
  list <a href="http://www.natwest.com/personal/day-to-day/online-banking/g1/faqs.ashx">[1]</a>:</p>
  
  <ul>
  <li>On this laptop, I use a Firefox 3.0 beta. Firefox 3.0 is listed is
  being supported, and it works (if I tweak it to identify it as
  Firefox 2.0, then I can use the site&nbsp;just&nbsp;fine).</li>
  <li>On my desktops, I use Iceweasel 2.x. Iceweasel is Firefox with a
  different name, to get around trademark issues. Ask your
  Linux-techies, they should know about it. Again, it works&nbsp;as&nbsp;expected.</li>
  </ul>
  
  <p>Secondly, <a href="http://www.natwest.com/personal/day-to-day/online-banking/g1/faqs.ashx">[1]</a> states: &#8220;Netscape, Mozilla and Firefox users with other
  operating systems such as Linux may also be able to access the
  service.&#8221; How are we supposed to access the service if you deny&nbsp;us&nbsp;access?</p>
  
  <p>More generally, locking out unknown browsers goes completely against
  your policy of Accessibility <a href="http://www.natwest.com/popup/global/access.ashx">[2]</a>. While the <span class="caps"><span class="caps">WAI</span></span> <a href="http://www.w3.org/TR/WAI-WEBCONTENT">[3]</a> doesn&#8217;t
  specifically recommend against turning away unknown browsers, I think
  you&#8217;ll find that&#8217;s because the authors didn&#8217;t even <em>dream</em> of
  <em>considering</em> such a thing. The <em>entire point</em> of <span class="caps"><span class="caps">WAI</span></span>, is to make your
  site as portable as possible, and to work for everyone with a far
  wider variety of user agents than you could ever&nbsp;test&nbsp;with.</p>
  
  <p>I don&#8217;t know how you can call yourself <span class="caps"><span class="caps">WAI</span></span>-compliant and reject
  un-&#8220;certified&#8221; browsers. Your webmasters should hang their heads&nbsp;in&nbsp;shame.</p>
  
  <p>Now, I don&#8217;t intend to rant any more than that, because that&#8217;s the
  only problem I have with your site (and your service). Beyond this
  little niggle (which stops me being able to bank, without configuring
  my browser to lie) I&#8217;m very impressed with&nbsp;your&nbsp;services.</p>
  
  <p>Please sort this out, it&#8217;ll turn me back into a&nbsp;happy&nbsp;customer.</p>
  
  <p><span class="caps"><span class="caps">SR</span></span></p>
  
  <p><span class="caps"><span class="caps">PS</span></span>: I&#8217;d have sent this by e-mail, where I&#8217;d, but you don&#8217;t provide any
     e-mail contact details on your site.
  <span class="caps"><span class="caps">PPS</span></span>: Only providing a small feedback form doesn&#8217;t help users give you
      real feedback, it just intimidates and&nbsp;irritates&nbsp;them.</p>
  
  <p>[1]: <a href="http://www.natwest.com/personal/day-to-day/online-banking/g1/faqs.ashx">http://www.natwest.com/personal/day-to-day/online-banking/g1/faqs.ashx</a><br />
  [2]: <a href="http://www.natwest.com/popup/global/access.ashx">http://www.natwest.com/popup/global/access.ashx</a><br />
  [3]: <a href="http://www.w3.org/TR/WAI-WEBCONTENT">http://www.w3.org/<span class="caps"><span class="caps">TR</span></span>/<span class="caps"><span class="caps">WAI</span></span>-<span class="caps"><span class="caps">WEBCONTENT</span></span>/</a></p>
  
  <p>&#8212;<br />
  Stefano Rivera<br />
   http://rivera.za.net/<br />
   H: +27 21 794 7937   C: +27 72&nbsp;419&nbsp;8559</p>
</blockquote>

<p>Now, that was rather harsh to them, but this has been irritating me for ages. Then, when I did decide to <em>do something</em> about it, I was rather worked up,&nbsp;and&nbsp;ranted.</p>

<p>I got a call back from NatWest this morning, and was basically told that they aren&#8217;t going to change anything. I can understand their position, but I don&#8217;t that they were seeing mine. (Oh, and I think they&nbsp;are&nbsp;wrong.)</p>

<p>The reasons I was given for this non-approved&nbsp;lockout&nbsp;are:</p>

<ol>
<li>Support. But of course, if your web site is decent, then you shouldn&#8217;t have any support issues. (<span class="caps"><span class="caps">OK</span></span>, that&#8217;s rather utopic, but the kind of people who use alternative browsers will be <span class="caps"><span class="caps">OK</span></span> in&nbsp;such&nbsp;situations).</li>
<li>Security. Apparently Opera caches previously visited pages as they were. Clicking back doesn&#8217;t revalidate with the server, and so someone who&#8217;s logged out of their Internet banking and gone on to google still has their private data visible in the history. Anyone coming up to their computer can go back&nbsp;to&nbsp;it.</li>
</ol>

<p>Now, I don&#8217;t think point 2 is NatWest&#8217;s problem. If Opera doesn&#8217;t support revalidation, then Opera must fix it. If Opera do, and NatWest doesn&#8217;t send the correct Pragma headers, then it&#8217;s&nbsp;NatWest&#8217;s&nbsp;problem.</p>

<p>But still, that doesn&#8217;t mean you lock-out untested browers, dammit. <em>Especially</em> if you call yourself&nbsp;<span class="caps"><span class="caps">WAI</span></span>-compliant.</p>

<p>I&#8217;d love to see some feedback from a <span class="caps"><span class="caps">WAI</span></span> board member on this type of issue. I don&#8217;t think the <span class="caps"><span class="caps">WAI</span></span> specs&nbsp;address&nbsp;it.</p>

<p>Oh, and everyone, please stand up for your right to browse the web however you see fit. If more people did so, these kind of issues would crop up&nbsp;less&nbsp;often.</p>
    ]]></summary>
    <content type="html"><![CDATA[<blockquote>
  <p>Subject: Strict Browser&nbsp;restrictions</p>
  
  <p>Hi, I&#8217;m a customer of yours, and a <span class="caps">GNU</span>/Linux user who gets frequently
  frustrated by your browser&nbsp;detection.</p>
  
  <p>Basically, the problem is that very few web browsers have been
  certified with your website. Now, I have no real issue with that,
  nobody has enough time to try <em>every</em> web browser in the world, and
  adjust their websites to fit around every browser&#8217;s bugs. <em>But</em> that
  doesn&#8217;t mean it&#8217;s acceptable to reject your users with a message like
  &#8220;The Internet browser you are using is not supported by online banking.
  Use the link below to see the complete list of browsers we&nbsp;support.&#8221;</p>
  
  <p>Firstly, the browsers I use <em>are</em> listed as being supported on your
  list <a href="http://www.natwest.com/personal/day-to-day/online-banking/g1/faqs.ashx">[1]</a>:</p>
  
  <ul>
  <li>On this laptop, I use a Firefox 3.0 beta. Firefox 3.0 is listed is
  being supported, and it works (if I tweak it to identify it as
  Firefox 2.0, then I can use the site just&nbsp;fine).</li>
  <li>On my desktops, I use Iceweasel 2.x. Iceweasel is Firefox with a
  different name, to get around trademark issues. Ask your
  Linux-techies, they should know about it. Again, it works as&nbsp;expected.</li>
  </ul>
  
  <p>Secondly, <a href="http://www.natwest.com/personal/day-to-day/online-banking/g1/faqs.ashx">[1]</a> states: &#8220;Netscape, Mozilla and Firefox users with other
  operating systems such as Linux may also be able to access the
  service.&#8221; How are we supposed to access the service if you deny us&nbsp;access?</p>
  
  <p>More generally, locking out unknown browsers goes completely against
  your policy of Accessibility <a href="http://www.natwest.com/popup/global/access.ashx">[2]</a>. While the <span class="caps">WAI</span> <a href="http://www.w3.org/TR/WAI-WEBCONTENT">[3]</a> doesn&#8217;t
  specifically recommend against turning away unknown browsers, I think
  you&#8217;ll find that&#8217;s because the authors didn&#8217;t even <em>dream</em> of
  <em>considering</em> such a thing. The <em>entire point</em> of <span class="caps">WAI</span>, is to make your
  site as portable as possible, and to work for everyone with a far
  wider variety of user agents than you could ever test&nbsp;with.</p>
  
  <p>I don&#8217;t know how you can call yourself <span class="caps">WAI</span>-compliant and reject
  un-&#8220;certified&#8221; browsers. Your webmasters should hang their heads in&nbsp;shame.</p>
  
  <p>Now, I don&#8217;t intend to rant any more than that, because that&#8217;s the
  only problem I have with your site (and your service). Beyond this
  little niggle (which stops me being able to bank, without configuring
  my browser to lie) I&#8217;m very impressed with your&nbsp;services.</p>
  
  <p>Please sort this out, it&#8217;ll turn me back into a happy&nbsp;customer.</p>
  
  <p><span class="caps">SR</span></p>
  
  <p><span class="caps">PS</span>: I&#8217;d have sent this by e-mail, where I&#8217;d, but you don&#8217;t provide any
     e-mail contact details on your site.
  <span class="caps">PPS</span>: Only providing a small feedback form doesn&#8217;t help users give you
      real feedback, it just intimidates and irritates&nbsp;them.</p>
  
  <p>[1]: <a href="http://www.natwest.com/personal/day-to-day/online-banking/g1/faqs.ashx">http://www.natwest.com/personal/day-to-day/online-banking/g1/faqs.ashx</a><br />
  [2]: <a href="http://www.natwest.com/popup/global/access.ashx">http://www.natwest.com/popup/global/access.ashx</a><br />
  [3]: <a href="http://www.w3.org/TR/WAI-WEBCONTENT">http://www.w3.org/<span class="caps">TR</span>/<span class="caps">WAI</span>-<span class="caps">WEBCONTENT</span>/</a></p>
  
  <p>&#8212;<br />
  Stefano Rivera<br />
   http://rivera.za.net/<br />
   H: +27 21 794 7937   C: +27 72 419&nbsp;8559</p>
</blockquote>

<p>Now, that was rather harsh to them, but this has been irritating me for ages. Then, when I did decide to <em>do something</em> about it, I was rather worked up, and&nbsp;ranted.</p>

<p>I got a call back from NatWest this morning, and was basically told that they aren&#8217;t going to change anything. I can understand their position, but I don&#8217;t that they were seeing mine. (Oh, and I think they are&nbsp;wrong.)</p>

<p>The reasons I was given for this non-approved lockout&nbsp;are:</p>

<ol>
<li>Support. But of course, if your web site is decent, then you shouldn&#8217;t have any support issues. (<span class="caps">OK</span>, that&#8217;s rather utopic, but the kind of people who use alternative browsers will be <span class="caps">OK</span> in such&nbsp;situations).</li>
<li>Security. Apparently Opera caches previously visited pages as they were. Clicking back doesn&#8217;t revalidate with the server, and so someone who&#8217;s logged out of their Internet banking and gone on to google still has their private data visible in the history. Anyone coming up to their computer can go back to&nbsp;it.</li>
</ol>

<p>Now, I don&#8217;t think point 2 is NatWest&#8217;s problem. If Opera doesn&#8217;t support revalidation, then Opera must fix it. If Opera do, and NatWest doesn&#8217;t send the correct Pragma headers, then it&#8217;s NatWest&#8217;s&nbsp;problem.</p>

<p>But still, that doesn&#8217;t mean you lock-out untested browers, dammit. <em>Especially</em> if you call yourself&nbsp;<span class="caps">WAI</span>-compliant.</p>

<p>I&#8217;d love to see some feedback from a <span class="caps">WAI</span> board member on this type of issue. I don&#8217;t think the <span class="caps">WAI</span> specs address&nbsp;it.</p>

<p>Oh, and everyone, please stand up for your right to browse the web however you see fit. If more people did so, these kind of issues would crop up less&nbsp;often.</p>
    ]]></content>
  </entry>
  <entry>
    <title>A telecoms rant</title>
    <link rel="alternate" type="text/html" href="http://tumbleweed.org.za/2008/02/10/telecoms-rant" />
    <id>http://tumbleweed.org.za/2008/02/10/telecoms-rant</id>
    <published>2008-02-10T12:43:49+00:00</published>
    <updated>2008-02-10T12:43:49+00:00</updated>
    <author>
      <name>tumbleweed</name>
    </author>
    <category term="rant" />
    <category term="south-africa" />
    <category term="telecoms" />
    <category term="telkom" />
    <category term="vodacom" />
    <summary type="html"><![CDATA[<p>You&#8217;d think that telecoms (esp in South Africa, where being one is a license to print money) would do everything they could to get you to spend money with them?&nbsp;If&nbsp;only.</p>

<p>Cellphones (at least Vodacom) have always required you to manually enable International phone calls <span class="amp">&amp;</span> International roaming, by giving them a call and requesting it. This is a pain, to say the least. And you normally forget until you are already in&nbsp;another&nbsp;country.</p>

<p>But Telkom have taken this to a new level. I got a new phone line last month (which still doesn&#8217;t have working <span class="caps"><span class="caps">DSL</span></span>, grr!), and just noticed that I can&#8217;t make International calls on it. So I phone telkom. Amazingly I didn&#8217;t have to wait on hold at all (something never before experienced when calling the beast), and the lady I spoke to told me I have to &#8220;Visit a Telkom Shop with my <span class="caps"><span class="caps">ID</span></span>&#8221;. <span class="caps"><span class="caps">WTF</span></span>? How hard are they making it to spend money&nbsp;on&nbsp;them?</p>

<p>Is there any legitimate reason that international calls are blocked? With our pricing, it&#8217;s easy to knock up a multi-k-<span class="caps"><span class="caps">ZAR</span></span> bill without even thinking about dialling an international number, so they aren&#8217;t&nbsp;protecting&nbsp;anyone.</p>

<p>In related news, the reason you can&#8217;t have incoming connections on Vodacom 3G (even with &#8220;internetvpn&#8221;) is because then you&#8217;d be liable for the cost of any <span class="caps"><span class="caps">DOS</span></span> you received. Isn&#8217;t this a problem that hosting providers and ISPs already have to deal with? Why are mobile operators special? We need some Internet Neutrality and Telecoms sense in&nbsp;this&nbsp;country&#8230;</p>
    ]]></summary>
    <content type="html"><![CDATA[<p>You&#8217;d think that telecoms (esp in South Africa, where being one is a license to print money) would do everything they could to get you to spend money with them? If&nbsp;only.</p>

<p>Cellphones (at least Vodacom) have always required you to manually enable International phone calls <span class="amp">&amp;</span> International roaming, by giving them a call and requesting it. This is a pain, to say the least. And you normally forget until you are already in another&nbsp;country.</p>

<p>But Telkom have taken this to a new level. I got a new phone line last month (which still doesn&#8217;t have working <span class="caps">DSL</span>, grr!), and just noticed that I can&#8217;t make International calls on it. So I phone telkom. Amazingly I didn&#8217;t have to wait on hold at all (something never before experienced when calling the beast), and the lady I spoke to told me I have to &#8220;Visit a Telkom Shop with my <span class="caps">ID</span>&#8221;. <span class="caps">WTF</span>? How hard are they making it to spend money on&nbsp;them?</p>

<p>Is there any legitimate reason that international calls are blocked? With our pricing, it&#8217;s easy to knock up a multi-k-<span class="caps">ZAR</span> bill without even thinking about dialling an international number, so they aren&#8217;t protecting&nbsp;anyone.</p>

<p>In related news, the reason you can&#8217;t have incoming connections on Vodacom 3G (even with &#8220;internetvpn&#8221;) is because then you&#8217;d be liable for the cost of any <span class="caps">DOS</span> you received. Isn&#8217;t this a problem that hosting providers and ISPs already have to deal with? Why are mobile operators special? We need some Internet Neutrality and Telecoms sense in this&nbsp;country&#8230;</p>
    ]]></content>
  </entry>
</feed>
