-
-
Notifications
You must be signed in to change notification settings - Fork 950
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
Twitter cursor scroll broken, can no longer retrieve more than a handful of tweets at a time #1170
Comments
This seems to be inconsistent, so I'm starting to think it's some new way of throttling requests... |
Is happening to me too, even when I put my username and password into my config instead of using my exported cookies. |
This should have only been a problem when using the built in login functionality. By the way, someone on Gitter recently posted this link. Apparently Twitter is removing its nojs interface on the 15th, which might break any new login attempts by gallery-dl (cached sessions should keep working though). |
@mikf So just to clarify, after the 15th, we just export a cookie file for gallery-dl to use and everything will be fine? |
Either that, or you keep using Me figuring out how to do a login on the regular login page would also be a solution, but, just like the last time I tried, I still don't know how to get a valid (*) it's possible to extend the "lifetime" of a cached Twitter session by at least 4 years by modifying the |
I use cookies with /media , and I am experiencing the same issue |
It's been fixed, you'll need to use the dev version or wait for a stable release update. |
sorry to be annoying about this, but its on also, I noticed this behaviour is random,some times I get the first "batch", sometimes I get denied right on first request.
config file I used:
|
I'm assuming you cleared all your cookies related to twitter in your browser and then logged back in and re-exported them? |
yes I did my guess is: because they are deprecating the old no-js site, they are rolling an update with requires something else, using some blue-green deployment, thats why I get an error, but sometimes I get the expected response also, I am getting those errors on both |
Huh. I just downloaded the latest dev build and reset my twitter extractor back to using a cookies.txt and stopped getting the error. At least, I haven't re-encountered it yet. |
@mikf There's something very wrong and I'm not sure if this change is related. Even though in my account settings, it's set to display sensitive content and to not hide it in searches, I'm no longer getting those tweets during extraction unless I remove my login information from my config file. Switching to a cookie file does not help. EDIT: Yeah, this change must be related, since I've looked through other accounts I've extracted just before this change and they downloaded everything just fine. It's just anything that was downloaded after this change. |
Your search settings (not your account settings) look like this? And I'm fairly certain a00b60f has nothing to do with this. All it does is update the |
Yes, they look like that. And this is happening with retrieving just a normal link, e.g. twitter.com/username, I haven't actually tested to see if it's affecting search results yet or not. And I do have this enabled. |
So for example for this Tweet you don't get any images? $ gallery-dl -u USERNAME https://twitter.com/i/web/status/1337783924555010053
/tmp/twitter/IllustOgre/1337783924555010053_1.jpg
/tmp/twitter/IllustOgre/1337783924555010053_2.jpg or from the account?
|
Hang on a second. There's something strange going on. |
1337808490211864577 is a retweet of 1337783924555010053, which is why 1337783924555010053 got downloaded twice with But the important thing is 1337783924555010053 is considered sensitive content. |
Yeah, I realized that and I deleted my reply. It's not happening for that account, but it's happening for a different one that I'm skittish about posting here. I'm trying to get down to the bottom of this. |
Fuck me, that isn't it either, I forgot to revert my config. This is driving me crazy. Do you have an email? The account I have for you to test is a bit embarrassing. |
https://github.com/mikf/gallery-dl/blob/master/gallery_dl/__init__.py#L15 ... and I was just about done reverting that commit The only Twitter related changes since 1.15.3 are
and none of them are responsible, it seems. Maybe a Twitter internal change? |
I'm very sorry for that. I forgot to hit 'save' on my test configuration and when I reverted that commit I thought I had fixed it. I'm a bit frazzled since I'm now worried that this has been a problem for a long time and I'm not sure how much of what I've downloaded has been affected. I emailed you. |
Ok, I can see what you mean. |
It doesn't really make any sense why it's behaving this way. I really hope this hasn't been affecting search results too. |
Could it be that it only affects tweets that are part of reply chains? (Even if the artist is replying to themselves.) |
@ImportTaste maybe open another, different issue for this, since this is definitely worth investigating. @hellupline @biznizz v1.16.0 with the fix is out. As for installing the dev version of gallery-dl: the old instructions ( |
can confirm, my previous confusion was because I was already using an dev build, I solved it using ( and was going to send this here, but you already solved that, blazing fast mikf ): |
When logged in, some entries returned by Twitter's API are so called 'homeConversation's (they would be regular tweet entries otherwise.) Those weren't picked up before and resulted in missing files compared to accessing a timeline as guest. ('/media' timelines and search results were not affected)
This error is occuring whenever the
cursor=scroll
parameter is added to the extraction URL:[twitter][error] 403 Forbidden ("This request requires a matching csrf cookie and header.")
The text was updated successfully, but these errors were encountered: