Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (0)
to General by Kalatti - 17 hrs, 53 mins ago -
Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 2 days, 14 hrs ago -
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 3 days, 11 hrs ago - more...
 |
Fatalist |
2015-01-23
, 13:11
|
|
Posts: 141 |
Thanked: 190 times |
Joined on Feb 2012
@ Barcelona - Spain
|
#91
|
yonybe please read the 4 last pages of the thread. WhatsApp is blocking Yappari because it uses an older version of the protocol and these days they are blocking other non official clients like WhatsApp + too.
 |
|
2015-01-23
, 13:23
|
|
Posts: 1,023 |
Thanked: 4,421 times |
Joined on Feb 2010
@ Argentina
|
#92
|
Users that stills using whatsup 0.3.4 (with 1.2 protocol) has same issue.
You're not getting banned, you need to update protocol.
You're not getting banned, you need to update protocol.
| The Following 10 Users Say Thank You to CepiPerez For This Useful Post: | ||
 |
|
2015-01-23
, 14:17
|
|
Posts: 1,396 |
Thanked: 2,796 times |
Joined on Sep 2010
@ Caracas, Venezuela
|
#93
|
People is NOT BANNED since they are receiving the SMS with the Whatsapp Code when they try to register.
The protocol has been blocked. Actually it even surprises me that they took so long to block it, I thought they were gonna do it in early 2014.
The protocol has been blocked. Actually it even surprises me that they took so long to block it, I thought they were gonna do it in early 2014.
__________________
Support Yappari (a Whatsapp client for the N900 only) - Donate
Support Yappari (a Whatsapp client for the N900 only) - Donate
|
|
2015-01-23
, 14:30
|
|
Posts: 57 |
Thanked: 90 times |
Joined on Nov 2010
@ Bologna
|
#94
|
Arrives correctly msg to authenticate , but soon requests a new authentication
|
|
2015-01-23
, 14:38
|
|
Posts: 1,396 |
Thanked: 2,796 times |
Joined on Sep 2010
@ Caracas, Venezuela
|
#95
|
Originally Posted by incrys
That's because Yappari can't understand what's going on and asks you to re-register. That's all.
Arrives correctly msg to authenticate , but soon requests a new authentication
The only solution is that ceene uses the coderus implementation of 1.4 (or 1.5) since the projects are very similar. Even though coderus already did most of the work, it's still A LOT of work for Yappari.
ceene might just give up and buy another phone :P
__________________
Support Yappari (a Whatsapp client for the N900 only) - Donate
Support Yappari (a Whatsapp client for the N900 only) - Donate
|
|
2015-01-23
, 14:40
|
|
Posts: 395 |
Thanked: 255 times |
Joined on Nov 2010
|
#96
|
So, the big questions now are (for who may responses):
Yappari will be updated to the 1.4 or 1.5 protocol?
If so, how many time will take care?
It will be better take the Yowsup alternative? In time invested, i mean, update Yappari will be more difficult and take more time than port(?) Yowsup.
Or we just have to forget of whatsapp on the N900?
Grettings.
Yappari will be updated to the 1.4 or 1.5 protocol?
If so, how many time will take care?
It will be better take the Yowsup alternative? In time invested, i mean, update Yappari will be more difficult and take more time than port(?) Yowsup.
Or we just have to forget of whatsapp on the N900?
Grettings.
|
|
2015-01-23
, 14:51
|
|
Posts: 3 |
Thanked: 2 times |
Joined on Nov 2010
@ São Paulo, Brasil
|
#97
|
Is there the possibility that the new header parameters on v1.1.55 cause some new bad behavior after they "lift" this 24-hour ban thingie? I started getting "Reply: {"status":"fail","reason":"format_wrong"}" registration errors after updating to v1.1.55, while before they where always "bad_param"...
This is just for information's sake, I understand that the question is about using new protocol versions on Yappari, but if the "lift" comes in form of servers accepting protocol v1.2 once again (at least temporarily), wouldn't the recent changes become a burden?
...then again, it should be trivial to revert back to old behavior?.
This is just for information's sake, I understand that the question is about using new protocol versions on Yappari, but if the "lift" comes in form of servers accepting protocol v1.2 once again (at least temporarily), wouldn't the recent changes become a burden?
...then again, it should be trivial to revert back to old behavior?.
|
|
2015-01-23
, 14:55
|
|
Posts: 57 |
Thanked: 90 times |
Joined on Nov 2010
@ Bologna
|
#98
|
Ok, yappari it is died in 23-01-2015 :'(
 |
|
2015-01-23
, 15:10
|
|
Posts: 1,974 |
Thanked: 1,834 times |
Joined on Mar 2013
@ india
|
#99
|
I kinda get baffeld on these
For example pick any phone and you are able to call and sms and these im services are crazy like new phone new yet another non standerd service
For example pick any phone and you are able to call and sms and these im services are crazy like new phone new yet another non standerd service
| The Following User Says Thank You to nokiabot For This Useful Post: | ||
 |
|
2015-01-23
, 15:29
|
|
Posts: 6,436 |
Thanked: 12,699 times |
Joined on Nov 2011
@ Ängelholm, Sweden
|
#100
|
Originally Posted by Scorpius
Scorpius don't want to do a last fight for N900?
That's because Yappari can't understand what's going on and asks you to re-register. That's all.
The only solution is that ceene uses the coderus implementation of 1.4 (or 1.5) since the projects are very similar. Even though coderus already did most of the work, it's still A LOT of work for Yappari.
ceene might just give up and buy another phone :P
