I don't think this is realistic until core switches to typescript.

Hi! We have many NodeBB plugins that are no longer maintained, but people still want to use them. Can we fork them to NodeBB Community (or other) namespace on GitHub and publish under @nodebb-community (or other) namespace on npm? To allow the installation of those plugins from ACP - we can increase the range of search to this namespace too. What do you think about this idea?

This is now available, sample implementation for a plugin https://github.com/NodeBB/nodebb-plugin-friends/commit/6e6f2f45b1ebf42cb1d688070c777a02eda1fd4a. Thanks @Antosik

Hi! Found a bug with SSO registration flow: Install and configure Google or Discord SSO plugin (or any other, maybe) Enable GDPR consent collection (ACP-> Settings -> Users) Logout after that and click "Register" Authorize with your provider You will see the registration "interstitials" Click "Cancel registration" Check the user list with your Admin account - You will see that account successfully created This behavior works only with SSO.

@antosik said in NodeBB + MongoDB + Scaling (k8s): @PitaJ I'm not against it ^^. Just want to research a bit before giving AWS more money. :d @baris So, we need to try: implement something like src\database\redis\pubsub.js in mongo; check out socket.io-adapter-mongo and @nodebb/mubsub packages? UPD. Found an interesting thing - maybe we can use watch + changeStream to implement the pubsub ? What's your overall goal? I have a feeling that you are giving AWS way more money than you should already. If the goal is to go big without wasting money, this isn't the approach. Unless you are doing something in the billion hits a month range, I don't think that this approach can be cost effective at all. So if you want to give AWS money just for fun, then you might as well give more. If you want to be cost effective, then setting yourself up for scaling will require more scale than will ever be practically needed.