Delicious is still tasty to me

I can’t help feeling disappointed in how quickly folks jumped ship and stayed on the raft even when it became clear that it was just a leaky faucet and not a hole in the hull.

I’ve been seeing many of my friends and peers jump ship and move their social/online bookmarks to other services (both free and paid) since the Yahoo leak about Delicious being in the sun-setting category of products. Given the volume of outcry over this, I was pretty confident that either Yahoo would change their minds or someone would buy Delicious or someone would replicate Delicious. So, I didn’t worry. I didn’t freak out. I haven’t even made a backup of my bookmarks, although I plan to do that soon just because it’s good to have backups of data.

Now the word is that Delicious will be sold, which is probably for the best. Yahoo certainly didn’t do much with it after they acquired it some years ago. But, honestly, I’m pretty happy with the features Delicious has now, so really don’t care that it hasn’t changed much. However, I do want it to go to someone who will take care of it and continue to provide it to users, whether it remains free or becomes a paid service.

I looked at the other bookmark services out there, and in particular those recommended by Lifehacker. Frankly, I was unimpressed. I’m not going to pay for a service that isn’t as good as Delicious, and I’m not going to use a bookmarking service that isn’t integrated into my browser. I didn’t have much use for Delicious until the Firefox extension, and now it’s so easy to bookmark and tag things on the fly that I use it quite frequently as a universal capture tool for websites and gift/diy ideas.

The technorati are a fickle bunch. I get that. But I can’t help feeling disappointed in how quickly they jumped ship and stayed on the raft even when it became clear that it was just a leaky faucet and not a hole in the hull.

IL 2010: Failcamp

speakers: Krista Godfrey, Char Booth, & Jan Dawson (moderated by Amy Buckland)

Buckland: Librarians seem to like reinventing the wheel. We only share our successes and not our failures (so that others may avoid them).

Dawson

AskON is an online chat reference service created by Knowledge Ontario. They wanted to integrate VOIP into their chat service so that they could add in vocal cues to clarify/focus the reference interview. They first used LivePerson, but the click-to-chat call button didn’t work, so they looked into Skype. When they were looking at feedback, they found that the data gathering portion was incomplete (forgotten or misused). However, they were able to follow-up on the feedback and found that staff preferred the workflow of text to vocal chat. Also, often both staff and users didn’t have proper equipment for vocal chat.

Godfrey

Fell into SecondLife and it snowballed from there. This snowballing is often the source of some fails. She was offered a chance to be on a panel talking about SL and then also some free space within it. So, her library began to explore how they could use the space in SL.

At one point they had six librarians covering shifts in SL, but after a while, participation dropped due to increases in traditional reference services and busy schedules. Fewer and fewer students were already active users, and they weren’t likely to start using it for reference services. They still have the island and hope to do something with it someday, but have stopped trying to do reference services there.

Booth

Don’t focus so much on the cause of failure. Figure out your contingency plan, then implement it if necessary.

Her library created a kiosk with a live image of a librarian’s face. The idea was to create a virtual reference space, but no one used it that way. In the end, they found it was more of a humorous PR tool.

Fake it like you’re making it. You can have self-doubt, but don’t show it. Your success will be more likely.

Audience

Are there any library initiatives to record and share failures? Not yet, but Kendra Levine offered to start one.

Library wanted to have a subject guide as a wiki, but it failed. How do you deal with a failure that you really wanted to work?

How do you process the failure as a group? If something does fail, assess it. It’s easier to walk away and ignore it, but you can’t learn from that.

Sometimes failures can turn out to be wild successes, but not in the way it had been originally designed. Tweak with purpose. And stop trying to control the user – learn what they need and how they want it, and you’ll have more success.

You need to know what resources you have from admin. You can’t go in to fix something if you don’t have the tools you need to fix any problems.

css.php