-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release #14
Comments
Hi @timeakesmarky, we're considering a couple of options. I'll get back to you once we decide on a solution. I appreciate your patience. |
Here you go: waReader 2.0 You'll find instructions on how to use it in the description of the release itself. If you're going to parse large files (>1 MB) please be patient, depending on your machine it might take a while to load. Please let me know if you find any issues or questions. |
@gariasf I'm getting a page not found error in these addresses.
|
You have to use You should also be able to use localhost:8080. |
I thought so. So, node wasn't in my windows path. I installed node and ran |
I tried all addresses including
|
Can you tell me which browser are you using? |
Chrome |
Can I see the hs output log in the console? |
|
Try using http-server@0.9.0
Install it and use it again. |
Works now. What was wrong? |
It looks like it has to do with the http-server dependencies causing an infinite redirect. It's not a waReader issue. |
@gariasf Hey, do you know how much of chats whatsapp exports in text format? |
According to official WhatsApp FAQ:
Anyway, 40k messages should be enough to cover most chats I believe. |
Yes, my exported chats have only around 37000 messages which is just about a month of chats, from August 1st week. That's too less, I want older chats. I guess there's no way to get those as txt. The only option would be obtaining msgstore.db. I also have this. Is there a way to convert it to whatsapp txt format? |
If you want to read msgstore.db you need the encryption key and extra data stored in a different file. I don't think there's any tool to export a "standard" .txt file from those sources. However, searching a bit I found this. It reads msgstore.db and uses wa.db along with the encryption key to read the messages. I don't have my phone rooted at the moment and I don't have any intention to, so I can't check if it works properly. |
Yes, I know about this. It works fine. My phone is old and rooted but I'm looking for txt parsers because I may change my phone and will need a non-root solution. I do have the key and the key file changes sometimes and I would fail to decrypt the crypt12 backups on my new phone. I found a solution here: Look at the answer. It's a paid chrome extension. |
That tool scraps the binary chat data from WhatsApp web socket connection. It requires internet connection. However I tested it and it works. If you're really interested in using the extension: You can get the downloaded source of the extension from your chrome extension folder (it's JavaScript after all so it's not compiled to anything unreadable), tweak the code to, say, avoid taking advantage of license validation and then install it in development mode to use it as your own. However as far as I've seen it doesn't export to txt files or databases. |
I checked it out, there's a checkLicense.js in its extension folder. I don't know what value to change, I'll trial and error. :D Yeah, html is fine too as long as I can read it. But why does it need google account? |
Because the license is tied to your google account when you buy the extension at the store. |
Can you please create a compiled release? :)
The text was updated successfully, but these errors were encountered: