I did the following and have very little spam issues:

• Use all elements the "Spam Be Gone" plugin offers: Askimet post check, Honeypot registration, Re-Captcha (v2) for registration, Stopformspam post check. All at default settings at the moment
• Disabled "About me" and "Signature" profile elements as the "Spam Be Gone" plugin does not check these
• Beep plugin to censor prohibited words on legitimate posts / topics

So far I have not had to use the post or registration queue. Not popular enough yet I guess, so the "Spam Be Gone" plugin suffices for now. I am very grateful for the anti spam tool-suite, which do work great. I know for a fact we would be riddled with spam without it.

I am still in the process of getting an AdSense account, one odd thing I noticed with plugin version 1.0.4 on Nodebb 1.12.2 is a weird rendering / navigation-to issue with the ACP. Whenever I exit the Google Adsense ACP and re-enter the ACP via navigation the ACP will not render. It will only render after one additional refresh or when I paste the ACP url from the navigation menu manually into the browser bar. It does seem to store settings fine.
I already reinstalled the plugin, re-ordered all plugins to the recommended order and did a rebuild a number of times, with no change. I hope this is just a harmless ACP navigation bug?

@PitaJ Awesome idea, indeed! If About Me, Website and Location are pulled into a single field this new field should at the same time be presented to the "Spam Be Gone" plugin elements to prevent spam in this field or it has no value long term IMHO.

NodeBB is open source, so it is free for everyone to run and host by him/herself. There are commercial plans available for professional hosting though.

As "About me" is mostly abused, I would like to disable "About me". I only found a setting to set maximum length to "0". Did I miss something? In this community I do not see an "about me" section in my profile so there must be a way.

Oh and how can the "website" section in profile edit be disabled? At least there is a nofollow directive on that url.

I am using the latest version of the beep plugin 0.4.2 on the latest version of NodeBB 1.12.2. I have one issue with the beep plugin regarding old topics which were created before I migrated my site to NodeBB which have words which should be censored.

Newly created topics are censored with the beep plugin just fine. In the MongoDB the beep plugin actually saves topics with the censored words, so e.g. "title" : "Ps test censor" or "slug" : "123/ps-test-censor" is persisted in the database. Posts are obviously not modified by the beep plugin in the database but on the fly. Queries on the DB show the full non censored words in all posts be it old or new posts. Old and new posts are correctly censored by the beep plugin on the fly during browsing of NodeBB forum.

To fix this, post processing must be run on all topics in mongodb to modify "title" and "slug" applying the current beep censor rules.
Fortunately, I did not have that many topics to fix, so a quick manual fix is to just open each offending topic once, editing the topic as admin and saving it.

As a future improvement of this plugin, it would be very nice to have a simple button in the admin panel which runs a post-processing script for the above issue. This would be especially helpful on any change of the censor words down the line.

@baris The Jointcrackers community is using NodeBB - https://www.jointcrackers.com/.