DISQUS

Community Page on DISQUS

what is this?

DISQUS Blog

The official Disqus forum. This is the place to receive beta support and offer suggestions.
« Back
Author

Major concerns with data ownership & presentation

Started by Jake McKee · 4 months ago

Daniel, et. al.,

If I may be so bold, I'd like to offer an opinion about Disqus and the reason I don't (yet) recommend that my clients and friends should rush out to use the service.

Generally, I don't see that Disqus is being approached in the HIGHLY ENCOMPASSING manner it should be. You guys are creating a great set of features, but you've yet to dial in the "platform" nature of the project. The reason I say this is that there are FAR too many open issues with the general questions/issues related to:

* My ability as a service user to control the way MY content is presented on YOUR site (I very much DO NOT want ANY display of my blog entries other than on my site, including community pages)

* Clarity regarding the ownership of MY content when it's presented on your site. You don't have a ToS, and the only clarity around what rights I'm turning over (or not) are in one FAQ. Further, I may own my content, but you certainly do what you want with it, without any of my oversight or choices. (See above)

* As a semi-technical user, the export functions on Disqus are basically useless. I spent nearly 4 hours last weekend trying to simply import my Disqus comments back into my WordPress site as both an experiment and as backup. I was completely unsuccessful. This means that export is, for nearly all users, fundamentally broken.

* Using Disqus fundamentally hobbles my ability to interact with my users by sending them direct emails or gaining access to their IP addresses in order to "tag" them in a service like Woopra.

Many, many people shy away from services that turn over important tasks (be it blog comments or project management like Basecamp or corporate directories or whatever) where there's not a VERY clear path to reclaiming the data that is rightfully theirs and/or not being able to control completely the access to said data.

Before you add another new feature, I'd STRONGLY suggest taking a long look at the data exchange process, data lock-in (perceived or real or by default due to complexity), and content presentation & ownership issues.

Don't get me wrong - I don't dislike the service, far from it. I'm posting this message because I think you guys are close to a pretty bad ass platform and want to be able to recommend it to my friends, family, and more importantly, clients.

Truth is, based on the issues above I'm not (yet) able to recommend it. To be perfectly honest, I'm not recommending this to my clients because I fear having them come back upset at some point in the future because of those issues.

And if someone like me who loves (LOVES!) the idea of a global comments platform, has already installed it, and regularly submits bug tests and functionality requests as a way to improve the system won't recommend it, that says something significant about the ability of this to break out of the early adopter crowd and get into the mainstream, no?

Would love to hear your thoughts.

Jake
communityguy.comj

5 comments

  • Hey Jake, we're going through this right now. Just wanted to let you know that it's not being ignored. There's a lot of stuff to think about but I'll keep this thread updated.
  • Thanks Daniel! Thanks for the consideration :)
  • By the way, happy to talk via phone or IM if you'd prefer. I'm happy to help how I can. Let me know.
  • Jake,

    I appreciate the extended evaluation. Here are my thoughts.

    * The community pages play an integral role on Disqus. We are still seeing how people use them, while extending its purpose.

    * A formal TOS may do us good, thanks.

    * Export is available so data is not locked within our walls. I believe strongly in that. It's the user experience of migrating data that is lackluster, and believe me, we are working on this.

    * IP addresses are available in a variety of places if you are a moderator.

    The service is still early and I agree there is a lot of room for us to fully flesh it out. Thanks for being an active member of this community and helping us improve Disqus. If I'm mistaken about anything or you'd like to chat further, email me anytime at daniel@disqus.com
  • Daniel, thanks for the reply, just wanted to reply inline and say thanks for the offer of offline discussion. I think that'll make it faster and easier to discus these issues.

    I feel a bit like the answers you give are brushing off the bigger issues I'm raising, but hopefully we can clarify offline.

    Thanks again for the willingness to dive into this matter.

Add New Comment

Returning? Login