@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.
I think this is plugin territory. In my forum I have several threads where only admins can post updates for users. Not really a discussion topic, more of a change log or mini blog. If posts were to start merging the updates would get tangled.
Just one use case, but I'd prefer the core code not to automatically join double posts....or at least make it an option.
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.