Feature request: If data/account.js is not found, check parser.py's folder

[timhutton]

I'm talking to a user who had parser.py in the root folder of the archive (as in the instructions) but was running it from a different folder, like:

c:\Documents> python e:\twitter_archive\parser.py

We could easily detect that I think, by just checking for data/account.js in the script's folder. It might help some people.

[tirolerben]

My twitter archive also doesn't have a data folder, account.js is in the root of the archive. /e: Oh, my biggest archive is from 2020. They used a different archive structure back then.

[timhutton]

@tirolerben If you think there's a need to parse archives in that old format then please open a separate issue for that. I'm trying here to handle current-format archives but where the user ran the script from the 'wrong' place.

[flauschzelle]

This would be fixed by #135 (which can't be merged right now because of merge conflicts, but may be merged soon if they are resolved).