-
Notifications
You must be signed in to change notification settings - Fork 45
"API query failed" for files/photos, then downloads spam for topics #131
Comments
Hello, |
We must have tried it a couple of dozen times, always very carefully checking everything. I even logged out, and logged back in, and copied the cookies from that session to see if maybe the cookies had timed out. We had three sets of eyes on it every time we tried. I don't think it's anything as simple as a missing quotation mark, since we downloaded something, just not what we were aiming for. Everything we downloaded under 'topics' was junk. It seems like we downloaded a spam folder, which Yahoo Groups doesn't have. None of the data made any mention of the group name anywhere. Very strange. |
Try with email option "-e" it is slower but you can parallelize the download with the options --start and --stop, example: |
I am also having issues downloading files. I'm using I have confirmed that I am using the full cookies for the T and Y values. |
yahoo.py -ct "z=someLongText&a=someLongText&sk=someLongText&ks=someLongText&kt=someLongText&ku=someLongText&d=someLongText&af=someLongText" -cy "v=1&n=someLongText&l=someShortText=someShortText&r=hp&intl=us" "nameofmygroup" -f |
I'm not super tech savvy, but got a couple of techies to help me install Python, then Pip, and we finally got some movement with the downloader, but never managed to download anything from my group.
For files and photos I consistently get "API query failed", but then for topics I get a bunch of downloads, but it's all pornographic spam. Not a single legitimate message from the group.
It's late in the game, but I'm still hoping to download my archives in the next 24 hours, before Yahoo removes them. Is there anyone who has some insight into what could cause this, and how to fix it?
The command line specifiess the location of the archiver, then the location of Python, then: ./yahoo.py group -ct 'T cookie' -cy 'Y cookie' 'nameofmygroup'.
We got an error that 'group' was a necessary argument, so inserted it, and that's what finally made it do something....except not what we wanted it to.
Thanks for any last minute insight anyone might have.
The text was updated successfully, but these errors were encountered: