Bug #4161
Messages to Google users from non Google users silently fail
| Status: | New | Start date: | 11/27/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | Backlog | |||
| Component: |
Description
Recipient is using hangouts and chatsecure. By default messages from sender (me) xmpp client are directed to the hangouts/messaging presence and not chatsecure. Can receieve messages from google user.
I'm not sure if this can be solved on your end, but the ability to select a presence like in Jitsi might work.
History
#1 Updated by n8fr8 over 2 years ago
- Target version set to v14.2 bug fix update!
#2 Updated by n8fr8 over 2 years ago
- Target version changed from v14.2 bug fix update! to Backlog
#3 Updated by axel about 2 years ago
Another solution is to use the name of the resources that are specific to Hangouts (the two I've seen so far are Messaging[A-Za-z0-9]{9} and messaging-lcsw_hangouts[A-Z0-9]{8}) to avoid sending messages to these specific resources, as we know they are Hangouts and just won't deliver them to the user.
At this point in time, any Hangouts XMPP resource is actually equivalent to a user not being available. I would almost argue we could not show a user as connected if they are only connected through Hangouts (ie, one of the two resources described above) as it functionally equivalent to not being online, nor offline with offline-delivery capacity.