- ‘should be cheaper than free’ – “I’m angry at the customers who send me nasty emails or reviews, threatening me with ‘telling Apple to remove it’ or rating it 1 star with a ’should be cheaper than free’ remark because after paying the ridiculously exorbitant 99c, they found it didn’t live up to expectations. "
- Hurdie Ho! – Maybe you had to be there and read the copy of Your Sinclair that this was originally published in, but this still makes me laugh.
- Museum looks at 2000-year history of the computer – The Computer History Museum was excellent even before this new exhibit. Recommended.
Tag: Iphone
A new version of my handy URL shortening app for iPhone and iPod touch has just hit Apple’s App Store. Please go and download it — it’s free!
I’ve added to the services that were supported in the previous version and now www.cut supports nine shortening services:
Also new in version 2.0 is a “URL Scheme.” This is a technical name for something that’s very useful. Picture the scene: you’re in Safari and you want to send the current URL to www.cut. Previously you had to copy the URL to the clipboard and manually launch it. Now, all you need to do is add “wwwcut:” to the beginning of the URL and www.cut launches automatically.
A few years ago I was very much “into” the whole open source movement. I read LWN (still do, actually). I bought a copy of The Cathedral and the Bazaar.
But one thing I never really did was contribute to open source projects. I never really had much need. They largely did what I wanted and when they didn’t, well, the modifications were too big to consider attempting in my spare time.
- Aerial views of New York – Neat pictures of Manhattan (and bits of New Jersey).
- Wallace and Gromit to appear on Christmas stamps – For once: Christmas stamps that I approve of.
- My First Week with the iPhone – I always assumed that a touch device like the iPhone would be pretty much useless for blind users. It’s good to be wrong.
- Protest The Pope – My images from todays “Protest the Pope” march and rally in London.
- Introducing: Yummy 2.5 – New version of Yummy, my iOS Delicious.com client, is now available on the App Store. Now includes iPad support, works better on iOS4 and has experimental pinboard.in support.
- Introducing iOS Beta Builder – Make distributing beta versions of iPhone software so much easier.
- Urbanized – After Helvetica and Objectified, Gary Hustwit’s next documentary is about the design of cities. “Urbanized looks at the issues and strategies behind urban design, featuring some of the world’s foremost architects, planners, policymakers, builders, and thinkers.” Can’t wait.
- 8-Bit Cities – This is awesome: maps of cities in the style of 1980’s video games.
- iPhone 4 – Case Program – I’ve not had any reception problems with mine but I’m not one to pass up free stuff…
##
The story so far
Last year Yahoo! announced, with no notice, a significant change that had far reaching consequences for all third party applications including my iPhone program, Yummy. This is the third in a series of posts that discusses how I dealt with it.
We’ve already talked about most of the work, starting with an overview, the announcement, the low level technical challenges and the implementation (technical and UI). All that remains it to launch it, and that’s what we’re going to talk about today.
##
The story so far
Last year Yahoo! announced, with no notice, a significant change that had far reaching consequences for all third party applications including my iPhone program, Yummy. This is the third in a series of posts that discusses how I dealt with it.
On Monday I gave an overview of the problem, Tuesday I looked at how those changes were announced and why they were tricky, and yesterday I looked at how I actually implemented those technical details.
##
The story so far
Last year Yahoo! announced, with no notice, a significant change that had far reaching consequences for all third party applications including my iPhone program, Yummy. This is the third in a series of posts that discusses how I dealt with it.
On Monday I gave an overview of the problem and yesterday I looked at how those changes were announced and why they were tricky. Today we’ll look at how I actually implemented those technical details — though not at the code level so don’t worry if you’re not a programmer!