Unlock account via arkose captcha solve

[obnoxiousish]

I decided to implement this and a few other patches in my asynchronous port of this lib, might make it Async agnostic at some point but

https://github.com/obnoxiousish/async_twitter_api_client here it is incase you wish to bring it into main repo

hopefully you can figure out why it wont let me use the self.session to complete it, had to create a new asyncclient to compelte it

uses a 2captcha.py file + 2captcha API to get the arkose solve, so its a paid solution

[JulienMaille]

@obnoxiousish how hard do you think it would be to port your solver to this non-async repo? Also what's the average cost you've experienced using 2captcha for arkose?

[trevorhobenshield]

@JulienMaille whole library is already async, i've just wrapped everything with calls to .gather() and .run() for ease of use.

can easily use the underlying async methods directly instead if you really need to

[obnoxiousish]

@obnoxiousish how hard do you think it would be to port your solver to this non-async repo? Also what's the average cost you've experienced using 2captcha for arkose?

very easily you could just copy paste and switch to Client instead of AsyncClient

[obnoxiousish]

@JulienMaille whole library is already async, i've just wrapped everything with calls to .gather() and .run() for ease of use.

can easily use the underlying async methods directly instead if you really need to

Could you elaborate on this? as most of the library is using Client not AsyncClient

[trevorhobenshield]

for account actions yes, but scraper and search are all async.

[obnoxiousish]

for account actions yes, but scraper and search are all async.

ah, thanks for the reply. i don't mean to argue or fight or question your experience knowledge or etc but just to say my async port exists almost entirely for the use case of people wanting to use multiple accounts at once without threading or multiprocessing (minus a few extra features)

it's quite nice that the scraper and search functions are asynchronous under the hood however

thanks for the repo again!

[trevorhobenshield]

all good! yep that makes sense, i decided against making the account methods async at their core because it was too easy to accidentally batch calls at high volumes and flag/ban the accounts (e.g. liking/commenting/posting multiple content at once)

but if you're careful, then i agree it's a good idea to make the account methods async!