XMPP, strophe.js debug for chat based on Ejabberd, new message count still displays while msg already read
Budget: $10 – $30 USD
We are developing a website based on PhP, javascript. We have developed a chat client/window based on strophe.js.
In our project, we only use multi-user based chat, no individual chat.
Currently, when a user has messages that have not been read, it will display a red dot and # of messages not read yet.
However, there's an issue now. When a user logs out and then logs in again, after a while, it displays a new msg alert, while this msg has already been read already.
The new msg is based on the timestamp of message. If the timestamp of a msg is behind the last read/click time of the chat, the msg is marked as a new msg. Otherwise, it's read. Then we know how many messages are new msgs.
We need you to check and fix this small issue.
The work needs to be done using remote control software like teamviewr or anydsk.
Obviously, if you know strophe.js well and XMPP protocols, it should be just a few min work.
In our project, we only use multi-user based chat, no individual chat.
Currently, when a user has messages that have not been read, it will display a red dot and # of messages not read yet.
However, there's an issue now. When a user logs out and then logs in again, after a while, it displays a new msg alert, while this msg has already been read already.
The new msg is based on the timestamp of message. If the timestamp of a msg is behind the last read/click time of the chat, the msg is marked as a new msg. Otherwise, it's read. Then we know how many messages are new msgs.
We need you to check and fix this small issue.
The work needs to be done using remote control software like teamviewr or anydsk.
Obviously, if you know strophe.js well and XMPP protocols, it should be just a few min work.