New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with notifications and Message Carbons. #107

Closed
maranda opened this Issue Jan 1, 2014 · 2 comments

Comments

Projects
None yet
2 participants
@maranda

maranda commented Jan 1, 2014

I noticed that proper notifications aren't always played or shown when there's a new sent or received message being forwarded neither in the notifications dock or within the app although if I open the conversation history with the contacts the messages are there.

@ge0rg

This comment has been minimized.

Show comment
Hide comment
@ge0rg

ge0rg Jan 2, 2014

Collaborator

yaxim is using sophisticated logic[tm] to prevent beeping all the time when the phone is on your desk and you chat using the PC. The logic (in the nightly releases as of December 2013) is as follows:

  • no notification/ringtone on "sent" carbons, i.e. for messages you wrote on the PC
  • one audible notification on the first "received" carbon
  • silent notification updates on further "received" carbons, until you open the chat window
  • audible notifications on received non-carbon messages

However, all messages, carbons or not, are shown in your chat history (this also includes their XEP-0184 message ack status).

That way, when you are actively chatting on your desktop PC, yaxim will only make one beep and go silent. After you check yaxim for messages, it will beep again, even if your buddy is still messaging your PC client. That way you should neither be bothered by perma-beeping, nor lose wrongly-targeted important messages.

Please let me know if what you are seeing differs from the described behavior, or if it is as described, but is not "the right thing to do". For this, please describe what you would expect, and what happens instead.

Collaborator

ge0rg commented Jan 2, 2014

yaxim is using sophisticated logic[tm] to prevent beeping all the time when the phone is on your desk and you chat using the PC. The logic (in the nightly releases as of December 2013) is as follows:

  • no notification/ringtone on "sent" carbons, i.e. for messages you wrote on the PC
  • one audible notification on the first "received" carbon
  • silent notification updates on further "received" carbons, until you open the chat window
  • audible notifications on received non-carbon messages

However, all messages, carbons or not, are shown in your chat history (this also includes their XEP-0184 message ack status).

That way, when you are actively chatting on your desktop PC, yaxim will only make one beep and go silent. After you check yaxim for messages, it will beep again, even if your buddy is still messaging your PC client. That way you should neither be bothered by perma-beeping, nor lose wrongly-targeted important messages.

Please let me know if what you are seeing differs from the described behavior, or if it is as described, but is not "the right thing to do". For this, please describe what you would expect, and what happens instead.

@maranda

This comment has been minimized.

Show comment
Hide comment
@maranda

maranda Jan 2, 2014

No sounds okay, and verified that's what happens.

maranda commented Jan 2, 2014

No sounds okay, and verified that's what happens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment