|
Re: [Announce] Yappari - New maintainership and new features!
ok...registered using friend's mobile.then he registered his number...then i logged in yappari. no registration asked...came for 30 seconds...went to background. status showed disconnected. what next?i think im not banned.
|
Re: [Announce] Yappari - New maintainership and new features!
i received messages as usual in his mobile. but in yappari nothing.
|
Re: [Announce] Yappari - New maintainership and new features!
Yappari 2.0.16 Build 5217
Yappari console debug start Reading roster DB... Roster retrieved in 435 milliseconds. Resetting timestamps at 1441339260104 Next run in 52139896 Reading open chats DB... Open Chats retrieved in 3 milliseconds. Entry retrieved: 91-1379508434@g.us Entry retrieved: 918@s.whatsapp.net Entry retrieved: 96@s.whatsapp.net Entry retrieved: 91@s.whatsapp.net Entry retrieved: 91@s.whatsapp.net Entry retrieved: 919@s.whatsapp.net Entry retrieved: 91@s.whatsapp.net Entry retrieved: 9@s.whatsapp.net Entry retrieved: 91@s.whatsapp.net Network connection changed: Online Current active connection: b8c53e46-2b7f-4296-a082-7f336ca84a8c Connecting to c.whatsapp.net:443... Connected successfully OUTGOING: <stream:features> <groups_v2> <presence> <privacy> <readreceipts> OUTGOING: <auth> mechanism=WAUTH-2 passive=false user=919496092168 INCOMING: <stream:start> from=s.whatsapp.net INCOMING: <stream:features> INCOMING: <challenge> Content of type challenge length: 20 OUTGOING: <response> Content of type response length: 46 There was an IO error: Connection closed by server. Connection closed. Stopping timers. Freeing up the connection. Freeing up the socket. Yappari will retry the connection in 10 seconds. Yappari 2.0.16 Build 5217 Yappari console debug start Reading roster DB... Roster retrieved in 531 milliseconds. Resetting timestamps at 1441339286315 Next run in 52113685 Reading open chats DB... Open Chats retrieved in 4 milliseconds. Entry retrieved: 91-1379508434@g.us Entry retrieved: 918@s.whatsapp.net Entry retrieved: 96.@s.whatsapp.net Entry retrieved: 919@s.whatsapp.net Entry retrieved: 919@s.whatsapp.net Entry retrieved: 919@s.whatsapp.net Entry retrieved: 919@s.whatsapp.net Entry retrieved: 9197@s.whatsapp.net Entry retrieved: 91828@s.whatsapp.net Network connection changed: Online Current active connection: b8c53e46-2b7f-4296-a082-7f336ca84a8c Connecting to c.whatsapp.net:443... Connected successfully OUTGOING: <stream:features> <groups_v2> <presence> <privacy> <readreceipts> OUTGOING: <auth> mechanism=WAUTH-2 passive=false user=919496092168 INCOMING: <stream:start> from=s.whatsapp.net INCOMING: <stream:features> INCOMING: <challenge> Content of type challenge length: 20 OUTGOING: <response> Content of type response length: 46 There was an IO error: Connection closed by server. Connection closed. Stopping timers. Freeing up the connection. Freeing up the socket. Yappari will retry the connection in 10 seconds. Yappari 2.0.16 Build 5217 Yappari console debug start Reading roster DB... Roster retrieved in 435 milliseconds. Resetting timestamps at 1441339307881 Next run in 52092119 Reading open chats DB... Open Chats retrieved in 4 milliseconds. Entry retrieved: 91-1379508434@g.us Entry retrieved: 9182@s.whatsapp.net Entry retrieved: 9659@s.whatsapp.net Entry retrieved: 919@s.whatsapp.net Entry retrieved: 919473@s.whatsapp.net Entry retrieved: 919573@s.whatsapp.net Entry retrieved: 919992@s.whatsapp.net Entry retrieved: 9197443@s.whatsapp.net Entry retrieved: 9182@s.whatsapp.net Network connection changed: Offline User has quit the application Application destroyed |
Re: [Announce] Yappari - New maintainership and new features!
You are playing a "dangerous" game using one number on two devices back and forth.
It does look like you're not banned yet. I would say delete the whole /home/user/.yappari directory, and also /home/user/.config/scorpius. Re-register and see what happens. Do not keep moving the number/SIM across the two devices. One more thing: your friends/contacts will appreciate it if you obscure their numbers :) before submitting your post, maybe replace them with XXXXX like others have done? We're not bad people, but this is a public forum that even gets crawled by Google, etc. |
Re: [Announce] Yappari - New maintainership and new features!
Quote:
|
Re: [Announce] Yappari - New maintainership and new features!
1 Attachment(s)
maybe crash problems are related someway to delivery notifications...
ceene take a look to log attached.. |
Re: [Announce] Yappari - New maintainership and new features!
1. cant see group profile icons. shows blue icons for all. but for individual contacts it shows images.
2. if i click new message notifications, it closes. gotta open yappari to view. 3.in background i think yappari doesnt work. when i open it, shows, connecting then logged in. |
Re: [Announce] Yappari - New maintainership and new features!
can we not send images and files through yappari? i can receive files though...
|
Re: [Announce] Yappari - New maintainership and new features!
Hi there,
I'm unable to receive private messages as already discussed in this thread earlier. According to the log file below yappari receive the incoming message but it do not show it on screen for some reason. My friend received my messages, I can see that he is typing but his reply isn't shown in yappari. It is same with yappari 2.0.15 and 2.0.16. I deleted .yappari and .config/scorpius but it didn't help. Did anyone who went through the same managed to solve this problem? Thanks ;) Code:
Message ID 1441392409-4 |
Re: [Announce] Yappari - New maintainership and new features!
Hi there,
I'm unable to receive private messages as already discussed in this thread earlier. According to the log file below yappari receive the incoming message but it do not show it on screen for some reason. My friend received my messages, I can see that he is typing but his reply isn't shown in yappari. It is same with yappari 2.0.15 and 2.0.16. I deleted .yappari and .config/scorpius but it didn't help. Did anyone who went through the same managed to solve this problem? Thanks ;) Code:
Message ID 1441392409-4 |
Re: [Announce] Yappari - New maintainership and new features!
1 Attachment(s)
since yesterday seems Yappari is crashing systematically :(
When not crashing I see "Connection closed by server" in main window.. To give you the best information I did the following: - delete log - start Yappari - leave main window open (no user input, no chats opened, no incoming messages) After a couple of minutes yappari crashed (main window closed) Entire log since opening yappari is attached (about 200 lines) hope it helps.. |
Re: [Announce] Yappari - New maintainership and new features!
Group messages work on last version, normal messages still being sent but not received except for media which is working fine.
|
Re: [Announce] Yappari - New maintainership and new features!
Quote:
|
Re: [Announce] Yappari - New maintainership and new features!
The thing about not receiving messages... is very very strange. The logs you sent simply indicate that no data is arriving to the phone, so Yappari can't of course show what it doesn't receive... I don't think it's Yappari's fault,as the logs simply indicate... nothing at all. :/
|
Re: [Announce] Yappari - New maintainership and new features!
Quote:
I'll provide my log as soon as I get home, with encrypted replies from my friend that wasn't displayed on screen. |
Re: [Announce] Yappari - New maintainership and new features!
also I have the same problem... :(
|
Re: [Announce] Yappari - New maintainership and new features!
I wonder if Whatapp have new magic against un-authorised clients?
Is there anyone who IS able to receive messages? |
Re: [Announce] Yappari - New maintainership and new features!
Quote:
|
Re: [Announce] Yappari - New maintainership and new features!
1 Attachment(s)
There is an example of incoming message that was received by yappari (if I understand the log file correctly) but it wasn't shown on screen.
A part of the log that seemed relevant to me is attached. Code:
INCOMING: |
Re: [Announce] Yappari - New maintainership and new features!
1 Attachment(s)
Quote:
A part of the log that seemed relevant to me is attached. Code:
INCOMING: |
Re: [Announce] Yappari - New maintainership and new features!
Here working fine.
Don't know if have to be something with the ghost contact or cause i'm on wifi or who knows. Greetings. |
Re: [Announce] Yappari - New maintainership and new features!
Just tested and a plain text message works fine, both receiving and sending.
I wonder Wotsup :-) ??? |
Re: [Announce] Yappari - New maintainership and new features!
Quote:
That's something doable, I guess, but I don't know the cypher nor how are the keys created and shared, etc... If anyone knows I can take a look at how much would take the implementation of this. |
Re: [Announce] Yappari - New maintainership and new features!
Quote:
|
Re: [Announce] Yappari - New maintainership and new features!
Quote:
Code:
void Connection::parseMessageInitialTagAlreadyChecked(ProtocolTreeNode& messageNode) |
Re: [Announce] Yappari - New maintainership and new features!
why do some clients send encrypted messages? whatsapp introduced encryption in latest versions?
|
Re: [Announce] Yappari - New maintainership and new features!
From Wikip.:"As of August 15, 2012, the WhatsApp support staff claim messages are encrypted in the "latest version" of the WhatsApp software for iOS and Android (but not BlackBerry, Windows Phone, and Symbian), without specifying the implemented cryptographic method."
How then, do BB, WP and Symbian devices read the encryption? |
Re: [Announce] Yappari - New maintainership and new features!
Quote:
Messages might be AES256 encrypted. If I have a spare time, I'll try to dig for an key from my android phone. If the key is generated per user and not per device, I could be able to decrypt messages using this key. It is strange that messages are sent in plain text to some users and encrypted to others even if they use the same client (Yappari of course :) ) |
Re: [Announce] Yappari - New maintainership and new features!
Quote:
|
Re: [Announce] Yappari - New maintainership and new features!
My test message was sent to me by an iPhone 5, and it may not have been upgraded I guess.
Clearly a number of users ARE not receiving messages but from what we have read, they should seek out a contact using older h/w or a BB, WP and Symbian and test a message from that source. |
Re: [Announce] Yappari - New maintainership and new features!
Encryption system is TextSecure, relying on libaxolotl.
This library seems to have been ported to QT by CODeRUS (see https://github.com/CODeRUS/libaxolotl), although I don't know if it's well tested and working. First step would be creating a .deb for Maemo, and then start coding the needed changes to Yappari. It seems doable given enough time. |
Re: [Announce] Yappari - New maintainership and new features!
Hi all!,
I'm having problems with the 2.0.16 version, because I'm not getting any messages sent by my contacts, I see "someone is typing" but did not get anything, any help? |
Re: [Announce] Yappari - New maintainership and new features!
Quote:
You can perhaps help: those contacts you get nothing from, do you know what devices (iPhone, Android etc) they are using, and if you know anyone with a Blackberry or Symbian device, can you receive messages from them? |
Re: [Announce] Yappari - New maintainership and new features!
Quote:
Greetings. |
Re: [Announce] Yappari - New maintainership and new features!
Quite weird, why some of us get iPhone, Android messages but others apparently not. If Whatsapp have differentially implemented encryption on the app based on platform, the server must choose between encrypted or not based on handshake (as apeman noted). And all instances of Yappari behave the same as far as the server is concerned.
Have those having trouble been banned earlier and then got themselves unbanned perhaps? Shot in the dark... |
Re: [Announce] Yappari - New maintainership and new features!
According to my yappari.log and yappari source code(see line 1241 in connection.cpp) yappari identifies itself as platform=none
Code:
OUTGOING:(My opinion is based on WHAnonymous PHP WhatsApp client documentation) Changing line 1241 in connection.cpp from Code:
sendClientConfig("none");Code:
sendClientConfig("S40"); |
Re: [Announce] Yappari - New maintainership and new features!
I would give it a try but I do not know how to create a deb package for maemo.
I cloned the source code, I can make the change but I don't know how to build/package it. Is there any tutorial available, how to build the deb package and how to setup a build toolchain? Do you use Qt SDK to open yappari project? What version? |
Re: [Announce] Yappari - New maintainership and new features!
Weird thing is that we all should be hit by this, as I imagine most of us are in comms with iPhone/Android users, right?
Look at this log file snippet relating to a message I received: Code:
INCOMING:And I am puzzled: I thought the method of Yappari evading detection as un-authorised software was by presenting itself as a symbian app. |
Re: [Announce] Yappari - New maintainership and new features!
Quote:
So changing "platform" value to "S40" might not help but I'd like to give it a try anyway.. |
Re: [Announce] Yappari - New maintainership and new features!
Quote:
Thanks a lot! |
| All times are GMT. The time now is 13:28. |
vBulletin® Version 3.8.8