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
Co-Founder, NodeBB Inc.
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:
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.
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!
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).
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
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.
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.
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
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
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
After much anticipated demand, I'm proud to say that Push Notifications have landed in NodeBB!
We've been in touch with PushBullet, a Y Combinator-funded startup in San Francisco, and they granted us early access to their OAuth based integration, allowing me to bring this to you guys. We're going into full testing mode with this now that the plugin is more or less complete, so you can try it out here on this forum (by clicking the "Pushbullet" menu option in your user settings), or by clicking here
Pushbullet released their OAuth interface yesterday, and so now's the perfect time to unveil our integration with it too!
This plugin is a premium plugin. What this means is that upon release, it is available exclusively to members of our hosted community and select partners. After a short period, it will be released publically and published on npm like other plugins.
Tentatively, the release date is scheduled for: When NodeBB v0.5.0 lands
EDIT: The plugin is now available to the general public! Install it via
npm install nodebb-plugin-pushbullet
Spring has finally arrived in Toronto, and that means it's time for a brand new NodeBB release!
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
@abarnes hey there, and thanks for posting!
In the write API plugin, this was originally a configurable option via the ACP, but in this new code we decide to turn it on or off based on the configured URL.
I did not anticipate this usage, my apologies! I will try to come up with a suitable alternative for auto-detection, and failing that, I'll just make it a configurable option again.
@crazycells @psychobunny is more well versed with this, but the only real functional difference is that it likely loads a bit faster now (at least, after the first load) because a lot of the pages are cached.
Before, it would reload the page just like you were visiting in a browser.
We don't support natively things like notifications yet, but it is a step in the right direction
@nefarius For what its worth, spam-be-gone is still very much actively maintained, but we don't get to many bugs for it because it just works
I'm not saying it's the perfect solution, by any means, but we will definitely fix up issues if reported.
Hi @togan, I've actually worked on getting the poll plugin compatible with latest Quill. It should be working fine with the latest poll version (v1.1.2)
spawn sendmail ENOENT means NodeBB is attempting to send emails by calling the local sendmail executable, which does not exist.
You'll need to re-check your amazon SES configuration settings... is this via plugin or direct via ACP?