[Announce] Yappari - New maintainership and new features! - Page 131 - maemo.org

enne30 | # 1301 | 2016-01-31, 17:09 | Report

whatsapp encryption is becoming really a pain in the a**....

You should try to:
- close Yappari
- rm /home/user/.config/scorpius/yappari.log
- start Yappari
- have a chat with iphone contact
- close Yappari
- post log here (obfuscating phone numbers)

About loosing first message (my only issue atm), I extracted from logs what happens:

Code:

INCOMING:
<message>
   from=39328xxxxxxx-1449917322@g.us
   id=w5rE/i4sYEkG1
   notify=yyyyyyy
   participant=39320xxxxxxx@s.whatsapp.net
   t=1454255868
   type=text
<enc>
   type=skmsg
   v=2
   3Â€Ã‘Â§Ã™

parseMessageInitialTagAlreadyChecked
Encoded message from 39328xxxxxxx-1449917322@g.us
OUTGOING:
<receipt>
   id=w5rE/i4sYEkG1
   to=39328xxxxxxx-1449917322@g.us
   type=error
<error>
   type=plaintext-only

OUTGOING:
<receipt>
   id=w5rE/i4sYEkG1
   to=39320xxxxxxx@s.whatsapp.net
   type=error
<error>
   type=plaintext-only

INCOMING:
<chatstate>
   from=39328xxxxxxx-1449917322@g.us
   participant=39320xxxxxxx@s.whatsapp.net
<composing>

INCOMING:
<message>
   from=39328xxxxxxx-1449917322@g.us
   id=w5rE/i4sYEkG1
   notify=yyyyyyy
   participant=39320xxxxxxx@s.whatsapp.net
   t=1454255868
   type=text
<enc>
   type=pkmsg
   v=2
   3!qÃšÃ•sÃ€5Â*%Ã‚DÂ¾R8cMÃ¹7Ã•Ã*Â¤-ÂˆÂ»WÂŸÃ¸Â¿*E!Ã8OÂ¡EgÃªÃ¤aÃ*)qÂ…Ã–Ã™zÃž,Â¯ÃšÃ…Ã„Â´%Â–ÂšnÂš"Â³3
!Â†)Ã•AÃªÂžÂ£uÂÂ‹"+Ã…Â’Â»Ã§Â®aÂ’uÂ¥Âˆ2EÃ«*(*

parseMessageInitialTagAlreadyChecked
Encoded message from 39328xxxxxxx-1449917322@g.us
OUTGOING:
<receipt>
   id=w5rE/i4sYEkG1
   to=39328xxxxxxx-1449917322@g.us
   type=error
<error>
   type=plaintext-only

OUTGOING:
<receipt>
   id=w5rE/i4sYEkG1
   to=39320xxxxxxx@s.whatsapp.net
   type=error
<error>
   type=plaintext-only

INCOMING:
<chatstate>
   from=39328xxxxxxx-1449917322@g.us
   participant=39320xxxxxxx@s.whatsapp.net
<composing>

INCOMING:
<chatstate>
   from=39328xxxxxxx-1449917322@g.us
   participant=39320xxxxxxx@s.whatsapp.net
<composing>

INCOMING:
<chatstate>
   from=39328xxxxxxx-1449917322@g.us
   participant=39320xxxxxxx@s.whatsapp.net
<composing>

INCOMING:
<message>
   from=39328xxxxxxx-1449917322@g.us
   id=w5rE/i4sYEkG2
   notify=yyyyyyy
   participant=39320xxxxxxx@s.whatsapp.net
   t=1454255901
   type=text
<body>
   Solo che purtroppo le ÃƒÂ¨ capitato in piccolo Fincidente...

parseMessageInitialTagAlreadyChecked
OUTGOING:
<receipt>
   id=w5rE/i4sYEkG2
   participant=39320xxxxxxx@s.whatsapp.net
   to=39328xxxxxxx-1449917322@g.us

For unknown reason, first encoded message (w5rE/i4sYEkG1) was sent encoded second time too, even after two error receipts;
then second message came plain text, but first one was lost...
I don't know if inverting error receipts order (user first, then group) may help on first message....

The Following 3 Users Say Thank You to enne30 For This Useful Post:
ceene, Fatalist, newone2

ceene | # 1302 | 2016-01-31, 18:02 | Report

Originally Posted by enne30 View Post

For unknown reason, first encoded message (w5rE/i4sYEkG1) was sent encoded second time too, even after two error receipts;
then second message came plain text, but first one was lost...
I don't know if inverting error receipts order (user first, then group) may help on first message....

The thing is, I believe the error receipt sent to the group doesn't do anything at all, but it also seemed not to do anything harmful. Maybe I can remove it altogether and test again, but I don't imagine it will be any better.

The Following 2 Users Say Thank You to ceene For This Useful Post:
enne30, newone2

CepiPerez | # 1303 | 2016-01-31, 21:18 | Report

@ceene:
Try adding participant to receipt, or send it directly to participant. I can't test it right now but maybe it works

The Following 4 Users Say Thank You to CepiPerez For This Useful Post:
ceene, enne30, Fatalist, sicelo

ceene | # 1304 | 2016-01-31, 21:35 | Report

Originally Posted by CepiPerez View Post

@ceene:
Try adding participant to receipt, or send it directly to participant. I can't test it right now but maybe it works

Yep, that's what I do now. If you look at enne30 log, for each encrypted message received on a group I send this, so that's one plaintext-only sent to the group itself and another sent to the participant that sent the encrypted message.

I don't know if you're maybe suggesting something different I didn't understand, though. Thanks anyhow!

Code:

