-
-
Notifications
You must be signed in to change notification settings - Fork 995
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 is now broken #806
Comments
I'm having the same thing suddenly on the same version of gallery-dl. I think this is on twitter's end, I assume they just rolled out some tweak to how the HTML works |
Does TwitterTweetExtractor still expect the "legacy" version of Twitter (i.e. using the AdaptiveMedia container etc.)? Because that thing's definitely gone now; they said they'd shut it down today, and they did. GoodTwitter browser addon doesn't work anymore either, and trying to use cmd-line tools such as curl returns an html response with no actual page content except "We've detected that JavaScript is disabled in your browser." EDIT: Other workarounds are still functional, such as the "legacy" image server (pbs.twitter.com/media/HASH.ext:size) and nitter.net |
Yup. Site change. |
URLs of the form: |
@rivke41levp656 How do I get that URL from a Twitter post, may I ask? |
That form would be for downloading all of a user's posts. If you just want one particular tweet I would use something like Image Max URL instead of gallery-dl. For example the image you gave: |
Everything except logging in with username & password and TwitPic embeds should be working again. Metadata per Tweet is massively different than before (mostly raw API responses - might need some cleaning up) and the default 'archive_fmt' changed.
Everything Twitter related got rewritten and now uses the new interface: a10f31d There actually was a warning 3 weeks ago that Twitter was shutting down its legacy interface (#740), but I didn't get this done before releasing 1.14.0. As the commit message says, most things should be working again except logging in, and there are most likely a few bugs here and there, so please test this and let me know. (And if anyone knows where/how to get the |
I've updated to the latest dev build and ran it. It downloaded a few tweets, then had an error. I know you're still working on it, so I'm sure it'll be worked out. However, I did see something. I had my "Logging in with username and password is currently not possible. Use cookies from your browser session instead." Which cookies should I use? Do I just copy them from Inspect Element into the conf, or do I have to export them with cookies.txt like deviantart? |
Thank you for the prompt update as always! I once again can't stress enough how much I appreciate this application and your hard work. Anyways, I'll list down some of the issues I've found with my limited testing. This is the tweet I used to test. It looks like image and video downloading in general work well, but details like file naming and the JSON metadata have some kinks to them. For file naming, the following do not work (they are replaced with "None"):
Some other things I noticed:
|
Short status update:
Thanks for testing and giving some feedback! @biznizz And what was the error you got? Something like @Cak3lies
This is now
These were there before, but not as packed with (useless) information. The main reason to have them are retweets or quoted tweets. "user" is the timeline owner, and "author" is the original creator of a tweet. These are pretty much redundant most of the time, so if you (or anyone else) has a better solution, I'm all ears. (Maybe only include the "author" field if "author" and "user" differ?) |
So, get latest dev build, export twitter cookies with cookies.txt extension, and have the twitter config look like this?
And yes, I think that was the error I got. I didn't screenshot it, but that sounds right. |
Just to shill my twitter related issue, can gallery compare tweet_id/id_str with existing ones inside --archive files before attempting to query twitter for it? I'm not sure how the archive works but it seems to be doing pretty much nothing except logging. |
I believe it is a related error?
|
Can reproduce the above error (since your censorship was weak af):
Full output: https://gist.github.com/a801327d2c4a9d61a1d80e4a8f7838a1 |
Tried d769bb4 and it works just like it should now! |
2 new upates
@biznizz @pxssy @KaMyKaSii |
What would cause them to be different and why? |
@anonieee if it's a retweet the |
Is it still impossible to download from twitter? I'm getting WinError 10061 every time I try downloading an account from there. |
Did you try to login or use cookies file? Twitter downloads are working here. I just would like the developer to add support for Twitter fleets, but I believe they are available still only here in Brazil |
I did both of these things, and I'm using the latest dev build. (You're Brazilian, too? What a coincidence.) |
Do you mean you did it individually or both at the same time? If it is the second option, it is not advisable, choose only one. I use the cookie file method and it works well here, also always running the latest code. And yep, I'm Brazilian :) |
I can confirm that, after setting my twitter extractor to my cookies.txt, I'm able to download pics from tweets. As mentioned above, I wouldn't use both and would say that the cookies.txt option is the better one. |
Did you get a WinError 10061 message when you used both? |
I can confirm that I am using only cookies.txt file and still getting this error. |
And you have the latest version since the last release on the 12th? Hm.... Can you post your twitter extractor info from your config? Also (sorry to ask), but you do have a twitter account and was logged into it before exporting your cookies? Just trying to eliminate variables. Also, I didn't use both at any time, when mikf said he altered it to work with cookies.txt, I altered my USERNAME/PASSWORD in my extractor config to work with cookies. So I never got any error. It's just that using two different methods at once would probably cause issues. |
And yes, I have a twitter account. |
Hmm... try this configuration:
I haven't seen anything regarding Does your cookies.txt have any other cookies from other sites on it. Mine has both my DA and twitter cookies with no spaces between any of the lines, and they work properly with both sites. |
Well, obviously since the file is named cookies.twitter.com.txt, it's specific to twitter. I had no idea until now that it was possible to store cookies for multiple sites in a single file. And, unless someone corrects me, twitpic images are still present in the accounts that used that site to post their images, and I don't want to ignore them. How come your configuration has the cookies settings so much farther than the other settings above? Is there some purpose to doing that? |
So I tested it with --ignore-config, and it still didn't work. |
Well, specifying/using different cookies.txt files should work. I just have two: the native one exported from browser with EVERY cookie I have, and a more managable one I use with gallery-dl that I can specify which site cookies to copy into. Dunno why my cookie creds are that far off when I copypasta'd it here, just formatting I guess. It still parses properly. Question: can you use gallery-dl on any other site other than twitter? Does it work with Deviantart at the moment? Because looking it up, WinError 10061 with Python means that there's a connection issue. |
Yes, I tested with dA and Tumblr. Both work fine. |
Well, it works for me here in the US. Do you have a VPN? You could try to run gallery-dl with it on a non-Brazillian server and see if that clears up the issue. |
I do... I'll try using it tomorrow. It may also be a good idea to try clearing my cache. |
Whatever the problem was before, clearing the cache fixed it. Didn't need to use a VPN. |
Well, glad to hear it. Since it was a connection issue, I figured it might have been a regional issue; dunno how the cache would have caused that, but whatev things are working for you now. :) |
Is anything being done about Issue #798? I can't test it, as I don't follow any locked accounts. |
I follow a few private accounts and they currently all work. Either the problem is actually unrelated to it being private or something is wrong with his setup. |
I sure hope someone tries to help him; I'm at my wits' end at this point. |
I'll try to give the guy a follow request and test it out if he accepts it. At least that way we can know for sure whether or not it's an actual bug. |
I think most bugs have been fixed and every feature has been restored to how it was before or even improved. General changes:
|
@KaMyKaSii it's rather hard to implement a feature without having access to it. Maybe open another issue for this specific feature and post a few timelines were I can find examples of these temporary tweets. |
For every Twitter post, I am now receiving this output. Was happening every so often a few hours ago, and now it does it all the time. Using gallery-dl 1.40.0.
Input
$ gallery-dl -j https://twitter.com/MotocrossNews/status/1267608884325216256
Output
Verbose
The text was updated successfully, but these errors were encountered: