Unintended Consequences, Thanks To Delicious

The ripples from my recent stolen Mac episode continuing to spread. I changed a number of passwords, including to Typepad, just in case. And it was only today, when I noticed that Delicious didn’t seem to be posting my bookmarks to Typepad, that I remembered that I had to update the password in the Delicious settings. Of course, Delicious didn’t alert me to the fact that posts were failing, either.

I know it’s my fault, but it’s just dumb not to alert the user. Whoever is managing Delicious these days should note this down. Having a message like the following buried deep in the bowels of Delicious is not enough:

[11/27/08 09:00:03 AM -0800] Creating blog post at http://www.typepad.com/t/api …ERROR: Failed due to General Exception: Curl returned non-null errno 52:Empty reply from server

And, oh, by the way: when I enter the new password, that would be a good time to verify if it works, not in the middle of the night 12 hours later.