The NodeBB Team is proud to announce the release of NodeBB v1.0.0!

This milestone has been a long time in coming, and the previous release, v0.9.3, had been out for several months already.

Click here to see the full blog post

We've had some really great contributions to our language files since we started supporting translations in NodeBB core, although keeping up with the changes has been quite hard. Specifically:

• There was never really any way to check if any changes were out of date, except trying out every page of NodeBB in a new language and looking for incorrect language tags
• When a language tag was missing, the system ended up showing the unattractive "code" behind the tag, instead of a sensible fallback like English

To that end, we've registered NodeBB as a project on Transifex! Using a web site like this will allow us to see at a glance how complete each language is, and allow translators to quickly see which strings need translating, and which do not.

(clap)

Start Translating Now!

Following up from here, in the lead-up to ForumCon, the NodeBB developers are hosting a Google Hangouts AMA (Ask Me Anything) session!

Date: Monday, June 16th, 2014
Time: 20:00 (8pm) Eastern Daylight Time (GMT -0400)
Location: Google Hangouts, link will be posted here (and twitter, and facebook, etc) when it begins.

Tell your friends, tell everybody! We'll be talking about ForumCon and some really exciting things we have planned for NodeBB v0.5.0 and beyond. Hope to see you there!

Session Sharing for NodeBB

In a nutshell, this plugin allows you to share sessions between your application and NodeBB. You'll need to set a
special cookie with a common domain, containing a JSON Web Token with user data. If sufficient, this plugin will
handle the rest (user registration/login).

How is this related to SSO?

Single Sign-On allows a user to log into NodeBB through a third-party service. It is best (and most securely)
achieved via OAuth2 provider, although other alternatives exist. An example of a single sign-on plugin is
nodebb-plugin-sso-facebook.

Single sign-on does not allow a session to become automatically created if a login is made to another site.
This is the one misconception that people hold when thinking about SSO and session sharing.

This session sharing plugin will allow NodeBB to automatically log in users (and optionally, log out users)
if the requisite shared cookie is found (more on that below).

You can use this plugin and single sign-on plugins together, but they won't be seamlessly integrated.

How does this work?

This plugin checks incoming requests for a shared cookie that is saved by your application when a user
logs in. This cookie contains in its value, a specially crafted signed token containing unique identifying
information for that user.

If the user can be found in NodeBB, that user will be logged in. If not, then a user is created, and that
unique indentifier is saved for future reference.

Read more at the project repository

Updates

• v1.0.13 released
• v2.0.0 released

I suppose in the grand scheme of things, the wait between the last NodeBB release (v1.4.6) and this release, v1.5.0, has not actually been long, though it has felt like so because the development team has been working on it for quite some time. In fact, the first closed issue of this milestone was actually completed in mid-December, and we've been anxiously waiting for the right time to release it.

The reason why we've held off on releasing v1.5.0 until today is so we could fit in as many breaking changes as we could at one time. We've received constructive criticism in the past about how difficult it was to upgrade NodeBB due to breaking changes (some unintentional), and so since the last minor release (v1.4.0), we've changed our strategy once again so that subsequent releases along the same branch should be more stable.

Click here to see the full blog post

Hello everybody,

The NodeBB team is proud to release v0.7.2, the second revision along the v0.7.x branch. As mentioned in an earlier post, we're aiming to launch more often (roughly every week or so), and the Persona theme is now standard across all new installations.

Since v0.7.0, we've also added Serbian and Danish to our list of supported translations, bringing our total up to 38 languages! More languages are undergoing translations at the moment, and supported languages will always need updating. If you speak a language other than English, please check out our internationalisation project on Transifex!

Concurrent with this release, I'm also releasing a Two-Factor Authentication plugin for NodeBB. To my knowledge, this is a feature unique to forum softwares, and one that is definitely in-demand. In fact, we're already seeing downloads of the plugin, and it hasn't even been formally announced yet!

For those of you in the San Francisco/Silicon Valley area, @psychobunny will be in town for the next two weeks! If you want to grab a coffee or otherwise meet one of the founders (and not to mention, our main designer) in person, feel free to send him an email

This past week, we also happened to hit 10,000 commits on GitHub, which we couldn't have done without our 99 contributors! Who will be the 100th?

For all of our supporters who have been with us since the beginning, and to those who are just joining us recently, thank you for spreading the word about NodeBB -- simply seeing NodeBBs in the wild still makes my day, and we're all happy to make a difference in the forum ecosystem, one community at a time.

The version history can be found on the project's GitHub wiki, and will be updated periodically.

Just some teaser screenshots of what you can expect to see when it comes to user groups, in v0.6.1.

Right now, groups are more of an administrative concept -- users are slotted into groups based on an administrator's decision. These changes introduce the concept of a private group, where members must request access from the owner. In addition, groups can be made public, so anybody may join.

Let me know if you have any questions about how this will work

Spring has finally arrived in Toronto, and that means it's time for a brand new NodeBB release!

So what's new?

We initially planned this release for late April, although we ran into a couple of last-minute blockers that necessitated pushing back the launch until today. We're excited to share this new version with you as it contains a couple of new features that allow for compliance with GDPR, as well as fixing a number of issues present in the current stable release.

Click here to see the full blog post

It's @psychobunny's birthday today! He's 28 now :trollface:

Please take a look at the official Plugin Writing Guide

@dunlix Ah yes sorry, I just hit reply on your post and it pre-populated your username.

Gosh... you know, I wish the people who made this stupid forum software would fix that

@Pitaj sure

@zxh the /api/user/email/:email API call is a GET route, not a POST route.

e.g. https://community.nodebb.org/api/user/email/julian@nodebb.org

@dunlix Can you tell me what is running in front of your server.... nginx, IIS, etc?

The HTTP2_PROTOCOL_ERROR is also of interest...

@smoe said in Multiple processes. Is Redis required?:

Ok. We should change / mention that in the documentation, too.

Thanks for the heads up, I'll make that change in the docs.

@yeehi It looks like the global chat plugin just adds a global chat room using the existing chat UI, so there is nothing new there.

@maiseu Thanks, added to our tracker: https://github.com/NodeBB/NodeBB/issues/9872

julianlam created this issue in NodeBB/NodeBB

closed Show unread notifications in PWA icon #9872

@bejan Our community reps are pretty awesome, we're lucky to have them

Our docs are open source, and we accept pull requests to them: https://github.com/nodebb/docs

We would greatly appreciate tweaks to the docs so that they are more accessible.

While I suppose more documentation doesn't always mean better documentation, we are always grateful for contributions

Probably the GA plugin currently doesn't send user data to Google Analytics. It'll need to be added via a PR.

@baris Thanks for the heads-up, v0.5.12 has been deprecated for the version mismatch issue, so v0.5.11 should be the recommended version

@maxwaldorf I just deleted the 1.18.2 tag from Docker Hub -- I most likely won't regenerate the image. v1.18.3 will be the next release with a Docker image.