#1176 closed defect

First message in a brand-new chat — at Initial Version

Reported by: fozzy@… Owned by: Miklos Vajna
Priority: normal Milestone:
Component: Skype Version: 3.2.2
Keywords: dbus, first message Cc:
IRC client+version: Client-independent Operating System: Linux
OS version/distro:

Description

Versions of Skype higher (and maybe lower) than 4.0.0.8 might not be sending first messages in a brand-new chat to bitlbee (i.e. when someone contacts you for the first time since client start). Skype just doesn't forward notifications about these to dbus for some reason.

For now clients < 4.3 cannot login, and it's time to fix this bug I think.

For a brand new chat with other user, first message look's like this:

CHAT #fozzy_bot/$fozzy_inside;3affbef0fa6e58a1 NAME #fozzy_bot/$fozzy_inside;3affbef0fa6e58a1
CHAT #fozzy_bot/$fozzy_inside;3affbef0fa6e58a1 STATUS DIALOG
CHAT #fozzy_bot/$fozzy_inside;3affbef0fa6e58a1 STATUS DIALOG
CHAT #fozzy_bot/$fozzy_inside;3affbef0fa6e58a1 DIALOG_PARTNER fozzy_bot
CHATMEMBER 99215 ROLE USER
CHAT #fozzy_bot/$fozzy_inside;3affbef0fa6e58a1 MYROLE USER
CHAT #fozzy_bot/$fozzy_inside;3affbef0fa6e58a1 MEMBERS fozzy_bot fozzy_inside
CHAT #fozzy_bot/$fozzy_inside;3affbef0fa6e58a1 FRIENDLYNAME Bender Bot
CHAT #fozzy_bot/$fozzy_inside;3affbef0fa6e58a1 ACTIVEMEMBERS fozzy_bot fozzy_inside
CHAT #fozzy_bot/$fozzy_inside;3affbef0fa6e58a1 TIMESTAMP 1407922908
CHAT #fozzy_bot/$fozzy_inside;3affbef0fa6e58a1 ADDER fozzy_bot
CHAT #fozzy_bot/$fozzy_inside;3affbef0fa6e58a1 STATUS DIALOG
CHAT #fozzy_bot/$fozzy_inside;3affbef0fa6e58a1 POSTERS fozzy_bot
CHAT #fozzy_bot/$fozzy_inside;3affbef0fa6e58a1 ACTIVITY_TIMESTAMP 1407922911

and has no

CHATMESSAGE <id> BODY <string>

But we can receive last messages like this:

GET CHAT #fozzy_bot/$fozzy_inside;3affbef0fa6e58a1 CHATMESSAGES
CHAT #fozzy_bot/$fozzy_inside;3affbef0fa6e58a1 CHATMESSAGES 100201
GET CHATMESSAGE 100201 BODY
CHATMESSAGE 100201 BODY first message test

Question is how to detect if need to send GET CHAT x CHATMESSAGES or not?

Change History (0)

Note: See TracTickets for help on using tickets.