I know it's somewhat brave to try to dump all of my tweets but that's exactly what I would expect from this command. And it tries. With varying results. I've got so far some 8 months of tweets on second attempt (within 10 minutes) and then "twidge: user error (Bad response: 503)"
Since results vary I would assume it's not twitter's limit or censorship on amount of data you can "liberate" as well it's probably not the api-call-limit-per-hour but simply server glitch (and the longer lsarchive runs the higher chances are) and simple "hold your breath and retry in 20 seconds, rinse, repeat" could probably work. Or a resume option.
I know it's somewhat brave to try to dump all of my tweets but that's exactly what I would expect from this command. And it tries. With varying results. I've got so far some 8 months of tweets on second attempt (within 10 minutes) and then "twidge: user error (Bad response: 503)"
Since results vary I would assume it's not twitter's limit or censorship on amount of data you can "liberate" as well it's probably not the api-call-limit-per-hour but simply server glitch (and the longer lsarchive runs the higher chances are) and simple "hold your breath and retry in 20 seconds, rinse, repeat" could probably work. Or a resume option.
Cheers.