With recent update of aiohttp_socks on July 16, 2020 - due to deprecation SocksConnector was renamed to ProxyConnector and SocksVer was renamed to ProxyType.

* Added language to tweetData and tweetFieldnames

* Added language to Tweet object as t.lang

* Added language to Tweet()

* added language field to update()

* updated to include language
Co-authored-by: JMorrow <jomorrcode@outlook.com>

fetching favorites and parsing in a new way since twitter returns a different page now. Output includes tweet text, tweet id, conversation id and date (#826)
Co-authored-by: yunus.catalcam <yunus.catalcam@vircongroup.com>

Co-authored-by: Lucas Magalhães <13581833+whoisroot@users.noreply.github.com>

* ability to specify tor control port and password from command line

* clarify documentation

* fixing not working example in README.md

* fixing error when username is not found

* revert README.md

* [FIX]: fix request error bug limiting requests

* [FEAT]: add dual poly. backoff + linear timer if request limit hit

Add a dual polynomial + linear timer to allow for optimal fine grain
searching of twitter timeout value. A new arg `min_wait_time` allows
users to to do one of three things; Firstly, if they know a value that
is optimal already then can input it directly allowing the timer to
stricty be a linear timer. Secondly, if Twitter suddenly changes their
timeout limit and the value no longer satifies the required amount,
the timer will decide the higher valued option between the polynomial
timer's and linear timer's next value so the application still
functions. Third, as the linear timers min_wait_time arg goes to zero
the timer becomes strictly a polynomial backoff timer that allows the
user versatility and less likely to explode in the case of a change in
Twitter request limit timeout.

* [FIX]: add args to config.py

* [REFACT]: minor changes to run.py

* [REFACT]: small change to arg case

i found a bug where you were using a variable "obj" that wasn't defined

In threaded applications, if the user does not explictly create a new 
event loop then one does not exist.

* Fix strftime format string

Lines 28 and 29 that were using `.strftime('%s')` where it should be written as `.strftime('%S')`. This error would make twint fail with an `Invalid format string` when using time-related configurations like `Since` and `Until`.

* Change strftime to timestamp

As we are looking for the timestamp version of the provided date/time string, using `timestamp()` should be more straightforward and shouldn't create any incompatibility issues as twint already requires Python >= 3.6