I generally don't want to use this blog to vent my frustrations so let's think of this post as a form of constructive criticism directed towards web bookmarking services that aren't following through on providing the services they claim to provide and aren't responding to customer service requests.
This topic is important and relevant to library innovation because, in my limited experience working in libraries, I've encountered a real fixation on desktop-based applications that often keeps librarians from improving their services for patrons by utilizing web-based services. I'll come back to this topic again with some specific examples that, I believe, illustrate the point that the problem isn't with incompetence, the problem is with shifting one's whole mindset to a different way of thinking about providing information services.
And I'm not one to throw around terms like "paradigm shift" in a glib manner. There really is a big difference in these two ways of thinking.
That said, I started using Diigo for both personal and professional bookmarking because of my disappointments with Publish2 which I began using because of my disappointments with Delicious, most of which are the exact same disappointments!
Generally speaking, social bookmarking web services provide a way to store links to sites and online content as an alternative to simply using one's browser to save such links. Using such services frees the user from a specific desktop and/or browser, allowing access from virtually any web connected computer or mobile device with the option of making those links public and interacting with other folks using the service.
Though I keep my bookmarks private and take my social networking activities elsewhere, I love the concept, the options, the possibilities. In addition to bookmarking, each of the above mentioned services also supposedly allows one to publish links to one's blog or other public platform which can streamline the process of sharing such links. Usually one can choose between posting directly to one's blog or setting up an automatic posting schedule that will send the links to one's chosen spot on the web as a published post or ready-to-go draft post.
I first tried this out with Delicious. It made my life a lot easier because I do a variety of projects for which I'm gathering multiple links on a daily basis. That is, until it stopped working and they wouldn't say why and they wouldn't respond to customer service emails. Because they were early movers and innovators back before Yahoo bought them, the breakdown of services and lack of communication was discussed widely on the web. I think they tried to do something at some point but it was a big FAIL.
So I tried Publish2, which is championing what they call "link journalism", an attempt to turn what everybody on the web's been doing into a professional practice and that's all I'll say on that topic. In any case, I started using their post to blog option which eventually stopped working. Some of my links were disappearing as well. My attempts at receiving customer service was a big FAIL so I moved on.
To Diigo, which seemed to do everything perfectly for me both personally and professionally, yadda, yadda.
I was using their send to blog system quite a bit last year to explore different blog topics and also keep some blog sites going to which I wanted to return but didn't have time to spend otherwise maintaining them. I took a break to evaluate my whole operation towards the end of the year and recently decided to begin again with a focus on blogs such as this one where I'm regularly posting content but would love to add some link posts as well to expand my coverage a bit.
Guess what? Diigo's send to blog isn't working. I can't find info online about that problem. Their customer service isn't responding to requests left via their online form.
But guess what else? They're offering customer service via Twitter, which is kind of cool except that it forces one to use Twitter to get help thus serving only a small portion of web users. Plus, you can't really tell what problem they're addressing because the questions don't show up with the answers. You can link through to the account of the person asking the questions but you have to then browse to find the question and if the person asking is active on Twitter, that's kind of tough.
My feeling is, yeah, be cool but make sure you're handling basics well. Diigo is not handling basics well. And the arrogance of this approach to customer service makes Diigo less accessible to the folks that I want to help bring into the age of web-based services. This kind of approach to customer service is exactly the sort of thing that justifies the oppositional attitudes of folks who are a bit dubious about such services.
Diigo, thanks for the FAIL. You're now undermining not only my web publishing projects but my attempts to advocate for the use of web services by librarians. And aren't those the kind of folks you're supposed to be serving?
Looks like Diigo's ubercool approach is pushing them into the FAIL category along with Delicious and Publish2.
And that makes me very sad. As well as angry. But people are more sympathetic to sadness so let's focus on that, shall we?
Update:
Diigo Update: Finally Solved Problem Despite Lack of Customer Service
Recent Comments