Bug Report

@crazycells it is, yes - I think I’ll leave it as there is no specific PWA CSS classes I know of. Well, you could use something like the below, but this means multiple CSS files for different operating systems.

/** * Determine the mobile operating system. * This function returns one of 'iOS', 'Android', 'Windows Phone', or 'unknown'. * * @returns {String} */ function getMobileOperatingSystem() { var userAgent = navigator.userAgent || navigator.vendor || window.opera; // Windows Phone must come first because its UA also contains "Android" if (/windows phone/i.test(userAgent)) { return "Windows Phone"; } if (/android/i.test(userAgent)) { return "Android"; } if (/iPad|iPhone|iPod/.test(userAgent) && !window.MSStream) { return "iOS"; } return "unknown"; // return “Android” - one should either handle the unknown or fallback to a specific platform, let’s say Android }

Once you’re in that rabbit hole, it’s impossible to get out of it.

@phenomlab thank you very much, this was helpful. Everything looks ok 🙂

@Panda You’ll need to do that with js. With some quick CSS changes, it looks like this

d619844f-fbfe-4cf1-a283-6b7364f6bf18-image.png

The colour choice is still really hard on the eye, but at least you can now read the text

@Panda It’s the best it’s ever been to be honest. I’ve used a myriad of systems in the past - most notably, WordPress, and then Flarum (which for SEO, was absolutely dire - they never even had SEO out of the box, and relied on a third party extension to do it), and NodeBB easily fares the best - see below example

https://www.google.com/search?q=site%3Asudonix.org&oq=site%3Asudonix.org&aqs=chrome..69i57j69i60j69i58j69i60l2.9039j0j3&sourceid=chrome&ie=UTF-8#ip=1

However, this was not without significant effort on my part once I’d migrated from COM to ORG - see below posts

https://community.nodebb.org/topic/17286/google-crawl-error-after-site-migration/17?_=1688461250365

And also

https://support.google.com/webmasters/thread/221027803?hl=en&msgid=221464164

It was painful to say the least - as it turns out, there was an issue in NodeBB core that prevented spiders from getting to content, which as far as I understand, is now fixed. SEO in itself is a dark art - a black box that nobody really fully understands, and it’s essentially going to boil down to one thing - “content”.

Google’s algorithm for indexing has also changed dramatically over the years. They only now crawl content that has value, so if it believes that your site has nothing to offer, it will simply skip it.

@phenomlab

Seems to be better with some scaling fix for redis on redis.conf. I haven’t seen the message yet since the changes I made

# I increase it to the value of /proc/sys/net/core/somaxconn tcp-backlog 4096 # I'm uncommenting because it can slow down Redis. Uncommented by default !!!!!!!!!!!!!!!!!!! #save 900 1 #save 300 10 #save 60 10000

If you have other Redis optimizations. I take all your advice

https://severalnines.com/blog/performance-tuning-redis/

@pwsincd welcome to sudonix, and thanks for the comments. What your looking for is here

https://sudonix.com/topic/195/nodebb-welcome-message/3?_=1648295651358

And now, after all this time 😕 I finally discovered that the CSS I previously referenced was for something else - and used the same CSS name, so I’ve had to reinstate this block 🤦

.tab-content { max-height: 0; padding: 0 2em; color: #898989; background: #eeeeee; transition: all 0.35s; margin-top: -5px; }

And, add this below to make it more specific.

.emoji-tabs .tab-content { height: 100%; max-height: 100%; padding: 0; margin: 0; }

@phenomlab yes, i can understand. it is working now 🙂