Dmitry Mottl

> how to use the nativetweets parameter @caradhras36, just add `filter:nativeretweets` to the `--querysearch` as following: ```GetOldTweets3 --querysearch "bitcoin filter:nativeretweets" --maxtweets 10```

I've tried get retweets from `BarackObama` but it didn't work as expected: ```GetOldTweets3 --querysearch "filter:nativeretweets" --username "BarackObama" --maxtweets 10``` Returned only 1 tweet. Weird. You can dig further: https://help.twitter.com/en/using-twitter/advanced-tweetdeck-features

@haidaraM, it will not work: "BarackObama" in your case is not a username, but a regular text. You can verify that by checking the gathered tweets.

@caradhras36, You can experiment with [Twitter search interface](https://twitter.com/search-advanced) to find a way to get retweets.

Hi, I doubt we can fix that easy. Probably one can split sentences by ellipsis taking into account the case of the first letter of the next word following ellipsis....

Only since 2005 though

Unlike python-side, rust-side doesn't take a filename as an argument for writing csv — it's a generic over `std::io::Write`. https://github.com/pola-rs/polars/blob/6f3c68b4920310e20fd6c78a7a9f2d947b608037/crates/polars-io/src/csv/write/writer.rs#L27-L46

It's your choice. To me, pandas approach is intuitive and works decent.

Btw, gzip supports multiple members out of the box, but without random access: [flate2::read::MultiGzDecoder](https://docs.rs/flate2/latest/flate2/read/struct.MultiGzDecoder.html)

Not really. We didn't agree with implementation. I prefer pandas approach with automatic recognition of compression from ".csv.gz" extension, while @ritchie46 wants to have a dedicated argument which turns compression...