Hmm, so I just found an interesting behavior that might be the cause.
It appears that NodeBB uses the websocket by default, but when the connection fails, it falls back to polling!
It does not appear to reconnect to the websocket after the failure. There's an easy way to see this - open up Chrome's dev tools on a NodeBB site, then kill your network connection.
It starts sending polling requests, and continues even after the connection is re-established!
Perhaps this is the reason that it gets "stuck" and has weird connectivity bugs?
@a_5mith I fully understand that. I come from SMF, in terms of the software my community was using.
But I am saying I've had a very serious problem before, where no time limits were set on deletion and edification. One previous member had the time and energy to go through their 200+ forum history and erase everything.
Once bitten, twice shy. If I have to mod something but the feature still technically 'exists' (as in, it's only a cover-up on the ui) then I don't feel safe using the software.