Once, there was this great app called Tweetie by Atebits. It was a Twitter client for iPhone and iPod touch, and very good, and the (Twitter-loving iPhone-using) people rejoiced.

And then there was Tweetie for Mac OS X. It was a Twitter client and very good, and the (Twitter-loving Mac OS X-using) people rejoiced.

And then there was Tweetie 2. It was a Twitter client for iPhone and iPod touch, and very good, and the (Twitter-loving iPhone-using) people GOT TERRIBLY ANGRY.

The reason behind the vitriol? The dev had the audacity to charge three bucks for his updated, rewritten Tweetie for Apple handhelds. Three dollars, for an app that you’ll likely use daily! Shocking!

But it’s not like this is without precedent. Increasingly, consumer-level software provides no upgrade cycle. On the Mac, the likes of Bento, iLife, Photoshop Elements, iWork and many others provide no discount if you bought the previous version, which is largely countered by the value of the product.

Tweetie 2 is on the App Store, which provides no upgrade model anyway, and so the dev had no other choice other than ‘work for nothing and eat baked beans every night for dinner’, which would pretty much guarantee no Tweetie 3 and no further apps. So, here are some helpful tips if you’re a Tweetie 1 owner who’s feeling hard done by:

1. Carry on using Tweetie 1. Atebits didn’t include a ‘blow up iPhone if user doesn’t delete Tweetie 1 when Tweetie 2 comes out’ feature. Your app will continue to work, enabling you, ironically, to bitch about its follow-up on Twitter.
2. Save up your pennies for Tweetie 2. I know times are tight and the economy’s screwed, but let’s look at something for a second: you’re sitting there with an iPhone or an iPod touch, which cost quite a lot of money. If you really want that copy of Tweetie 2, which costs all of $2.99 or £1.79, I’m fairly sure you could save up your pennies. Don’t have that Starbucks coffee for one whole day, or make your own sandwich for work. As if by magic, you’ll have saved enough cash to buy Tweetie 2!
3. Stop bitching. No, really—it’s getting old, and you sound stupid.

Great article on TorrentFreak: Copyright Drama Prevents Artist From Sharing Music on MySpace. The short version is this:

• Edwyn Collins pens and has a hit with A Girl Like You.
• Collins retains copyright and the licensing deal expires.
• Collins tries uploading the track to MySpace.
• MySpace yells NO! and sends Collins to a chilling REEDUCATION page.
• Detective work unearths the fact Warner claims rights to the song that Warner doesn’t have.
• Warner lawyers told to resolve the issue.
• Warner can’t be arsed to resolve the issue.

The article also notes: “Several big shot labels are still selling Collins’ track today even though their license to do so expired several years ago. This basically means that the labels are pirating his music, and making profit from these activities.” And while lots of idiots helpfully suggest Collins should sue or shut his whinging mouth (or words to that effect), it’s worth noting that it’s hardly simple to sue a massive record label, nor even keep track of ‘cease and desist’ notices and subsequent lawsuits if a whole bunch of labels are ripping you off.

I wonder whether Peter Mandelson and his Labour chums will cut off the internet access of all the major labels’ UK offices—in the manner they’re planning for individuals (Times Online: Can Peter Mandelson cast the internet pirates adrift?)—for such flagrant rights violations?

TechRadar reports Adobe’s firing more shots at Apple regarding Flash on iPhone. The arguments, made via an irritating, patronising ‘skit’ suggest 1) Apple is really stupid because Flash doesn’t run on iPhone, and; 2) Adobe is really great, because it can get Flash to run on iPhone.

However, important points are missed:

• The Mac version of the Flash plug-in sucks balls. It’s the main source of Safari crashes on the Mac desktop, and the sandboxed plug-in still crashes regularly on Snow Leopard. The likelihood is, on the basis of the Mac version, the Flash plug-in could also suck balls on iPhone. Worse, with iPhone being relatively underpowered compared to desktop Macs, a Flash plug-in would wreck Safari’s stability and speed.
• Adobe’s mostly crowing about standalone Flash apps. There’s a whole world of difference between Flash apps on iPhone and Flash working within a browser that has its own overheads. (Note also that Flash apps don’t have access to OS X for iPhone UI components, and so many of them are a mess in terms of interface.)

I very much hope reporters don’t start moaning in unison that since Flash apps run on iPhone, so too should the plug-in—but I’ll bet they will. In the meantime, perhaps if Adobe rewrote its Mac Flash plug-in so it was even remotely comparable to the Windows one, Mac users and Apple itself wouldn’t be quite so hostile towards the technology.

On the 5th, Network World ran the article Three Reasons Why iPhone Won’t Get Adobe Flash. The reasons were: Apple doesn’t want Flash on the iPhone, the iPhone is created so it won’t support Flash (the article cites Apple not allowing plug-ins for mobile Safari), and Apple is betting on a different standard (HTML 5).

Funny that they missed out the most likely reason: Flash on the Mac—specifically the Flash plug-in—sucks.

On Leopard, the Flash plug-in is so unstable that Apple sandboxed browser plug-ins in Snow Leopard’s Safari. Interestingly, I’ve had one Safari crash since upgrading to Snow Leopard, compared to at least one per hour on Leopard. The Flash plug-in process, however, keels over with alarming regularity.

Also, put a PC next to a Mac and run some complex Flash content. Watch in horror as a knackered old PC outperforms a shiny new Mac—something that just doesn’t happen elsewhere.

Apple might be a huge control freak, but it’s proved plenty of times in the past that it will let other companies into its play-pen. However, said companies have to prove themselves worthy. I have no doubt that if the Flash plug-in was an amazing piece of Mac engineering, Apple would—at least now the App Store is hugely successful—allow Adobe to create the equivalent for iPhone and iPod touch. But since the Mac version of the plug-in is such a buggy, sluggish pile of garbage, why would Apple let the Flash plug-in anywhere near the mobile version of Safari, where it could at a stroke create the impression that Apple’s handheld platform and browser are slow, bug-ridden and unstable?

Cnet recently asked is the iPhone hurting AT&T’s brand? The reasoning? Network complaints and AT&T’s general incompetence means iPhone owners are getting terribly angry, and because iPhone is very newsworthy hardware, people report these problems with much gusto.

Quick answer, Cnet: no. The iPhone isn’t hurting AT&T’s brand. The only thing hurting AT&T is AT&T.

See also: O2 and iPhone in the UK. Again, some reports have suggested that ‘poor little O2’ has somehow been suckered into taking on iPhone and that those nasty iPhone users have somehow made the wonderful O2 look rubbish. O2 may have been taken by surprise with high data usage, but to blame Apple or its hardware for O2’s shortcomings is just stupid.

Man, sooner or later, people will look at something wonderful like BBC’s iPlayer and somehow suggest that the BBC is somehow at fault for making lots of shoddy ISPs look like the idiots that they are, due to not being able to cope with the traffic the fantastic iPlayer creates.

Oh, right—that’s already happened too.