Unable to scrape all the data of an Twitter account, need help in scraping all of its contents

[rarelygoeshere]

Hello everyone, a recent problem occurred to me while I was using gallery-dl on Twitter.
I'm trying to scrape the data on this account, and while it was scraping, it seemingly arbitrarily stopped scraping at around over 3k images, despite there being much more than that, as you can see below.

Regarding what config I am using for Twitter, I am using the config from #4534, with afaik no altercations to it yet. However, if anyone wishes to review my config.json in its entirety, I have placed it at the bottom of this issue. Edit: I have deleted most of the irrelevant parts of the config and left out the parts I feel are relevant for the question.

I hope someone is willing to assist me on this matter. thanks 👍

the relevant config.json parts

{
    "extractor":
    {
        "base-directory": "./gallery-dl/",
        "parent-directory": false,
        "postprocessors": null,
        "archive": null,
        "cookies": null,
        "cookies-update": true,
        "proxy": null,
        "skip": true,

        "user-agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Firefox/115.0",
        "retries": 4,
        "timeout": 30.0,
        "verify": true,
        "fallback": true,

        "sleep": 0,
        "sleep-request": 0,
        "sleep-extractor": 0,

        "path-restrict": "auto",
        "path-replace": "_",
        "path-remove": "\\u0000-\\u001f\\u007f",
        "path-strip": "auto",
        "path-extended": true,

        "extension-map": {
            "jpeg": "jpg",
            "jpe" : "jpg",
            "jfif": "jpg",
            "jif" : "jpg",
            "jfi" : "jpg"
        },

        },
        "twitter":
        {
            "username": "null",
            "password": "null",
			"filename": "{author[name]}-{author[id]}({author[date]:%Y%m%d_%H%M%S})-{tweet_id}({date:%Y%m%d_%H%M%S}).{extension}",
            "cards": false,
            "conversations": false,
            "pinned": false,
            "quoted": false,
            "replies": true,
            "retweets": false,
            "strategy": null,
            "text-tweets": false,
            "twitpic": false,
            "unique": true,
            "users": "timeline",
            "videos": true

    "downloader":
    {
        "filesize-min": null,
        "filesize-max": null,
        "mtime": true,
        "part": true,
        "part-directory": null,
        "progress": 3.0,
        "rate": null,
        "retries": 4,
        "timeout": 30.0,
        "verify": true,

        "http":
        {
            "adjust-extensions": true,
            "chunk-size": 32768,
            "headers": null,
            "validate": true
        },

        "ytdl":
        {
            "format": null,
            "forward-cookies": false,
            "logging": true,
            "module": null,
            "outtmpl": null,
            "raw-options": null
        }
    },

    "output":
    {
        "mode": "auto",
        "progress": true,
        "shorten": true,
        "ansi": false,
        "colors": {
            "success": "1;32",
            "skip"   : "2"
        },
        "skip": true,
        "log": "[{name}][{levelname}] {message}",
        "logfile": null,
        "unsupportedfile": null
    },

    "netrc": false
}

[anthonyj-codestuff]

Friend, you may want to double-check those credentials before you publish your username and password on a public forum. Hope you've got 2FA turned on.

[rarelygoeshere]

oh right I forgot to delete that, That's my mistake, thank you for notifying me. I'll change that now. That's only a throwaway, so it's not that important thankfully

[anthonyj-codestuff]

You already know this I'm sure, but for anyone reading this, you should also change passwords on any other accounts that had this same password. But of course you don't need to because you never re-use passwords :)

[rarelygoeshere]

Good advice indeed, haha XD, you should also use a password manager to manage them all too to save the trouble forgetting them all.

[rarelygoeshere]

I'm not sure what's the etiquette for questions that aren't answered in a couple weeks but I'll make an input requesting for help again.

I recently got my g-dl up to date to the latest version (I figured out that I haven't updated it in a while) and retried scraping from the same account as above again, however, it still has the same problem, although this time it stopped downloading when it reached 3215 items. I hope that someone with better insights into g-dl might be able to assist me in this matter.

Thank you.

[mikf]

TLDR: Twitter search bad, but the only option

As far as I know, it is not really possible to get more items from a Twitter user than gallery-dl already gets, unless maybe with a more precise search query.

The current strategy is using the /media timeline for the first ~1000 items, followed by a search for from:USERNAME maxid:LAST_MEDIA_ID. The problem with this is 1) there are no other ways to get older Tweets other than searching and 2) search got severely crippled, rate limited, and is inaccurate (i.e. it misses Tweets).

Your config settings shouldn't matter all that much or at all as long as you run gallery-dl with twitter.com/USERAME as input URL.

I'm not sure what's the etiquette for questions that aren't answered in a couple weeks but I'll make an input requesting for help again.

Sorry about that, it wasn't my intention to ignore your question. Sometimes I put off answering a question for "later" (basically Soon:tm:) for various reasons. It then moves to page 2 or 3 in my notifications, never to be seen or remembered again.

(It also doesn't help that I've already answered very similar questions far too often)

[rarelygoeshere]

Hello! Thank you for coming by to answer this question for me! And don't worry about feeling like you ignored my question, I don't mind it.

That being said, what you say is rather unfortunate to hear, as I was able to scrape two accounts with over 10k media tweets with gallery-dl, yet for the above account, it caps at around over 3k tweets. I was really hoping I could scrape this entire account altogether.
So I suppose I should probably try to look into alternatives to tackle this large account for myself :( It's tough but it is what it is.

Thank you for coming by and answering my question, I appreciate it.

[FebX23]

If you're hitting a limit with gallery-dl on Twitter after scraping around 3k images, despite there being more, it sounds like you might be encountering API rate limits or the tool's internal limitations. The config from #4534 should generally work well, but every tool has its constraints, especially with large volumes of data.

For overcoming such limitations, Crawlbase could offer a potential solution. While it's not specifically designed for Twitter scraping, it's robust handling of requests and data could help manage and possibly bypass the stumbling blocks you're facing. It's particularly useful for large-scale scraping projects where managing requests efficiently and avoiding detection become crucial. You can also try brighdata or scrapingbee as alternatives.

[rarelygoeshere]

Thank you for your suggestions. However, upon investigation, I've found that they are all paid services, so I don't think I can afford to use them for my needs.