I know it is blasphemy to reply/reopen an old thread, but I think I have some sort of workaround for this. Say that per-category header warning message is 1) not going to be as native functionality, or 2) still waiting for plugin for that, I think a pinned thread atop all threads would suffice.
the software is open source so whatever exposure we can get is more than appreciated given the work we've put into this.
that said, legally nothing is stopping you from removing the copyright footer. we're just happy enough that you're using the software:)
@Jacob-Bridges no problem buddy, I've used it myself on occasion, so can't claim to be as highly philosophical as I make out. But i don't believe developers/designers should be forcing non default browser options like target attributes on users. then again, people have argued about it for years, so it's not going to be definitively resolved anytime soon.
Let us know if we can be of any more help, NodeBB are currently hosting a competition, if you're looking at writing plugins, you've joined at a great time.
@baris Yes I use Redis for NodeBB, so it gets applied to the integrated socket.io. But also it seems like I misinterpreted the problem for some reasons...
Several features are not working with clustering, for example the chat:
I can open it, but...
As you see in this screenshot, sometimes I get the messages and sometimes I don't.
Or the plugins, I can initiate installation and nothing happens but the image changes. Installation through the ACP just don't work with clustering. I haven't tested it yet together with websockets, as I'm a cloudflare customer and haven't got access to the websockets right now.