January 26, 2009
PreSpotting On Twitter
If there’s any doubt that people are excited about the Pre, just check out the daily massive chatter about it on Twitter.
Here’s a sample (unchronologically) from just the past 24 hours:

And the winner:

Needed: Stanza Reader For Palm Pre
Everyone who is going to buy a Pre, sign up for Twitter and Follow @stanza_reader.
Then, every time you get a tweet from them, reply thusly:

I am determined to launch a campaign to get them to port the Stanza eBook reader to the Palm Pre as their next effort.
Why?
Stanza has been downloaded over one million times at the Apple App Store.
It’s the only eBook software for handhelds/smartphones that can read ePub eBooks. ePub is the eBook file format all of the book publishers have standardized on.
(In addition, Stanza — at least for iPhone — can do eReader eBooks too, but my campaign is for ePub capability. eReader would be an extra.)
Stanza is currently looking at other platforms to target:

But I think their wisest choice would be the Pre:
1) They’d likely be the first and only eBook reader at launch
2) Palm helped create a mass-market for eBooks
3) The Pre is likely to sell like crazy at launch (I’m more convinced with each day there will be shortages for weeks, if not months)
Why bother with Android or Blackberry? Android users will simply not approach Pre numbers (sorry, former PalmSource people!). And Blackberry users are already happy playing with all of their email. The Pre is ideal for Stanza.
If you’ve never heard of Stanza before now, check out: Demo Of Stanza eBook Reader For iPhone
Then join the campaign for Stanza For Pre!
The Pre And The Cloud And You #3

At the very least, some basic cross-posting services, tools, or desktop applications could move us towards a future where local data was replicated to numerous clouds with one simple action. Even a basic photo uploader tool that synced pictures to all the free online services would be much appreciated at this point. Or a document uploader that synced files between your computer, Live Mesh, Google Docs, Zoho, and others. That way, we could live in the best of both worlds with the confidence that our data was relatively safe…somewhere.
There are two issues here.
1) Standardized data structures. It should be easy to move our data out of one service to another. WordPress, for example, claims to give me an XML Export file. Well, I tried that file with a service that will take XML as input and format a printed book from it. The file was rejected. An email inquiry revealed WordPress is not actually doing 100% compliant XML.
2) Propagation of data. It’d be senseless, say, to have the Pre camera upload the same photo multiple times, for multiple services. I suspect this is where Sprint will step in with a propagation solution. The photo will be uploaded to a Sprint server service and propagated from that. One upload, automagic dispersion.
