Reading Whatsapp messsages without blue ticks

Many of you have probably encountered this scenario: you received a message that you so desperately want to read, yet you do not want to let the sender know that you have read it, and you do not want to disable the read receipt (blue tick) functionality of Whatsapp off either.

So you go on the internet to search for the way to do it, and most of the pages you discovered mention tricks that do not work anymore and all these searching and reading just fuel your curiosity even more.

And you come across this page, at the time of writing 13/01/2018, this page provides the verified working way to read that message without blue tick, so read on

Requirement:


  • Mobile phone with wifi connected and Airplane Mode function
  • Computer capable of opening whatsapp web
  • Optionally firewall capable blocking all network connection installed in the computer

Procedure:

  1. Open Whatsapp in your mobile phone
  2. Ensure the chat message that you want to "peek" is not in Archive
  3. Open web Whatsapp: https://web.whatsapp.com/
  4. Go to Web Whatsapp in your mobile phone and follow the instruction there
  5. Scan the code in web Whatsapp using your phone.
  6. Let it establish web Whatsapp in the browser and the phone, give it few seconds to load all the messages.
  7. Turn on Airplane Mode in the mobile phone
  8. Turn on firewall in the computer and block all network connection, alternatively just pull the network plug or disable wifi
  9. Select the message you want to read, it should be displayed fully in your Web Whatsapp
  10. Close the Web Whatsapp once you have finished reading it
  11. Restore your network connection or plug back your network cable or enable wifi
  12. Turn off Airplane Mode in the mobile phone
  13. Verify that the message is still marked as unread in the Whatsapp of the mobile phone

Tips:


  • Web Whatsapp only loads recent messages, meaning if you are trying to read old unread messages, it probably won't show up using the above trick
  • In order to read old unread messages, you will need to trick the Whatsapp into thinking that the message is now, simply by changing your phone system date and time to the day the old unread message is received before executing the above trick, should do the trick

Comments

Post a Comment

Popular posts from this blog

Image
Implementing gRPC Using Spring Boot and Gradle Background GRPC (gRPC) is a RPC framework pioneered by google later on made public and open source. GRPC has not been officially supported by Spring Framework, so far there are few community libraries that can work seamlessly with Spring Boot. In this article, I will use the lognet's grpc-spring-boot-starter. Project Structure Ideally, the proto files for gRPC is located in another directory, which will then be accessed by the gradle plugin to auto generate the required files.   Gradle Script The heart of gRPC enablement lies on the grpc boot starter, which includes few other tasks outlined as below. https://github.com/overtakerx/grpcbootdemo/blob/main/build.gradle Few important note: first you have to run gradlew compileJava for the auto generation to generate the files from the proto file, then you will need to rebuild the project for Intellij to recognise the auto-generated files. Full demo: https://github.com/overtakerx/grpcbootdem
Read more

Spring Boot 2: Parallelism with Spring WebFlux

Image
Spring Boot 2: Parallelism with Spring WebFlux Parallelism is rather unusual in Spring application, however when we encounter the need of HITLOL (HIgh Throughput LOw Latency), we need ways to make async calls. With Spring Boot 1, in high level definition, we can declare async on all the functions that are meant to be parallel and return Futures from there. Here is more detailed info:  https://medium.com/sipios/how-to-make-parallel-calls-in-java-springboot-application-and-how-to-test-them-dcc27318a0cf For Spring Boot 2, we shall employ Spring WebFlux libraries to accomplish parallelism. Mainly focused on functions: Mono.zipDelayError(), Mono.subscribeOn() and Mono.onErrorResume() The main function that drives the parallelism is zipDelayError(), the purpose of zipDelayError() as supposed to using zip() is to enable the other Monos to run to completion even if one Mono failed. AllDtos allDtos = Mono. zipDelayError (Arrays. asList (firstDto , secondDto , (Mono&l
Read more

Spring Boot Reactive API Part 2

Image
 Spring Boot Reactive: Improving CPU bound performance using Scheduler In part 1 , we have seen that Spring Boot Reactive doesn't really improve performance if the WAITING time is CPU bound / CPU intensive tasks. This article show a quick way on how we can improve the speed through specific configuration Setup Spring Boot's embedded Tomcat is reconfigured to only use 10 worker threads, this way we can clearly see the performance limitation and tweaks. Gatling is configured to simulate 30 concurrent requests with 30000 milliseconds request timeout. APIs internal process is calling java native code that calculate the value of PI over 1 million iterations Default / No scheduler The main reason why CPU bound tasks do not improve (or even degrade) with high parallelism is because of the costly overhead for context switching in the low level. In the scenario below, 10 main threads are all being used to calculate PI values and because there are less CPU than threads, a lot of context
Read more