maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Applications (https://talk.maemo.org/forumdisplay.php?f=41)
-   -   [M5] [Announce] Yappari - New maintainership and new features! (https://talk.maemo.org/showthread.php?t=94465)

Carlotic 2015-09-22 15:35

Re: [Announce] Yappari - New maintainership and new features!
 
Latest version works perfectly fine. No crashes since the update wich i did something like 9h ours ago its working absolutely fantastic.

xiskillo 2015-09-22 16:26

Re: [Announce] Yappari - New maintainership and new features!
 
Amazing news

Gracias Ceene

WilleWee 2015-09-22 19:06

Re: [Announce] Yappari - New maintainership and new features!
 
Still problem receiving messages?

enne30 2015-09-23 10:33

Re: [Announce] Yappari - New maintainership and new features!
 
Quote:

Originally Posted by WilleWee (Post 1483378)
Still problem receiving messages?

I think devs need some additional info... could you elaborate a bit more?

ceene 2015-09-23 15:33

Re: [Announce] Yappari - New maintainership and new features!
 
Well, hello everybody!

I'm very pleased to announce that latest version 2.0.21 is quite stable, probably more than ever.

This version may still get you banned if you try to create a new group. I haven't tested this. It may happen or luckily it may have been solved.

If you are willing to risk getting banned, you can try to create a new group and inform us of the result. We will all benefit from this information.



Special thanks, as always, to cepiperez, as he was the one to explain me why the stream:error (and subsequent disconnections) were happening.

I had no idea what was happening since the stream:error occurs only when not ack'ing a notification in the required time, so the logs were not very clear (at least to me, since I didn't knew what to look for).

In the meantime, lots of other things have happened since 2.0.16, which was the latest release I properly announced, so let's comment the full changelog since that release.

  • Process notification of types "encrypt", "features" to be able to ack them

This one, as commented above, is the fix that cepiperez informed me of. WA is now sending two new types of notifications that need to be acked. This fixes the great majority of disconnections, although I know they can still happen. There's still an underlying issue on the OS (probably QT) that I haven't been able to debug, but I believe it only happens on disconnection, and since it seems we've solved the random disconnections, we shouldn't suffer from this very much.


  • Don't send ourselves as participant of new group, that's redundant
  • Fix sendGetGroups xml message
  • Fix set group subject
  • Updated group creation code

All of these are trying to fix the ban on group creation, but I have NOT tested this, so that's the reason for the big red disclaimer.


  • Fix set initial config_ (will this force clients to send non crypted messages?)
  • Complete sendFeatures with 'identity' feature
  • Updated WA build hash
  • Set platform value to S40 (will force WA to send unencrypted messages? Let's hope so).

I found a couple things that weren't being sent rightfully (the S40 platform, for example). So with these fixes I try to be as similar as possible to the official S40 client. This may help us inform the servers that we don't support (yet) ciphered messages, and should always reduce the chance of us getting banned for using an unofficial client.


  • Speed up notification processing (type can only have one value)

And at least, a small optimization both on speed and computational power (battery!). It's probably non noticeable, but it's there, every little thing counts.



Well, it's been quite a journey these last 20 days. Not only all of these has happened, but as I commented earlier, I've also backported libaxolotl to QT4 coderus' QT5 libaxolotl alongside its required libraries. The backport is more of a hack than anything else, but it should get the job done.

Now, however, there's the job of implementing Textsecure into Yappari, for which a working libaxolotl is only the first step, so don't expect this soon, sorry :P

All in all, I hope you enjoy this release very much, and I ask you to kindly vote for it, so people who don't read the forums and don't want to use testing or devel repos can enjoy these release too.


This is quite important, as these people don't have a usable version of Yappari, since the last the reached extras repos is using the previous protocol.

WilleWee 2015-09-23 15:59

Re: [Announce] Yappari - New maintainership and new features!
 
Nice! Now there ain't the problem "**** is writing" but message never come. Everything works perfeclty now! Huge thanks for you guys!

ceene 2015-09-23 16:35

Re: [Announce] Yappari - New maintainership and new features!
 
Quote:

Originally Posted by WilleWee (Post 1483449)
Nice! Now there ain't the problem "**** is writing" but message never come. Everything works perfeclty now! Huge thanks for you guys!

I think this means we're succesfully notifying WA that we don't support encryption :)

enne30 2015-09-24 07:24

Re: [Announce] Yappari - New maintainership and new features!
 
Quote:

Originally Posted by ceene (Post 1483453)
I think this means we're succesfully notifying WA that we don't support encryption :)

