Technical Blog

Commentosphere – Importer and Userscript

Posted on

After much trouble and headaches with the speed of the Ning backend, the Commentosphere Delicious Importer is working! Numerous recent updates and optimizations to Ning seem to have greatly increased the speed of the backend, which was what was dragging down the original. I created a test app clone of Commentosphere and successfully imported 70 comments from some test data Johan sent me awhile back to make sure that it really was working this time.

There is also now a Greasemonkey userscript for posting to Commentosphere! Based off of Johan’s commentblogging userscript, it adds a link to all comment post pages on Blogger blogs that links to the Add a Comment form on Commentosphere, already filled in with the necessary information for your new comment. One thing I would like to add to the script is the ability to select parent comments from the comment page, instead of having to get that data manually if you want it. It is still recommended to run with both the userscript and the bookmarklet — for posting comments from non-Blogger blogs.

5 Responses

Gina Bianchini


I just wanted to drop you a quick comment and thank you for bearing with us while we’ve been improving performance. We’ll be continuing to optimize the speed in the coming weeks.

Your App is very cool and we’re lucky to have you using Ning!


Yay! Nice one, Stephen! It’s all looking particularly gorgeous and I can’t wait to see how this evolves.

I know you know this already, but just to reiterate for anyone else either building or wanting to build an app on Ning: If you need help with something, questions answered, or just want to ramble about your app idea with someone, feel free to give me a yell: yozg (at)

Johan Sundström

Nice! I would find it even nicer if I could keep the markup, allowing those of us who want it to keep it, and those who don’t to just not save that data in their tags in the first place (it’s really just about picking up .textContent instead of .innerHTML in the tagger script).

You could have the importer script close any truncated input with open tags, though, if you want to make a nice feature, or just leave that work to the user to do by hand before importing (as I would have expectet to).


The problem with the markup was that in importing the test data there were some unclosed tags (only there because of the fact that truncates the extended field) that were causing display problems — the entire content of a comment is not usually contained in a commentblogging post anyway, so I don’t feel it to be a great loss.

Leave a Response