That's not a bad idea... we just don't have plans to split the sites yet.
I understand that you don't want to split up anything, but how about mentioning the OpenSource version at all? 🙂
Right now, when I go to nodebb.org, the only chance to see that there is a free version that I can roll out myself is to know what the github logo looks like and then scroll down all the way to the bottom to spot it there (very small, barely visible).
Additionally, if I have AdBlock Plus turned on, these social buttons do not appear at all.
I perfectly understand that you want to earn money and therefore want to focus the page around your hosting service but I think that you could significantly cut the amount of requests from people who heard about a cool OpenSource forum and who now struggle to find a link to download it.
Something that interested me when I first started hacking on NodeBB was how the platform uses realtime communication through socket.io (and websockets). This interest stems from work I did whilst working as a realtime engineer at Pusher several years ago. One of my research projects whilst there was to look into how websockets get used in production, and other use cases for websockets besides the standard "subscribe to a channel and receive events".
How NodeBB currently seems to use realtime communication:
RPC: Request data from the server, get a response back, present that data to the user (or send data to a server like you would POST to a HTTP server)
Channels: Used for user to user chat messages
Events: Used for online/offline states of users.
I may have missed something here, so, let me know if I have.
Most of the websocket usage appears to be in RPC style messages: Get this piece of data do something with it. At present, all realtime communication for NodeBB is built on top of Socket.io, which uses a protocol more tailored for event type packets, rather than for RPC style packets. For this, something like JSON RPC may be more appropriate.
For user-to-user chat messaging you could still multiplex that onto the same actual websocket / socket.io connection (although it's arguable if this is actually beneficial).
Why do any of this writing or work? Interest more than anything else, but it may make the code to NodeBB cleaner, and improve maintainability.
Not rude, just wondering why you were tagging me for input for plugin requests. I'm a pretty random person to have asked to respond about them.
Cos, You replied to my previous thread. So I thought you'll be throwing some light about NodeBB.
Sure, but your questions were about feature requests. Your original question was about when NodeBB would be enterprise maintained, and that was easy to answer... five years ago and continuously since then. It's absolutely enterprise ready now.
Your next set of questions weren't really questions, but just mentions of features specific for you that you'd like someone to develop. There wasn't really a question to answer there, it's just a note that you'd like to see those features. Not much that I, as a long time user, can say about those.
I can shed light on the usual paths... you can make a thread requesting them (one thread each or no one will notice), but unless they get loads of traction, there is no reason to assume that NodeBB will even consider that - that's not how the core system works. You can hope that others want them too and that someone third party makes a plugin for you to use, but if that is going to happen it is most likely to have already happened. You can offer a bounty on the plugins. Or you can hire either NodeBB themselves or a third party to make plugins. That's easy to do, but expensive.
Other than that, I'm just an end user like you, but not one that wants those features so am glad that NodeBB is not focusing on them.
The reason that no one responded to that particular post is because, if you read it, there isn't a question - nothing that would warrant a response. So I had read it, but it just seemed like you were mentioning a wish list. Which would make no sense for me to respond to since you weren't wishing it from me.