Hi @julian @PitaJ @baris

Kindly consider the following:

1. When the user starts typing, client sends "typing notif" to the server
2. If the user continues to type after 30 sec, the clients sends another "typing notif"
3. The server broadcast "user typing notif" to the clients upon receipt of said (1) and (2), iff there was no prior "user typing notif" in the past 30 sec. (just to make sure the client is not illegally pushing typing notif)
4. The client clears out "user typing" from the DOM upon receipt of a message from said user, or following 30sec since the server sent "user typing notif"; and,
5. As for server->client notif in (3):
   a. (3) is executed for all clients that notified the server, such that a single message is formed containing all "typing" users; and,
   b. (3) is concatenated to a chat message sent by a user to same room (if there was one); and,
   c. (3) is executed just for the online users.

While not perfect, the cost is minimal:
client -> server: 1 message per typing users per 30 sec.
server -> online clients: 1 message containing all typing users per 30sec. (potentially no message at all given 5b).

Changing the latency granularity (i.e., 30sec above) will set a tradeoff between usability and cpu cycles.

@kikii and @laserfire3 take a look at:
https://github.com/NodeBB/NodeBB/issues/7330

pitaj created this issue in NodeBB/NodeBB

open Chat improvements #7330

Great job!

Hey @Kosiak
@julian delivers -

I would like to extend my appreciation for the amazing work you guys are doing. The endless hours that you are spending working on NodeBB, and the professionalism that you have shown continues to impress me, and I believe many many others, immensely. Thank you once again for all your effort!

Dear NodeBB Team,

May I humbly request to have Postgresql supported?

I understand that I am asking a lot, I mean, when you commit a feature, you have to support it going forward, so this may become a liability and a big headache, especially given the number of forums you must have on your back.

The upside is that Postgresql integration will allow simple and cost effective setup/hosting (for example in Amazon/Heroku, where Postgresql is provided as a service with automated backups/restore).

I believe (my humble personal opinion), that with Postgresql support, NodeBB will become more popular, especially with the teams that have less IT experience (yes, I admit I am one of them ).

It seems that @Ben-Lubar completed the Postgresql driver and has a pending pull request: https://github.com/NodeBB/NodeBB/pull/5861. It looks like the relevant DB tests passed and the driver is ready for action. Furthermore, from what I read the driver has similar performance to Mongo/Redis. I would love to see it committed to master so I could give it a test run.

Lastly, I realize that you must be extremely busy, so I totally understand if Postgresql is put on the back burner. I have yet to see a similar team that is so helpful. Thus so far you immensely helped my efforts and I am most appreciative.

Thanks again for your kind consideration,
JJ.

BenLubar created this issue in NodeBB/NodeBB

closed PostgreSQL database driver #5861

Amazing work, as always!

Hello Everyone,

I am new to NodeBB so kindly hold on with the tomatoes.

First, I must say that I found NodeBB only few days ago and been playing with it ever since.
I absolutely love it. You guys have made excellent work!!!

Kindly allow me to make a small contribution.

I was looking for ways to set up NodeBB with SSL, and I wanted to make sure the site is secured, and I must say that getting there gave me more gray hair than my calculus professor, lol Let me cut some corners for ya-all:

Target platform: EC2 @ Amazon
OS: Amazon Linux2

Installation Steps:

1. Note that in AWS Linux, you can't immediately install LetsEncrypt (Certbot) and Nodejs. For that follow:
   1a. Aws Linux 2 is similar to Centos7, the best way to install is to follow: https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/setting-up-node-on-ec2-instance.html
   1b. LetsEncrypt (with manual hack): https://community.letsencrypt.org/t/help-with-certbot-on-the-new-amazon-linux-2/49399/7
2. Follow: https://hostpresto.com/community/tutorials/how-to-install-nodebb-forum-on-centos-7/
3. Configure NodeBB with DB (I used AWS Redis - rants below)
4. Install nginx: In AWS linux: $amazon-linux-extras install nginx1.12
5. Note, I did not need to change SELinux on my setup.

Addressing SSL security:

1. Find out the latest setup recommendations for security for your nginx version: https://mozilla.github.io/server-side-tls/ssl-config-generator/
2. Remove exploits: Add into the nginx config file:
   
   nginx: How To Block Exploits, SQL Injections, File Injections, Spam, User Agents, Etc.
3. I was having real hard time with HSTS header - it looks as though someone else (nodebb?) is inserting this header, so don't include that header in nginx.
4. Check your site: go to: https://www.ssllabs.com/ssltest/ with the above you should get A+

Database Rants:

