Saturday, July 05, 2008

iPhone mystery: will Apple allow developers to do desktop sync?

I've been watching this for months. Despite all the SDK talk, there's no mention of whether Apple will allow app developers to sync with desktop apps (rather than with net apps).

This is a big deal for products like OmniFocus. Omni acts as though a solution is coming, but a week from go-live Mariner software doesn't know how this will work ...
Your Tech Weblog: Local firm making a spreadsheet for iPhone 
... He also needs [Mariner] Calc for iPhone to sync with Calc for the Mac, and is talking with Apple on how that might happen, but he has no idea when this critical hurdle will be overcome....
I assume that Apple wants very tight DRM and security for the iPhone, and that this has created their synchronization issues.

I wish Android were doing better. It would be nice for Apple to feel more competitive heat. As it is, they look ready to rule. For better and for worse! 

Precipitate: unify your online and local memories (files)

A few hours ago I wrote about my memory management meme. Things are moving even faster than I'd thought [1], because somebody at Google went and coded Precipitate:
Official Google Mac Blog: Precipitate: search your local and online docs 
... you're like me, some of your information is in the cloud and some is on your machine, and you don't always remember what is where. That can make it frustrating when you try to use your favorite local search tool to find something. Isn't the whole point of search that you don't have to remember where you put things?
That's where Precipitate comes in. After you install Precipitate, you can use Google Desktop or Spotlight to find files online (such as those in your Google Docs list) just as you would find files stored on your Mac...
Yep, that's what I need -- a tool to help unify my distributed memory. Precipitate currently supports only Google Docs and bookmarks. When they integrate Google Custom Search (as in my blogs) I'll try it out.
[1] joke.

My new number one Blogger request: fix backlinks with whitelisted URLs

I used the think that my #1 and #2 Blogger priorities were enhancing the BlogThis! bookmarklet and full support for Safari.

That was yesterday.

Today I thought differently about what my blogs are for, and where they are leading.

I've created a new category called "memory management" that will expand this idea, both here and in Gordon's Notes. More on that as I get to it, but it has nothing to do with "Quarterdeck Extended Memory Manager" (geeks of a certain age just had chest pains).

"Memory management" involves personal memory management and corporate memory management, private memory management and (this is new) public memory management, and an early (ok, so I was re-reading Idoru this am) version of gordon-google mind-fusion (one decaying, one growing).

Enough parens there?

Which brings me to my new #1 Blogger request.

Fix the backlinks.

First:
What are backlinks and how do I use them?

.... Backlinks enable you to keep track of other pages on the web that link to your posts. For instance, suppose Alice writes a blog entry that Bob finds interesting. Bob then goes to his own blog and writes a post of his own about it, linking back to Alice's original post. Now Alice's post will automatically show that Bob has linked to it, and it will provide a short snippet of his text and a link to his post. What it all works out to is a way of expanding the comment feature such that related discussions on other sites can be included along with the regular comments on a post....
Except backlinks very rarely appear on my blogs, and they NEVER include backlinks between posts on my domain.

Now you might think this is because Google never indexes my blogs -- which is how they claim to create the backlinks, but, honestly, Google is astoundingly quick to index all my blogs considering their negligible readership.

What I think happened is that the original purpose of backlinks collapsed due to fraud, webspam attacks, and search engine optimization. Google has given up on them for all but very high end blogs, and one of their defenses has been to block backlinks within blog domains (to reduce search engine optimization and link farm fraud).

Ok, that's fine, but backlinks are an aspect of what we used to call "backward chaining" in inferencing systems. In people-speak they allow one to explore semantic connections (insert obligatory semantic network, xanadu, memex, etc reference) to antecedent or precedent posts.

This capability is a strategic component of my personal memory management obsession.

So I want Blogger to create a new sort of backlink -- to posts that are within domains that I specify. I would create a set of whitelisted urls for my blogger account, and links from those urls to a specific posts would always become backlinks. I could remove them if I wished of course. To avoid linkfarm abuse Google would exclude this type of backlink from their value estimation algorithms.

This, then, is my new number one Blogger request: Create backlinks based on whitelisted URLs.

PS. As of first posting a search on "URL backlink whitelist" returns no meaningful hits. I wonder when that will change...

Update: 7 hours after the initial post the "URL backlink whitelist" search returns two meaningful hits -- this post and my secondary Gordon's Notes post. Actually it probably happened much faster than that, my embedded search had a typo in it. This sort of thing is really astounding, even though we increasingly take it for granted.

Blogger a mess with Firefox 3

I'm rewriting this post.

Every other post I've written over the past 3-5 days has had problems with lost line breaks. All my text runs together. It's as though Blogger had broken their age-old management of paragraph breaks. I've tried Safari 3, Firefox 3, ScribeFire, XP, OSX, Blogger-standard and Blogger-in-Draft.

My original post implied the problem was with ScribeFire, Blogger in Draft, and Firefox 3. Then I thought it was Firefox 3 and any version of Blogger. Now I think it's any version of Blogger with Firefox 3 and Blogger-in-Draft with Safari 3.

Basically Blogger is having a really lousy holiday weekend.

Be warned.

They'll fix this eventually. It's not hard to spot!

Friday, July 04, 2008

How to know it's time to stop reading a blog

