-
Notifications
You must be signed in to change notification settings - Fork 53
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
Minimal Archive for Testing / Different Archive Formats #10
Comments
@MetricMike I think if we can try to create some pull request for that, to detect which sort of archive is that? I don't have access to such archive so someone else have to do it. Also probably it has to use different methods for parsing as that's one big file for messages |
@MetricMike thanks for help on other PR. So what about test suite? |
Thank you @marzann for helping out with this: For now I'm going to focus my efforts with my facebook archive:
We'll probably have some overlap and significant diffs so I'm excited to see where we end up landing and working with you to make future development easier 😄 |
In order to analyse the different archives, an option might be, to make a script that will replace the text with a random string of the same length. That way we can ask user to send their archives in for further analyzation without compromising their privacy. That will also help in parsing (maybe different structures, who knows atm?) What ya thinking? |
Bringing part of the discussion from #7 over here:
Some users (@krishna015) seem to be getting a different archive which can't be processed using the script atm. I've tried using different languages but haven't been able to reproduce how they're getting that archive.
#9 also mentions a need for a minimal archive to help with testing.
I think we were all under the assumption that the archive looks like #7 (comment)
If anyone has examples of how to get an archive that looks different, that'd be helpful!
The text was updated successfully, but these errors were encountered: