Twarc

* Add start-time/since-id parameters in the timeline CLI command to the timelines CLI command.
* Ensure that sample command only writes JSON on stdout.

v2.7.0 adds a new `places` command to search for places and their identifiers, which can be used in search and stream queries. Even though it's still on the 1.1 endpoint the 1.1/geo/search.json API endpoint makes these place identifiers available when searching by the name, geo coordinates, or ip address.


Usage: twarc2 places [OPTIONS] VALUE [OUTFILE]

Search for places by place name, geo coordinates or ip address.

Options:
--type [name|geo|ip] How to search for places (defaults to name)
--granularity [neighborhood|city|admin|country]
What type of places to search for (defaults
to neighborhood)
--max-results INTEGER Maximum results to return
--json Output raw JSON response
--help Show this message and exit.


There is a corresponding method `twarc.client2.Twarc2.geo()` method which you
can use to do the lookup yourself from Python.

- Adds the searches CLI command for running multiple searches from an input file
- Makes progress reporting more accurate for commands that consume files one line at a time (users, conversations, hydrate etc)

This release includes new functionality for working with Twitter's new [Batch Compliance API](https://developer.twitter.com/en/docs/twitter-api/compliance/batch-compliance/introduction) which allow you to upload large datasets of Tweet or user IDs to retrieve their compliance status in order to determine what data requires action in order to bring your datasets into compliance.


Usage: twarc2 compliance-job [OPTIONS] COMMAND [ARGS]...

Create, retrieve and list batch compliance jobs for Tweets and Users.

Options:
--help Show this message and exit.

Commands:
create Create a new compliance job and upload tweet IDs.
download Download the compliance job with the specified ID.
get Returns status and download information about the job ID.
list Returns a list of compliance jobs by job type and status.

This release ensures that the timeline, timelines, conversation and conversations commands default to a `--start-time` of `2006-03-21` (the first day of tweets) when being instructed to use the `/tweets/search/all` endpoint behind the scenese. For example when doing:

twarc2 timeline --use-search jack

or:

twarc2 conversation --archive 21

Previously it was defaulting to the last 30 days (which is an unfortunate default set by the `/tweets/search/all` endpoint). Many thanks to Darren Halpin and SamHames for identifying and fixing the issue!