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

Own messages are marked unread when using other Facebook apps #161

Closed
Smile4ever opened this Issue Oct 31, 2015 · 6 comments

Comments

Projects
None yet
2 participants
@Smile4ever

Smile4ever commented Oct 31, 2015

I don't know if this is in the control of purple-facebook, but if I use the Messenger app and I send a message to my contact person, my own message appears in Pidgin unread.

I know that I sent that message, so Pidgin doesn't need to remind me.

@jgeboski

This comment has been minimized.

Show comment
Hide comment
@jgeboski

jgeboski Oct 31, 2015

Collaborator

Duplicate of #131?

Collaborator

jgeboski commented Oct 31, 2015

Duplicate of #131?

@Smile4ever

This comment has been minimized.

Show comment
Hide comment
@Smile4ever

Smile4ever Oct 31, 2015

No. Because the conversation window is already open. I would like a "auto mark as read" when the sender == myself.

Smile4ever commented Oct 31, 2015

No. Because the conversation window is already open. I would like a "auto mark as read" when the sender == myself.

@jgeboski

This comment has been minimized.

Show comment
Hide comment
@jgeboski

jgeboski Dec 28, 2015

Collaborator

Given the current limitations of the libpurple interfaces, this is not possible without digging into Pidgin or Finch. I have zero interest in doing anything which requires resources outside of libpurple. It really hinders the compatibility with other third-party clients.

The real issue is that there is no real self-message capability in libpurple, and this plugin has had to hack the functionality in. Maybe at some point in the future, the development version of libpurple will support such an interface.

Collaborator

jgeboski commented Dec 28, 2015

Given the current limitations of the libpurple interfaces, this is not possible without digging into Pidgin or Finch. I have zero interest in doing anything which requires resources outside of libpurple. It really hinders the compatibility with other third-party clients.

The real issue is that there is no real self-message capability in libpurple, and this plugin has had to hack the functionality in. Maybe at some point in the future, the development version of libpurple will support such an interface.

@jgeboski jgeboski closed this Dec 28, 2015

@jgeboski jgeboski added the wontfix label Dec 28, 2015

@jgeboski

This comment has been minimized.

Show comment
Hide comment
@jgeboski

jgeboski Dec 28, 2015

Collaborator

As of 609d20c, self messages can now be disabled. This patch will appear in the next release.

Collaborator

jgeboski commented Dec 28, 2015

As of 609d20c, self messages can now be disabled. This patch will appear in the next release.

@Smile4ever

This comment has been minimized.

Show comment
Hide comment
@Smile4ever

Smile4ever Dec 29, 2015

What do you mean? Are they still displayed in the conversation window when they are disabled? Will the default resolve this bug?

Smile4ever commented Dec 29, 2015

What do you mean? Are they still displayed in the conversation window when they are disabled? Will the default resolve this bug?

@jgeboski

This comment has been minimized.

Show comment
Hide comment
@jgeboski

jgeboski Dec 29, 2015

Collaborator

Are they still displayed in the conversation window when they are disabled?

Nope. The functionality is disable completely.

Will the default resolve this bug?

Nope. By default, self messages are enabled. You will need to uncheck the box in the account settings.

Collaborator

jgeboski commented Dec 29, 2015

Are they still displayed in the conversation window when they are disabled?

Nope. The functionality is disable completely.

Will the default resolve this bug?

Nope. By default, self messages are enabled. You will need to uncheck the box in the account settings.

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