"Mobile Opportunity" has been an occasionally fun read for a veteran of the Palm wars, but every so often it says something like this:
Mobile Opportunity: Symbian changes everything, and nothing

...Here's the weird thought for the day: Microsoft is the last major company charging money for a mobile operating system...
You might think he was excluding the iPhone OS because it's derived from a desktop OS, or you might think he excluded OS X because it's bound to hardware, but I've been reading MO for a bit. He really has no interest in the iPhone as a mobile platform.

That's just too odd.

On the other hand his link to the Register's Psion retrospective is party redeeming. The story reminds me of the sad tale of PenPoint -- I keep that book next to my OS/2 architecture book.

Dan's data reviews IDrive online backup, and mentions Mozy too

I suspect the "paid review" model will eventually produce the same results as PC Magazine of old, but it will take a while to corrupt Dan's Data. A recent review is very thorough and appropriately technical:
Review: IDrive online backup service

... The reason why I find IDrive particularly interesting, though, is that they're paying me via ReviewMe.com to write this review.

ReviewMe isn't one of those scummy services that allow payment to be conditional upon a favourable review, though. Whether I say IDrive is humankind's finest creation, or that it took both of my legs off at the knee, I get paid the same....
Dan's review of IDrive is pretty positive, though he only does XP stuff.

I've been looking for a good online backup solution for a while, to supplement my current Retrospect Pro USB disk solution. Apple's MobileMe might produce something, but it will be costly. I've about given up on Google -- they could deliver a service next week or next century.

DD says both IDrive and Mozy support XP and OS X. IDrive is setup for multiple accounts sharing the same space, that would work for me.

Incidentally, the primary reason to have offsite backup in Saint Paul MN is not fire, flood and quake, it's theft. True, smart thieves won't bother to steal hard drives, but most thieves are stone stupid. Elsewhere, fire and flood are right up there.

I wouldn't use these services as my primary backup solution, but as a supplementary solution they do interest me.

Update 4/11/09: Great comment below. At least some services (iDrive) don't back up OS X shortcuts/favorites -- which breaks some app data stores including some iPhoto and Aperture configurations. It's a good reminder to check how well security attributes are managed.

Blogger gets some real updates and Google moves away from Data Lock

There's still no update to the extremely antiquated BlogThis! blogger bookmarklet, but Google is, at long, long last, putting some energy into Blogger.

To see the new environment you need to be using FF 3 or Safari 3 (some versions of IE too) and running Blogger in draft. Today Safari 3 is showing the old editor, so things will be fluid.

The current big news is that Safari 3 is supposed to have full support -- which means it's a more viable browser for my use. The big future feature is promised FTP file upload and enclosures. Uploaded images are stored only in Picasa web albums.

I've run into these bugs and lost capabilities so far:
  1. Items authored in the BlogThis! window are formatted incorrectly when edited in the new editor.
  2. Items authored using ScribeFire for FF are formatted incorrectly in the new editor and cannot be fixed easily. (SF has just been updated, so this may change.)
  3. Lists don't work fully. So if you save an item and try to add to a list, it inserts the row without a list tag. (known issue)
  4. The Save Now button closes the draft, so you have to reopen it (known issue)
  5. No formatting  buttons in HTML mode (they will return soon)
Some highlights on the editor:
  1. The new post editor: Dynamic image resize, drag and drop location. Changes to the HTML editor that seem of unclear value to me (solving a non-existent problem?). Full Safari 3 support? (But today 3.1.2 gave me the old editor, so they may be tweaking something).
  2. How to report HTML bugs with the new post editor: Add a comment to this blog post? Seems that won't scale.
There are also some very nice big new features, the backup and ability to effectively merge blogs seems awfully big to me (note that this particular page has links to pages that are "saved in draft" and thus don't appear as regular post pages -- a curious choice):
  1. Star ratings. Readers only, personally I'd like to be able to rate my own posts too -- differentiate the ones I think are more interesting.
  2. Import / export of blogs. Back up all of your posts and comments to one Atom XML file on your computer, and import your posts from one blog to another.
  3. Embedded comment form. By incredibly popular demand, we’ve brought the comment form to your blog’s post pages, with support for Google Account and OpenID authentication.
    New post editor. We’ve completely revised the post editor, bringing in drag-and-drop image placement and better HTML handling.
Safari 3 support in the new editor is great, but for me the really big deal is import/export. Per blogger:
  1. Merge two or more blogs into one. Take the exported posts and comments from one blog and import them into another one.
  2. Move individual posts from blog to blog. After importing, select just a set of posts to publish and publish them with one click.
  3. Back up your blog to your own storage. You can keep your words safe and under your control in case anything happens to your blog, or us, or if you want to remove them from the Internet.
  4. Move your blog somewhere else. Our export format is standard Atom XML. We hope to see other blogging providers extend their Atom support to include import and export. And, if you decide to come back to Blogger, importing your export file will get you back up and running in seconds.
The last is big. Google claimed over a year ago that they were going to make user data portable (see also). I've been very skeptical, and it's taken them a heck of a long time to do anything real. Now I'm willing to give them some time to show genuine commitment -- such as the ability to move Picasa albums to other services.

Altogether this is the best Blogger news since it became a somewhat reliable service about a year ago. Maybe Google can do product commitment after all.

Now if Google would only fix BlogThis!