Skip to content
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

Closed
timea-techgirl opened this issue Aug 26, 2019 · 21 comments
Closed

Release #14

timea-techgirl opened this issue Aug 26, 2019 · 21 comments

Comments

@timea-techgirl
Copy link

Can you please create a compiled release? :)

@gariasf
Copy link
Member

gariasf commented Aug 26, 2019

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.

@gariasf
Copy link
Member

gariasf commented Sep 8, 2019

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 gariasf closed this as completed Sep 8, 2019
@timea-techgirl
Copy link
Author

@gariasf I'm getting a page not found error in these addresses.

D:\node-v10.5.0-win-x64>hs
Starting up http-server, serving ./
Available on:
  http://192.168.56.1:8080
  http://192.168.224.1:8080
  http://192.168.27.2:8080
  http://192.168.1.104:8080
  http://127.0.0.1:8080
Hit CTRL-C to stop the server

@gariasf
Copy link
Member

gariasf commented Sep 8, 2019

You have to use hs where you extracted the zip file. Such a folder should have these files. If you extracted the zip at /home/user/xxx/waReader then hs needs to be called in /home/user/xxx/waReader.

You should also be able to use localhost:8080.

@timea-techgirl
Copy link
Author

I thought so. So, node wasn't in my windows path. I installed node and ran hs from wareader folder now but still the same problem.

@timea-techgirl
Copy link
Author

timea-techgirl commented Sep 8, 2019

I tried all addresses including localhost:8080:

C:\Users\Timea\Desktop\waReader2.0>hs
Starting up http-server, serving ./
Available on:
  http://192.168.56.1:8080
  http://192.168.224.1:8080
  http://192.168.27.2:8080
  http://192.168.1.104:8080
  http://127.0.0.1:8080
Hit CTRL-C to stop the server

@gariasf
Copy link
Member

gariasf commented Sep 8, 2019

Can you tell me which browser are you using?

@timea-techgirl
Copy link
Author

Chrome

@gariasf
Copy link
Member

gariasf commented Sep 8, 2019

Can I see the hs output log in the console?

@timea-techgirl
Copy link
Author

[Sun Sep 08 2019] "GET /" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.87 Safari/537.36"
[Sun Sep 08 2019] "GET /" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.87 Safari/537.36"
[Sun Sep 08 2019] "GET /" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.87 Safari/537.36"
[Sun Sep 08 2019] "GET /" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.87 Safari/537.36"

@gariasf
Copy link
Member

gariasf commented Sep 8, 2019

Try using http-server@0.9.0

npm install -g http-server@0.9.0

Install it and use it again.

@timea-techgirl
Copy link
Author

Works now. What was wrong?

@gariasf
Copy link
Member

gariasf commented Sep 8, 2019

It looks like it has to do with the http-server dependencies causing an infinite redirect. It's not a waReader issue.
For now downgrading the library fixes the problem.

@timea-techgirl
Copy link
Author

@gariasf Hey, do you know how much of chats whatsapp exports in text format?

@gariasf
Copy link
Member

gariasf commented Sep 11, 2019

According to official WhatsApp FAQ:
When exporting with media, you can send up to 10,000 latest messages. Without media, you can send 40,000 messages. These constraints are due to maximum email sizes (because the export might get sent via email).

I believe this constraint is a recent addition. I've got older huge exported chats with more than 40k lines that weigh more than 2MB. Nevermind, they were chats without media. Those constraints were there all along.

Anyway, 40k messages should be enough to cover most chats I believe.

@timea-techgirl
Copy link
Author

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?

@gariasf
Copy link
Member

gariasf commented Sep 11, 2019

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.
Their README has more info about the procedure.

@timea-techgirl
Copy link
Author

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:
https://android.stackexchange.com/questions/215009/exporting-a-full-whatsapp-chat-to-txt

Look at the answer. It's a paid chrome extension.
https://chrome.google.com/webstore/detail/backup-whatsapp-chats/gmbicfpadlmgkfhfepknbmemfhahelll

@gariasf
Copy link
Member

gariasf commented Sep 11, 2019

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.

@timea-techgirl
Copy link
Author

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?

@gariasf
Copy link
Member

gariasf commented Sep 11, 2019

Because the license is tied to your google account when you buy the extension at the store.
I can give you more details in private on how to do what I said, I'm on Twittter and Telegram @gariasf, .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants