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!

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

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!

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

Recently, a milestone had passed me by without my knowing – the original start date for my very first programming job was May 3rd, 2010. Ten years have flown by (or in some cases, have dragged by), and much has changed both in my personal and professional life, and much has stayed the same. I thought it would be a nice exercise to look back and see where I came from.

Click here to see the full blog post

Please take a look at the official Plugin Writing Guide

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

@א-ש

You don't run ./nodebb setup to upgrade.

• pkill -9 node to kill off NodeBB running on the machine.
• ./nodebb upgrade to upgrade
• ./nodebb start to start

As for search... try re-indexing the forum content from the DB Search plugin page in the ACP.

@gotwf The reason why we went with DigitalOcean (or Linode, or Hetzner, or any other "VPS as a service" offering) is because I explicitly don't want to handle bare-metal servers.

There are significant cost-savings to be had, but at the same time, if things go belly-up on a Sunday at 3 in the morning, who gets paged? Me!

On the other hand, using DO give us significant cost savings compared to if we had built our infrastructure on Heroku, GCP, AWS Lambda, etc...

On the latter point, I haven't actually done the math, so maybe a deployment on Lambda could end up being more cost effective, so who knows.

All I know is I also like shell access

@PitaJ https://github.com/pitaj/nodebb-plugin-calendar/pull/148/files

barisusakli created this issue in pitaj/nodebb-plugin-calendar

open refactor: move acp script to modules #148

@faizanzahid said in Thoughts on content ownership and long, meaningful discussions:

d. In Ability to follow tags , like if we follow a topic on quora, we see all posts tagged with that topic in our news feed. Would love to have this.

I agree with this in part, but always with caveats.

The moment you put in a "feed" of sorts, you're embarking down a path of curated content, and that is the antithesis of what forums are about.

The really great thing about forum software (and web 1.0 as a whole) is the act of content discovery. We make that easier with things like /recent and /unread, but I draw the line at having some sort of "recommended" list of what one should read.

It's none of my business what you like, and beyond the scope of NodeBB to try to determine what you should read.

@Freelancer Is this you? https://github.com/NodeBB/NodeBB/issues/10632

Disable the admin timeout and that should resolve it.

AkanshDivker created this issue in NodeBB/NodeBB

closed NodeBB Admin Timeout #10632

@Thangaraja-C Not easily, you'd have to code it.

At a high level;

• Export that excel to csv
• Write a script to use the Write API to iterate through that CSV, row by row, and create topics/replies.

@Thangaraja-C Can you show us an example? In Persona, the first post has the same design as the replies.

Over the years, NodeBB has amassed quite a collection of plugins, most of which were published to npm and listed in the “Manage Plugins” page in the admin control panel. With the release of v2.0.0, we received some reports that the plugin directory was now empty. This was intentionally done, for a number of reasons—read […]

Click here to see the full blog post

@omega said in Why hosted NodeBB is so expensive?:

$5 p/month

Digital Ocean has $4/mo droplet now

... but I cannot guarantee NodeBB will successfully build its webpack payload on such a small droplet.

Removing view privileges from spiders will get rid of most, but not all crawlers. As @gotwf says, crawlers are not the most law-abiding scripts out there.

Simply removing all guest privileges should do the trick, but if you're regularly copying prod to your dev forum, then the more surefire way to keep EVERYONE away would be to restrict access to a single IP or range (e.g. a VPN) you control.

That might be overkill, though.