How to download within a specific time range from a specific list of account

[MarqFJA87]

I have a list of Twitter accounts, and I want to download all media tweets from these specific accounts that were made within a particular time range (between the beginning of January 18 and the end of January 19). Is it possible to do this?

[mikf]

This filter expression should work and stop after 2026-01-18

--filter "(date < datetime(2026, 1, 18) and abort()) or date <= datetime(2026, 1, 19)"

As an alternative, use an advanced search with
from:USERNAME since:2026-01-18 until:2026-01-19
as search query

"https://twitter.com/search?q=from:USERNAME since:2026-01-18 until:2026-01-19"

[mikf]

The message appears whenever the extraction process is interrupted, be it abort() like here or an error. Just ignore it or disable cursor for these.

[MarqFJA87]

Interrupted by what, though? There's no clear pattern to when the message would be triggered; it could go through like a dozen accounts before triggering it, or it could be triggered after going through only a couple of them since the last trigger.

[MarqFJA87]

@mikf Hey, uh, just checked the output, and it seems that the app is mostly fetching the text captions even when the tweet has images. And grabbing seemingly random tweets that are outside the designated range.

Also, the second method doesn't work at all with accounts that are shadowbanned from the search results.

[MarqFJA87]

OK, I finally cottoned on to the fact that I should've added "/media" to the URLs when using the first method. But now I'm left with the problem that it's still downloading the text captions for other, inapplicable tweets; how do I prevent gallery-dl from doing that?

EDIT: Turns out I should be using --post-filter instead of just --filter. Problem solved... hopefully. Time to test it with the whole list.

[mikf]

Interrupted by what, though? There's no clear pattern to when the message would be triggered; it could go through like a dozen accounts before triggering it, or it could be triggered after going through only a couple of them since the last trigger.

Fixed in 40e4cc6

There won't / shouldn't be any cursor messages when calling abort() anymore.

[MarqFJA87]

That's good to hear.

Also, forgot to report last night that --post-filter worked perfectly, so the OP question has been conclusively answered. Thank you very much for putting me on the right track.