1. Redis (AWS Free Tier) does not support backup, and its mighty expensive otherwise.
2. MongDB is not available in AWS Free Tier.
3. AWS Postgres is awesome and available for AWS Free Tier, making NodeBB + Postgres is the ultimate solution for AWS. I saw that mighty @Ben-Lubar got that figured out, however, his pull request is collecting dust as of Jan-13 (https://github.com/NodeBB/NodeBB/pull/5861). @barisusakli, your help pushing the code to master will be highly appreciated, thank you!!!

Security issues:
I wanted no guests, so following https://community.nodebb.org/topic/2371/faq-how-to-make-your-forum-private I added a small JS that checks if the UUID==0 and kicks the user to the login page.

1. Clicking breadcrumb in the login page allows the guest user to go back to the forum main page (in my case, categories). I disabled categories to guests, so that page is now blank.
2. The said JS code does not run for guests users, so if the guest used breadcrumb to redirect to the main page, I would have expected redirection to login.

How to repeat? Simply log out of your account. To resolve, may I suggest to:

1. Remove breadcrumbs from the login page
2. Allow the js code added in the admin page, to run for guests as well.

Additional issues:

1. I installed the onesignal plugin, and I can confirm it does not work. Note, I pulled the latest code from github: https://github.com/CCob/nodebb-plugin-onesignal . Furthermore, the plugin description is a bit difficult - where should I change the "redirect_uri"? OneSignal gui does not allow you to add /onesignal/auth. Redirect entire site in nginx? but that would affect all users. @CCob your help will be highly appreciated.
2. I can confirm the text in the chat window (when not in full screen) is reversed from the getgo, that is with no special css. @mohammadhassan is correct (see: https://github.com/NodeBB/NodeBB/issues/6192 ). The issue exists in the master branch. @julianlam, your help will be highly appreciated. May I suggest to remove the text, and use an icon similar to the one used in the full-page chat? When will the new chat GUI become available in master btw?
3. Clicking the image of the user in the chat window (full screen), opens the user profile, but below the chat window. I believe it should be opened above the chat window - but this is no biggie.

Again, awesome forum!!! I love it. Amazing work guys. Chapeau!

All the best,
JJ.

[Now you can go ahead with the tomatoes]

julianlam created this issue in NodeBB/NodeBB

closed Rewrite chat frontend #6192

BenLubar created this issue in NodeBB/NodeBB

closed PostgreSQL database driver #5861

No problemo @Kosiak , do check back on this plugin after October.
If you are looking for WYSIWYG then I believe this could be the solution for you, since Redactor unfortunately may be on its way out.
Take care and good luck with your forum!
btw: i started few months ago as none-coder like you (and yeah I still suck...), so be careful you might get addicted and convert

Dear Devs,
Thank you very much for your continued support and for the ever evolving NodeBB forum.
Warmest thoughts and best wishes for a wonderful holiday and a very happy new year. Wishing you the gifts of the season — Peace, Hope and Happiness.
JJ.

Not much to learn from my experience, since my #users/day is pathetic.
As for tdwtf, I personally don't believe it would have been faster with Mongo, but I could be wrong. I looked but unfortunately I could not find the exact benchmark chart I was referring to earlier. Nevertheless, see here: https://what.thedailywtf.com/topic/25362/so-about-that-postgresql-thing/8?lang=en-US&page=1

Finally, you should consider visiting tdwtf often, the posts there are among the funniest I have ever encountered

Thank you very much for your recent release.
Your humble contribution foster communication and help make the world a better place.
It is always intriguing to review your code and learn.
Wishing you the best!
JJ.

Hi @julian @PitaJ @baris

Kindly consider the following:

1. When the user starts typing, client sends "typing notif" to the server
2. If the user continues to type after 30 sec, the clients sends another "typing notif"
3. The server broadcast "user typing notif" to the clients upon receipt of said (1) and (2), iff there was no prior "user typing notif" in the past 30 sec. (just to make sure the client is not illegally pushing typing notif)
4. The client clears out "user typing" from the DOM upon receipt of a message from said user, or following 30sec since the server sent "user typing notif"; and,
5. As for server->client notif in (3):
   a. (3) is executed for all clients that notified the server, such that a single message is formed containing all "typing" users; and,
   b. (3) is concatenated to a chat message sent by a user to same room (if there was one); and,
   c. (3) is executed just for the online users.

While not perfect, the cost is minimal:
client -> server: 1 message per typing users per 30 sec.
server -> online clients: 1 message containing all typing users per 30sec. (potentially no message at all given 5b).

Changing the latency granularity (i.e., 30sec above) will set a tradeoff between usability and cpu cycles.

@kikii and @laserfire3 take a look at:
https://github.com/NodeBB/NodeBB/issues/7330

pitaj created this issue in NodeBB/NodeBB

open Chat improvements #7330

@alfazaz
Yes,
Create a module, say dt.js.
Paste the datatables code into said file.
That module will be compiled with nodebb, and then you can just require the module in the client.
If you need help let me know.

@julian is being modest. this plugin kicks ass!

Hey @Kosiak
@julian delivers -

Not much to learn from my experience, since my #users/day is pathetic.
As for tdwtf, I personally don't believe it would have been faster with Mongo, but I could be wrong. I looked but unfortunately I could not find the exact benchmark chart I was referring to earlier. Nevertheless, see here: https://what.thedailywtf.com/topic/25362/so-about-that-postgresql-thing/8?lang=en-US&page=1

Finally, you should consider visiting tdwtf often, the posts there are among the funniest I have ever encountered

Pgsql v10 works perfectly for us (although our forum is tiny so it may not be a good test case). @Ben-Lubar however, did a number of performance comparison to mongo-DB, and it looks like pgsql is on par. You can follow his work in tdwtf. Good luck!

Great job!

Hi All,
Need some help please: I am trying to render a page that has just the last post (in html) of a certain topic. Can I access said data from the template system?
Thank you!
JJ.

Hey @youhosi , I love the chat layout, its beautiful great job!
@scottalanmiller I don't know the reason why FB and others decided to split the chat from the main app, maybe the wanted to cover multiple vertical markets, who knows :). Since most browsers support desktop notification IMHO notifications is not a showstopper. Kindly try What's app web page - I think you'll find it working well (in browsers).

By the way, @PitaJ open a GitHub issue about potential chat improvements. Its a good place to post your recommendations:
https://github.com/NodeBB/NodeBB/issues/7330

pitaj created this issue in NodeBB/NodeBB

open Chat improvements #7330