This is a great question. I share the standpoint throughout (including privacy, and forced updates), and I very much doubt they are going to release new versions of their API to improve privacy without some strong external incentives.
My potential concerns with these are:
1. The API isn't necessarily backwards compatible. In fact, from a development standpoint, the expiry time in every release allows them to only have to maintain versions of their API until the oldest active official one, then they can simply remove it. So, even if they haven't introduced BC breaks in the API, that doesn't mean they won't.
2. There is a blog post that suggest they do revamp their API from time-to-time, affecting non-official clients. Therefore, I suspect this strategy will only work for a fixed amount of time, before app starts sporadically crashing or you lose messages.
3. I did notice that WhatsApp import and use the c2dm libraries which are officially deprecated. I imagine they will remove support for this entirely at some point in the future, simply because they will have to unless some deal is reached.
I imagine it would be very possible to bypass it; since the logic is in the client. It must have knowledge of (a) the current date/time (which it also verifies to be relatively accurate, IIRC, so changing your devices clock might not work) and (b) the expiry timestamp. A quick hack of (b) to make it in 100 years should offer immediate relief.
You need xposed framework installed.
Xposed Framework APK
Modded APK
Launch ui in modules section framework. Disable Expired Check is tick (Default). Enable debug mode in app and check the logs from framework. forward the date beyond original date to test it.
ไม่มีความคิดเห็น