OUTGOING:
<receipt>
   id=w5rE/i4sYEkG1
   to=39328xxxxxxx-1449917322@g.us
   type=error
<error>
   type=plaintext-only

OUTGOING:
<receipt>
   id=w5rE/i4sYEkG1
   to=39320xxxxxxx@s.whatsapp.net
   type=error
<error>
   type=plaintext-only

The Following 2 Users Say Thank You to ceene For This Useful Post:
enne30, newone2

CepiPerez | # 1305 | 2016-01-31, 22:01 | Report

to=232323-453545@g.us
participant=676767@whatsapp.net

But I'm just guessing...

The Following 3 Users Say Thank You to CepiPerez For This Useful Post:
ceene, enne30, sicelo

enne30 | # 1306 | 2016-01-31, 22:15 | Report

@cepiperez: the way ceene sends notifications seems to work always but occasionally the very first message won't return plain text

Also I cannot understand why first encrypted message (w5rE/i4sYEkG1) seems to be different the second time it has been received

mykle187 | # 1307 | 2016-02-02, 08:20 | Report

i have downloaded the new yappari but whenever i try and register it, it keeps saying unable to connect to registration server

what can i do to resolve this issue

enne30 | # 1308 | 2016-02-02, 11:40 | Report

Originally Posted by mykle187 View Post

i have downloaded the new yappari but whenever i try and register it, it keeps saying unable to connect to registration server

what can i do to resolve this issue

please post your exact yappari version ("about" in main menu) and log file from /home/user/.config/scorpius/yappari.log

About my issue I'm quite sure after sometime some contacts "forget" we cannot receieve encrypted message, so their first encrypted message in group gets lost (message received after error notification are ok):

Code:

INCOMING:
<chatstate>
   from=39320xxxxxxx-1435563407@g.us
   participant=39320xxxxxxx@s.whatsapp.net
<composing>

INCOMING:
<chatstate>
   from=39320xxxxxxx-1435563407@g.us
   participant=39320xxxxxxx@s.whatsapp.net
<paused>

INCOMING:
<notification>
   from=s.whatsapp.net
   id=2801439201
   t=1454408645
   type=encrypt
<count>
   value=0

OUTGOING:
<ack>
   class=notification
   id=2801439201
   to=s.whatsapp.net
   type=encrypt

INCOMING:
<message>
   from=39320xxxxxxx-1435563407@g.us
   id=692D9B145472F35C480
   notify=yyyyyy
   participant=39320xxxxxxx@s.whatsapp.net
   t=1454408645
   type=text
<enc>
   type=skmsg
   v=2
   3Ã?Â¤Ã©Ã?Ã**ÃÂ¥
Ã©Â?{Â¸Â*9Ã¤Â?^Ã?Â?Â»U{Â¨Â¿Â*Â´Ã?Â?;ÃÂºO}Â¬Â?Â³Âª?Â?m
Ã?Ã¶Ã¦zÃ¹Â?'CÃ»S$Ã?e]DÃcÃ¹Ã?Â?Ã?bÂ¹k`

parseMessageInitialTagAlreadyChecked
Encoded message from 39320xxxxxxx-1435563407@g.us
OUTGOING:
<receipt>
   id=692D9B145472F35C480
   to=39320xxxxxxx-1435563407@g.us
   type=error
<error>
   type=plaintext-only

OUTGOING:
<receipt>
   id=692D9B145472F35C480
   to=39320xxxxxxx@s.whatsapp.net
   type=error
<error>
   type=plaintext-only

INCOMING:
<chatstate>
   from=39320xxxxxxx-1435563407@g.us
   participant=39320xxxxxxx@s.whatsapp.net
<composing>

INCOMING:
<message>
   from=39320xxxxxxx-1435563407@g.us
   id=692D9B145472F35C481
   notify=yyyyyy
   participant=39320xxxxxxx@s.whatsapp.net
   t=1454408684
   type=text
<body>
   .

parseMessageInitialTagAlreadyChecked
OUTGOING:
<receipt>
   id=692D9B145472F35C481
   participant=39320xxxxxxx@s.whatsapp.net
   to=39320xxxxxxx-1435563407@g.us

Probably there is no way to overcome this issue without implementing encryption

The Following 2 Users Say Thank You to enne30 For This Useful Post:
ceene, newone2

tantoniazi | # 1309 | 2016-02-02, 13:29 | Report

Good day
my yappari 2.0.24 dont register...

HttpRequestv2() Socket Error 1 The remote host closed the connection
reg/req/register/start
Request: https://v.whatsapp.net/v2/register?c...75&code=667049
HttpRequest(): Connecting to v.whatsapp.net:443
HttpRequest(): Sending request...
HttpRequest(): Waiting for response...
HttpRequest(): Got response
H
HttpRequestv2() Socket Error 1 The remote host closed the connection
Network deactivated: b0dd6379-ea3c-416f-a0eb-2142ae586e02
Network connection changed: Offline
updateTimeStamps()
Resetting timestamps at 1454378400221
Next run in 86399779

tantoniazi | # 1310 | 2016-02-02, 13:47 | Report

hello I am having trouble registering also

HttpRequestv2() Socket Error 1 The remote host closed the connection
reg/req/register/start
Request: https://v.whatsapp.net/v2/register?c...75&code=667049
HttpRequest(): Connecting to v.whatsapp.net:443
HttpRequest(): Sending request...
HttpRequest(): Waiting for response...
HttpRequest(): Got response
H
HttpRequestv2() Socket Error 1 The remote host closed the connection
Network deactivated: b0dd6379-ea3c-416f-a0eb-2142ae586e02
Network connection changed: Offline
updateTimeStamps()
Resetting timestamps at 1454378400221
Next run in 86399779