@crazycells thanks!

@volanar @volanar said in File and image storage engine and performance: You must upload files to folders by upload date (for example, current year - current month - current date). I would not necessarily say "must" as there can also be performance penalties from deep hash structures that are minimally populated. Caching is also a factor that can very favorably impact image delivery. At least w.r.t. the most popular ones. One more fer' the road: Many cloud providers are using SSD backed storage modern days. Is file I/O actually your bottleneck? Hmmm... How many images are you envisioning for YOUR site/use case? Just a couple shootin' from the hip thoughts. ymmv.

@volanar said in List of plugins that are incompatible when upgrading to version 1.19.2: nodebb-plugin-gdpr @baris @julian any updates on nodebb-plugin-gdpr ? This is required for me at least being GDPR compliant

I appreciate the changes made to the mobile theme. Much more useful now. I have one more suggestion to the team. When any topic is updated on mobile, the notification section at the top causes a slide. Maybe it would be a good idea to get this to the bottom part. [image: 1645259906677-screenshot_1.png]

When creating a multilingual forum, I faced the problem of distributing content in different languages. I liked how this problem was solved in invision power board. To create a multilingual forum, I need to develop a plugin that disables unnecessary languages and adds additional fields to the platform settings for adding content in the required languages. To begin with, I need to have additional fields for the names and descriptions of categories, as is done in invision power board. Who can do it, send your suggestions in the chat

I'm waiting for improvement on this too

@julian said in Rocket.Chat SSO + embed plugin for Nodebb: @volanar contact us at [email protected] and we can discuss details Done

For an automatic transition from www to no www, this code works well if ( $host ~ ^www.(?<domain>.+) ) { rewrite ^/(.*)$ $scheme://$domain/$1; Express.js does not support http/2. Or am I wrong? Does it make sense to include http/2 support in nginx?