Ran into this issue as well, used conditionals which Baris broke when everything switched over to loggedIn rather than isLoggedIn.
Ah well, it's nice having every conditional the same anyways!
For efficiency and security reason, I use https to protect users and our site. However, there is a noticeable downgrade of getting the content of the website. So I wonder if there is a better way of serving anoymous users which does not input their propriety assets. so that http is better, and https seves registered users only.
@jiangcaiyang you could use nginx in front and maybe get this to work but unlikely. It's not a good idea, regardless. HTTPS is good for everyone regardless of the sensitivity of the information. If HTTPS is causing a noticeable performance lag, you may be having other issues.
With all optimized steps on, I could get as fast as previous when https not enabled, but far more faster when https enabled. Other bottleneck could be the images. Recently, I'm working hard on reducing warnings of mixed content, so I'm not prefering 3rd party images and assets, rather using the resources provided our own.
@jiangcaiyang you shouldn't have too many issues with mixed content at least in core. If you do, please report a bug with the Github issues. Make sure you have the address in config.json set correctly to the endpoint of your site.
@PitaJ Thanks, it is actually not the issue of NodeBB, it is the decision on which strategy to choose. Anyway, I've done no worse than before, that is enough.
Test the out image links: