@baris would be nice to have the pagination component build as a plugin. That way people could just use the same hooks at the actual component and modify or implement different ways of pagination.
I think that if i would want to build a different way of pagination (lets say, use a lib for that) even if i use the same hook for pagination socket.on('event:new_post', onNewPost); , because the pagination code still present in the core of nodebb, that code would execute anyway, so even if i use my own code to paginate, the core code would execute, even it would not needed at all.
I think it should not be difficult to migrate the pagination mechanism to a plugin, as it was made for the composer. Or maybe the bast majority of the core code should still present but a few new hooks should be created.
Powerfull and more usefull IMO.
@psychobunny you mean us? not really, still witnessing weird behaviour on https via mobile connection from mobile devices (smartphones + tablets)
Yeah, it'd be either your browser (stock browser, or chrome?) or your ISP (sometimes websockets not established on 3G). The new socket.io version is not implemented in NodeBB yet...
@julian said in RFC: Drop support for old node.js versions?:
Those in enterprise environments?
Edit: Good lord, it's 11-0 right now.
Ehh, even enterprise needs to drop support for older dependencies. Especially these days where old versions can lead to security issues!