Posted on November 8, 2012 by samjparker
We’re proud to announce a suite of enhancements to the new Disqus. Based on feedback from thousands of communities, these changes help Disqus comments natively adapt to a broader range of site designs, community management styles, and languages.
The new Disqus has always adapted visually to fit a range of site color schemes, automatically picking up on the background and link colors. Font style is a new appearance feature and comment text will switch to a serif font when appropriate. All appearance options are also now available as manual overrides in the admin settings, including a new feature to emphasise moderator comments with custom badge text. You can see we’re now using the “Disqus Team” badge here on our blog.
New font style, color scheme, and mod badge controls.
Today we’re rolling out a core change to the community rules: downvoting a comment is now reserved for users who are logged in. We’ve also reorganized the community rules in the site settings page, making it clearer how to configure whether guest users can comment on your site and whether to send certain types of comments to pre-moderation.
Downvoting is now for signed-in users only.
Disqus powers communities all around the globe. Full localization is now supported in the new Disqus for 7 languages: French, Spanish, German, Portuguese, Russian, Swedish, Turkish. See additional detail about Disqus localization and forthcoming language support.
That’s not all. We’ve enhanced other elements of the core comment interface—including a new hover state to show the absolute timestamp—and there’s more to come. See the release notes for the complete breakdown of recent changes.
Publishers using the new Disqus have experienced the results we built it to produce: more engagement, increased traffic and better discussion. Don’t have the new Disqus and want to try it out for yourself?
We’re always looking for feedback. Let us know what you’d like to see next in the comments below.
We welcome relevant, respectful comments. Please read our Community Guidelines.blog comments powered by Disqus