Vote for NodeBB 0.4.1 Features
-
Ok, I'm jumping the gun a little bit here, but with the release of NodeBB 0.4.0 just around the corner, and with 4 features already listed for 0.4.1 on GitHub, I'm starting this topic as a way to give the community an opportunity to let the developers know the most requested features for the next release (after 0.4.0).
Tell us what features are most important to you and the rest of us will vote on it using the up/down vote buttons. Sorry we do not have a true voting plugin yet, but those up/down vote buttons will do for now. The feature requests with the most UP votes will get the attention of the developers, who have to make the final decision whether they have the time and motivation to work on them.
To avoid requesting a feature that's already being worked on, take a look at the current issues list on GitHub.
-
To get things started, here's my feature request for NodeBB 0.4.1:
A WAF (Web Application Firewall) or WAF-like feature that will give NodeBB some protection against brute-force attacks on user accounts.
If you run a server and monitor it, I'm sure you already know the number of attempts are made to forcefully log into the system using an existing user account. Now imagine the number of accounts on a platform like a NodeBB-powered forum and you can imagine the number of brute-force attacks on the system. And if you also consider that most of those user accounts will have very weak passwords, it gets even worse.
That's where a WAF with login monitor comes in. It can have other security features, but the basic ones are shown in this screenshot taken from a similar WP plugin.
-
-
Good ideas!
-
- mark as read per topic within unread-page
- category-filter for unread-page
If I want to read some posts it's just a bit annoying that after reading one the older ones are still present and I have to take a closer look to find my current position. Therefor it'd be great to mark single topics as read without looking into it...
-
Its not on the list but..
Email templates could also be translated
-
- List of previous usernames displayed on users profile
- Example Plugin to easily add user-settings if it's already implemented, otherwise a way for plugins to easily add user-settings (with possibility to add user-settings dependent on admin-settings)
Edit: second point already done as @psychobunny mentioned below: https://github.com/designcreateplay/nodebb-plugin-kitchen-sink/blob/master/library.js#L49-L74
-
@frissdiegurke said:
Example Plugin to easily add user-settings if it's already implemented, otherwise a way for plugins to easily add user-settings (with possibility to add user-settings dependent on admin-settings)
The hooks for this are
filter:user.getSettings
andfilter:user.saveSettings
. -
@baris said:
@frissdiegurke said:
Example Plugin to easily add user-settings if it's already implemented, otherwise a way for plugins to easily add user-settings (with possibility to add user-settings dependent on admin-settings)
The hooks for this are
filter:user.getSettings
andfilter:user.saveSettings
.So
getSettings
gets called whenever a value is needed, fair enough. but I cannot get the saveSettings triggered... Shouldn't it get called if I press 'Save Changes' on /user/xyz/settings?
Anyway, with these two I could add user-dependent settings, but I want to add some configuration to the list therefor the user may change them himself.
Sth. likefilter:user.listSettings
which serves a callback that accepts an array like[ "settings/xyz.tpl" ]
and would add the content of the template to /user/abc/settings.
(Just an example, there may be better ways than adding template-files)And another feature for 0.4.1: up-to-date hook-list within wiki ^^