So let's hope S40 version will never support encryption! :p

Fatalist 2015-09-24 15:57

Re: [Announce] Yappari - New maintainership and new features!
 
Version 2.0.21 seems more stable. I can see avatars of groups and receive messages from groups but still not from individual contacts.

Here's part of the log file (I replaced names and phone numbers with XXXXX):

OUTGOING:
<presence>
name=XXXXX

sendGetStatus(): Requesting status of 34XXXXX@s.whatsapp.net
OUTGOING:
<iq>
id=getstatus_2
to=s.whatsapp.net
type=get
xmlns=status
<status>
<user>
jid=34XXXXX@s.whatsapp.net

OUTGOING:
<iq>
id=get_groups_3
to=g.us
type=get
xmlns=w:g2
<participating>
type=list

INCOMING:
<ib>
from=s.whatsapp.net
<dirty>
timestamp=1443109488
type=groups

INCOMING:
<message>
from=34XXXXX@s.whatsapp.net
id=1442869615-1447
notify=XXXXX
offline=3
t=1443098811
type=text
<enc>
type=msg
v=1
3
!•M^ÀÌ1Èþ…Ùoìèà *¤ÛŽOŠ3n¾ææôÞR*" +Íèä*Ân>¾0¥[ÃyqMÛ*KOwï©

parseMessageInitialTagAlreadyChecked
INCOMING:
<message>
from=34XXXXX@s.whatsapp.net
id=1442869615-1480
notify=XXXXX
offline=3
t=1443104074
type=text
<enc>
type=msg
v=1
3
!•M^ÀÌ1Èþ…Ùoìèà *¤ÛŽOŠ3n¾ææôÞR*" f‰—¼.{:Ö„WDr.@ž·ß|O;

parseMessageInitialTagAlreadyChecked
INCOMING:
<message>
from=34XXXXX@s.whatsapp.net
id=1442869615-1482
notify=XXXXX
offline=3
t=1443104083
type=text
<enc>
type=msg
v=1
3
!•M^ÀÌ1Èþ…Ùoìèà *¤ÛŽOŠ3n¾ææôÞR*" ÷Æû›

parseMessageInitialTagAlreadyChecked
INCOMING:
<message>
from=34XXXXX@s.whatsapp.net
id=1442869615-1496
notify=XXXXX
offline=3
t=1443106803
type=text
<enc>
type=msg
v=1
3
!•M^ÀÌ1Èþ…Ùoìèà *¤ÛŽOŠ3n¾ææôÞR*" }?¬lõ”Â*¤Ã*‡•¿ÿ+ à ;]@Øu‘

parseMessageInitialTagAlreadyChecked
INCOMING:
<ib>
from=s.whatsapp.net
<offline>
count=4

INCOMING:
<iq>
from=s.whatsapp.net
id=config_1
type=result

INCOMING:
<presence>
from=34XXXXX@s.whatsapp.net

INCOMING:
<iq>
from=s.whatsapp.net
id=getstatus_2
type=result
<status>
<user>
jid=34XXXXX@s.whatsapp.net
t=1443084215
I am using Yappari!

Updating contact 34XXXXX@s.whatsapp.net
INCOMING:
<presence>
from=34XXXXX@s.whatsapp.net
last=1443109469
type=unavailable

Updating contact 34XXXXX@s.whatsapp.net
Updating contact 34XXXXX@s.whatsapp.net
INCOMING:
<iq>
from=g.us
id=get_groups_3
type=result
<groups>
<group>
id=34XXXXX-1357827317
<group>
id=34XXXXX-1333275050
<group>
id=34XXXXX-1401183152
<group>
id=34XXXXX-1411372085
<group>
id=34XXXXX-1415458390
<group>
id=34XXXXX-1423832623

thexmaster 2015-09-27 12:35

Re: [Announce] Yappari - New maintainership and new features!
 
Hello!
Same problem here. App is very stable. I can receive messages from groups, pictures from a single contact but no text messages.

Greetings from Austria
Stefan


All times are GMT. The time now is 03:48.

vBulletin® Version 3.8.8