@julian
Sorry forgot this one, mail notification settings says
"Send an email if a new chat message arrives and I am not online"
And I receive one even if I'm connected (but not on same tab) which does not match option configuration 😉

Hummm, that's why I searched on all options with no success 😉
glad to know I'm not crazy,
thanks @julian

@julian,
it 's the same thing

Internal error. Oops! Looks like something went wrong! /auth/github/callback Cannot read property '0' of undefined

is there a way to clear github related information from a user in the nodebb database ?

Julian,
Yeah I saw this, but in fact it's more the way it's showed that I would like 😉 I know it's just presentation but this make it easy to show which category is the most active

Ensuring compatibility is quite a daunting task, especially since core itself does change often (less so than before, but occasionally still does).

In the case of bundled modules, that is, those defined in package.json, if they are out-of-date or too far ahead, they will cause NodeBB to not function. Its behaviour is quite restrictive, although it is intentional!

We're considerably less restrictive when it comes to third-party plugins, and all we read is the nbbpm.compatibility portion of package.json. Even then, we can't ensure that a dev will keep this section up to date, or even that there will be a section at all! So it is merely a suggestion, though I am open to changes.

I am considering changing nbbpm itself so that if a nbbpm.compatibility section is not found, it will not be added to the plugin listing. Right now a great majority of plugins don't specify compatibility information at all...

Haha, nice one. I need to correct myself, too. 😓
Turns out I just wanted more, more, more(!), again. 🙂

Excellent, I need to try this ASAP 😉

And for those who're interested here the trick on nginx (mine on /etc/nginx/sites-enables/default) for nodebb

################################# # community.yourgreatdomain.com # ################################# server { listen 80; server_name community.yourgreatdomain.com; return 301 https://$server_name$request_uri; } server { listen 443 ssl; server_name community.yourgreatdomain.com; ssl_certificate /etc/ssl/community.yourgreatdomain.com.chain.crt; ssl_certificate_key /etc/ssl/community.yourgreatdomain.com.key; location / { proxy_pass http://localhost:4567/; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_redirect off; proxy_buffering off; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } }