<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>PHP, iPad, and iPhone Developer - Ben Dodson &#187; Uncategorized</title>
	<atom:link href="http://bendodson.com/category/uncategorized/feed/" rel="self" type="application/rss+xml" />
	<link>http://bendodson.com</link>
	<description>The blog and portfolio of an Apple iPhone Developer</description>
	<lastBuildDate>Sat, 05 Dec 2009 20:00:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>London Underground Tube Updates API is live!</title>
		<link>http://bendodson.com/2009/04/26/london-underground-tube-updates-api-is-live/</link>
		<comments>http://bendodson.com/2009/04/26/london-underground-tube-updates-api-is-live/#comments</comments>
		<pubDate>Sun, 26 Apr 2009 21:48:47 +0000</pubDate>
		<dc:creator>Ben Dodson</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[json]]></category>
		<category><![CDATA[london underground]]></category>
		<category><![CDATA[rewiredstate]]></category>
		<category><![CDATA[rss]]></category>
		<category><![CDATA[tfl]]></category>
		<category><![CDATA[tube]]></category>
		<category><![CDATA[Tube Updates]]></category>
		<category><![CDATA[xml]]></category>

		<guid isPermaLink="false">http://bendodson.com/blog/?p=55</guid>
		<description><![CDATA[For all of you who emailed me about the London Underground XML file I made, you'll be happy to know that my new Tube Updates API is now live and ready to be used by your applications.]]></description>
			<content:encoded><![CDATA[<p>I <a href="http://bendodson.com/blog/2008/03/16/rss-feed-of-the-london-underground-tube-status/">posted an article</a> just over a year ago about an RSS feed of the London Underground Tube Status that I&#8217;d created by scraping the <a href="http://www.tfl.gov.uk/">TFL website</a>.  I was overwhelmed not only by the response via comments and emails, but also by the sheer number of people using it (my apache access logs increased by 7GB per month!) that I decided to make a full blown API so that it would be easier for developers like me to create great mashups using data that should always have been publicly accessible.</p>
<p>I&#8217;m happy to announce that after a good test run at the <a href="http://rewiredstate.org/">Rewired State</a> event a couple of weeks ago, the Tube Updates API is now live and ready to be used at <a href="http://tubeupdates.com/" title="An API for TFL London Underground Tube Update data">tubeupdates.com/</a> &#8211; You can request updates from any line (including the Docklands Light Railway) in either JSON or XML format and everything is structured to give you as much information as possible e.g. station closures, why there are &#8216;minor delays&#8217;, etc.</p>
<p>But that&#8217;s not all!  I am caching the data (and have been since 1st Jan 2009) so you can also go back in time and look at the underground system at any point in time!  I wrote a rather rudimentary <a href="http://tubeupdates.com/stats/">stats analyser</a> for my <a href="http://rewiredstate.org/projects/tfl-statistics">Rewired State project</a> which shows you the basic reliability over the past couple of months but that is just a taster of what you can do with the information now available.</p>
<p>I&#8217;ll be releasing new versions of the RSS feed shortly so that non-developer types can still access the data &#8211; I&#8217;ll be announcing those <a href="http://bendodson.com/blog/">on this blog</a> and on <a href="http://twitter.com/bendodson/">my twitter feed</a> once they are ready in the next few days.  In the mean time, please play around with the API.  There are no real usage terms but I&#8217;d love to know how you are using it so please <a href="http://bendodson.com/contact/">get in touch</a> if you make use of it!</p>
<p><em>For those that come to this site regularly, you may have noticed that it&#8217;s undergone a major overhaul!  I&#8217;ve done a complete redesign (looks best in Safari) and replaced the blog engine with Wordpress so I should be blogging a lot more frequently.  I&#8217;m also about to become a full time freelance PHP developer and web consultant but I&#8217;ll be posting more details about that soon!!</em></p>
]]></content:encoded>
			<wfw:commentRss>http://bendodson.com/2009/04/26/london-underground-tube-updates-api-is-live/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Twitter stops sending SMS to UK / Europe / Australia</title>
		<link>http://bendodson.com/2008/08/17/twitter-stops-sending-sms-to-uk-europe-australia/</link>
		<comments>http://bendodson.com/2008/08/17/twitter-stops-sending-sms-to-uk-europe-australia/#comments</comments>
		<pubDate>Sun, 17 Aug 2008 15:33:52 +0000</pubDate>
		<dc:creator>Ben Dodson</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[iPhone]]></category>
		<category><![CDATA[sms]]></category>
		<category><![CDATA[tweetsms]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[twitteriffic]]></category>

		<guid isPermaLink="false">http://bendodson.com/blog/?p=40</guid>
		<description><![CDATA[After over a year and a half of free sms 'tweets', Twitter has stopped sending updates to mobile phones in the UK, Europe, and Australia.  Will this kill Twitter or does it still have its uses?]]></description>
			<content:encoded><![CDATA[<p>Undoubtedly the biggest web app of 2007 was <a href="http://twitter.com/" rel="external">Twitter</a>, the simple web app that allowed you to send a text message and have that sent for free to anyone that followed you.  Combined with a simple API, useful web apps could be created to send you txts when your train was going to be delayed or when you got a new email, etc.  However, this has all stopped in the UK, Europe, and Australia for the time being as Twitter has finally turned off the ability to send messages (although you can still update your status by sending a txt).  The full details are below in an email that was received by those registered with the service in affected areas and also on the <a href="http://blog.twitter.com/2008/08/changes-for-some-sms-usersgood-and-bad.html" rel="external">twitter blog</a>:</p>
<p><span id="more-40"></span><br />
<blockquote>
<p>Hi,</p>
<p>I&#8217;m sending you this note because you registered a mobile device to work with Twitter over our UK number. I wanted to let you know that we are making some changes to the way SMS works on Twitter. There is some good news and some bad news.
<p>I&#8217;ll start with the bad news. Beginning today, Twitter is no longer delivering outbound SMS over our UK number. If you enjoy receiving updates from Twitter via +44 762 480 1423, we are recommending that you explore some suggested alternatives.</p>
<p>Note: You will still be able to UPDATE over our UK number.</p>
<p>Before I go into more detail, here&#8217;s a bit of good news: Twitter will be introducing several new, local SMS numbers in countries throughout Europe in the coming weeks and months. These new numbers will make Twittering more accessible for you if you&#8217;ve been using SMS to send long-distance updates from outside the UK.</p>
<p>Why are we making these changes?</p>
<p>Mobile operators in most of the world charge users to send updates. When you send one message to Twitter and we send it to ten followers, you aren&#8217;t charged ten times&#8211;that&#8217;s because we&#8217;ve been footing the bill. When we launched our free SMS service to the world, we set the clock ticking. As the service grew in popularity, so too would the price.</p>
<p>Our challenge during this window of time was to establish relationships with mobile operators around the world such that our SMS services could become sustainable from a cost perspective.</p>
<p>We achieved this goal in Canada, India, and the United States. We can provide full incoming and outgoing SMS service without passing along operator fees in these countries.</p>
<p>We took a risk hoping to bring more nations onboard and more mobile operators around to our way of thinking but we&#8217;ve arrived at a point where the responsible thing to do is slow our costs and take a different approach. Since you probably don&#8217;t live in Canada, India, or the US, we recommend receiving your Twitter<br />
updates via one of the following methods.</p>
<p><a href="http://m.twitter.com" rel="external">m.twitter.com</a> works on browser-enabled phones<br />
<a href="http://m.slandr.net" rel="external">m.slandr.net</a> works on browser-enabled phones<br />
<a href="http://twittermail.com" rel="external">TwitterMail.com</a> works on email-enabled phones<br />
<a href="http://bit.ly/12bw4R" rel="external">Cellity [http://bit.ly/12bw4R]</a> works on java-enabled phones<br />
<a href="http://bit.ly/MFAfJ" rel="external">TwitterBerry [http://bit.ly/MFAfJ]</a> works on BlackBerry phones<br />
<a href="http://bit.ly/1WxjwQ" rel="external">Twitterific [http://bit.ly/1WxjwQ]</a> works on iPhones</p>
<p>Twitter SMS by The Numbers</p>
<p>It pains us to take this measure. However, we need to avoid placing undue burden on our company and our service. Even with a limit of 250 messages received per week, it could cost Twitter about $1,000 per user, per year to send SMS outside of Canada, India, or the US. It makes more sense for us to establish fair billing arrangements with mobile operators than it does to pass these high fees on to our users.</p>
<p>Twitter will continue to negotiate with mobile operators in Europe, Asia, China, and The Americas to forge relationships that benefit all our users. Our goal is to provide full, two-way service with Twitter via SMS to every nation in a way that is sustainable from a cost perspective. Talks with mobile companies around the world continue. In the meantime, more local numbers for updating via SMS are on the way. We&#8217;ll keep you posted.</p>
<p>Thank you for your attention,<br />
Biz Stone, Co-founder<br />
Twitter, Inc.<br />
<a href="http://twitter.com/biz" rel="external">http://twitter.com/biz</a></p>
</blockquote>
<p>Now this has upset a LOT of users (especially in Australia) but is the general outcry from the web community really justified?  As Twitter themselves say, it could cost them nearly $1000 per user per year to send txts and with 2.2 million users that ain&#8217;t cheap.  It has always been a mystery to me as to how Twitter makes money and how they are able to send all these txts for free so it comes as no surprise that they have finally stopped doing it.</p>
<p>But what about the alternatives?  I&#8217;m using a mac and an iPhone so I&#8217;ve gone for the obvious choice of <a href="http://iconfactory.com/software/twitterrific" rel="external">Twitteriffic</a> on both which does a pretty good job.  On my mac, I get a little chirpy noise and a popup when I get a tweet which works a lot better than an SMS in a lot of ways and this is similar on the iPhone.  The only downside is that the iPhone doesn&#8217;t support 3rd party apps running in the background so at present you have to open the app to see if there are any updates which is a bit of a pain.  However, this is due to change with iPhone Firmware 2.1 which is hopefully going to be with us some time in September.</p>
<p>Once the ability to receive twitters from Twitteriffic seamlessly occurs, I think it will prove a lot more successful than the txt message route.  Firstly, because it will cost nothing to reply (whereas previously it was very easy to reply to a twitter from a txt and thus get charged for it) and secondly because new features can be added to the service.  Twitteriffic already supports location awareness on the iPhone so people can see where I am twittering from &#8211; a small improvement but an improvement none the less.</p>
<p>In response to everybody shouting at Twitter about this issue, why don&#8217;t they instead complain about the mobile phone companies who are so greedy in the affected countries that they refuse to do a deal with Twitter?  It comes as no surprise to me that in the UK the cellular networks refused to budge on pricing but that is no fault of Twitter who have been paying so much over the last year and a half to make a great service at absolutely no cost to the end user (not even adding advertising to tweets which would seem an obvious money making route).</p>
<p>So in answer to <em>&#8220;is Twitter now dead&#8221;</em> I would say no!  There are still several uses for it (e.g. I use it to keep a <a href="http://bendodson.com">micro blog on my homepage</a>) and with several applications for all types of phones it is still easy to stay updated.  It will become really useful for me however when Apple release the next iPhone update with push technology &#8211; then it will be as if nothing had even changed.</p>
<p><strong>Update:</strong> Amusingly it looks like someone is already trying to cash in on the lack of SMS from Twitter around most of the world.  Apparently <a href="http://www.tweetSMS.com/" rel="external">tweetSMS</a> will &#8220;send you individual, hourly or daily updates from all (or just some) of your friends&#8221; for a &#8220;very small fee&#8221;.  We&#8217;ll see how small that fee is when they launch I suppose&hellip;</p>
]]></content:encoded>
			<wfw:commentRss>http://bendodson.com/2008/08/17/twitter-stops-sending-sms-to-uk-europe-australia/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
		<item>
		<title>Kampyle &#8211; An easy way to get web user feedback</title>
		<link>http://bendodson.com/2008/08/04/kampyle-an-easy-way-to-get-web-user-feedback/</link>
		<comments>http://bendodson.com/2008/08/04/kampyle-an-easy-way-to-get-web-user-feedback/#comments</comments>
		<pubDate>Mon, 04 Aug 2008 15:32:15 +0000</pubDate>
		<dc:creator>Ben Dodson</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Firefox Extensions]]></category>
		<category><![CDATA[google analytics]]></category>
		<category><![CDATA[grease monkey]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[kampyle]]></category>
		<category><![CDATA[Site]]></category>

		<guid isPermaLink="false">http://bendodson.com/blog/?p=38</guid>
		<description><![CDATA[You may have noticed the "Leave Feedback" icon in the bottom right corner of this site?  That is due to Kampyle, an easy way to get feedback and bug reports from the users of your website that has recently announced integration with Google Analytics.]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.kampyle.com/" rel="external">Kampyle</a> is an easy to set-up javascript widget that gives users the opportunity to comment on your site either for the purposes of a bug report or simply to say &#8220;you have a nice site&#8221;.  On clicking the feedback icon, a new window opens that gives the user various different options on how to comment on the site.  The default options are Bug, Site Content, Suggestion, Compliment, and Other. Each of these has several sub-options such as &#8220;browser issues&#8221; or &#8220;feature request&#8221; which are all completely customisable by the website owner.  The user can then fill in a bit of text to describe the problem or suggestion, etc, and can choose from 5 different emoticons to say how they feel about the website in general.  All of this information is then logged in your account at the Kampyle website for you to look over at your leisure &#8211; they can also email daily reports to you so that you can stay on top of all your adoring fans or pissed off IE6 users.</p>
<p><span id="more-38"></span>
<p>I&#8217;ve installed Kampyle on my site (using a custom icon as their default choices are pretty bad &#8211; animated gif anyone?) and I&#8217;ve already had quite a few pieces of feedback.  The great thing is that I&#8217;ve been able to fix a few bugs people have alerted me to and then have Kampyle email them back to let them know that the issue has been resolved.</p>
<p>Kampyle is pretty good as it is, but the thing that is putting Kampyle on the map is their recent <a href="http://www.kampyle.com/blog/?p=53" rel="external">integration with Google Analytics</a> which means you can see all of your feedback stats within your Google Analytics account.  The way they have done this is particularly clever &#8211; You need to download the <a href="https://addons.mozilla.org/en-US/firefox/addon/748" rel="external">Grease Monkey Firefox Extension</a> and install the <a href="https://www.kampyle.com/zlib_off/kampyle.user.js" rel="external">Kampyle Grease Monkey script</a>, but then when you go to your Google Analytics account you&#8217;ll see the Kampyle stats showing up in their own dashboard widgets.  Pretty clever really.  This was a major incentive for me as it means I can now see all of my stats in one place rather than having multiple accounts across the internet.</p>
<p>So, if you&#8217;d like to leave any feedback on the site just click on the &#8220;Leave Feedback&#8221; banner in the bottom right hand corner!</p>
]]></content:encoded>
			<wfw:commentRss>http://bendodson.com/2008/08/04/kampyle-an-easy-way-to-get-web-user-feedback/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Does anybody really use RSS Feeds?</title>
		<link>http://bendodson.com/2008/07/21/does-anybody-really-use-rss-feeds/</link>
		<comments>http://bendodson.com/2008/07/21/does-anybody-really-use-rss-feeds/#comments</comments>
		<pubDate>Mon, 21 Jul 2008 15:28:46 +0000</pubDate>
		<dc:creator>Ben Dodson</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[rss]]></category>
		<category><![CDATA[Site]]></category>
		<category><![CDATA[syndication]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://bendodson.com/blog/?p=34</guid>
		<description><![CDATA[I was having a chat with a web developer today who refuses to use RSS feeds and prefers to be emailed when a site gets updated - is this a global thing or is this guy just behind the times?]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been using RSS feeds for several years now and find them incredibly useful for keeping up to date with blogs and news sites.  However, today I was talking to another web developer who said that he hates RSS feeds and would much rather have email updates when a site gets updated rather than having to add an RSS feed to his email client.</p>
<p><span id="more-34"></span>
<p>Now I wouldn&#8217;t find this strange coming from a lot of people as I can understand that a lot of people have no idea about RSS and would get confused trying to work out what an aggregator is.  But from a web developer?  Come on!  If the people that develop websites with RSS can&#8217;t even be bothered to use it then what chance is there of the general populous using it?</p>
<p>I use mac mail to manage all of my RSS feeds and find that it does a fairly good job &#8211; everything gets synced over to my iPhone as well so I can keep up to date when I&#8217;m on the train etc.  I also have a few RSS feeds on my <a href="http://www.google.com/ig" rel="external">iGoogle homepage</a> so I can see the latest <a href="http://xkcd.com/" rel="external">xkcd</a> or <a href="http://www.dilbert.com/" rel="external">dilbert</a> strip whilst I&#8217;m pretending to work.  Now I&#8217;m fairly sure you can set Outlook up to receive RSS feeds &#8211; so why doesn&#8217;t this developer do that?  Apparently, if Windows were to crash (unlikely but stay with me on this) then he would lose all of the RSS feeds he was tracking and therefore have to add them again so it&#8217;s not worth doing.  &#8220;You could use <a href="http://www.google.com/help/reader/tour.html" rel="external">Google Reader</a> or any other number of online aggregators&#8221; say I.  &#8220;Too much effort&#8221; says he.  I give up.</p>
<p>So, in the next day or so there will be a &#8220;sign up&#8221; button on this site so that those of you who can&#8217;t be bothered with RSS can get email alerts when a new message is posted.  I&#8217;ve also set up a twitter account which will be syndicating the posts on this site as and when they happen &#8211; the account to follow is <a href="http://twitter.com/bendodson_com/" title="Stay up to date with bendodson.com on Twitter" rel="external">bendodson_com</a>.  Oh, and for those of you that have moved into the 21st century, here is the <a href="http://bendodson.com/rss.xml" rel="external">good old RSS feed</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://bendodson.com/2008/07/21/does-anybody-really-use-rss-feeds/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>phpMyOpenID Beta Testers Required!</title>
		<link>http://bendodson.com/2008/02/25/phpmyopenid-beta-testers-required/</link>
		<comments>http://bendodson.com/2008/02/25/phpmyopenid-beta-testers-required/#comments</comments>
		<pubDate>Mon, 25 Feb 2008 14:59:25 +0000</pubDate>
		<dc:creator>Ben Dodson</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[beta]]></category>
		<category><![CDATA[openid]]></category>
		<category><![CDATA[phpmyopenid]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://bendodson.com/blog/?p=13</guid>
		<description><![CDATA[I&#8217;ve finally got around to adding full multi-user support for my phpMyOpenID script and I&#8217;m now looking for some beta testers to help find any bugs that are lurking around.
]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve finally got around to adding full multi-user support for my <a href="http://labs.bendodson.com/phpmyopenid/">phpMyOpenID</a> script and I&#8217;m now looking for some beta testers to help find any bugs that are lurking around.</p>
]]></content:encoded>
			<wfw:commentRss>http://bendodson.com/2008/02/25/phpmyopenid-beta-testers-required/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
