Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Potential fix for reCaptcha problem #102

Merged
merged 1 commit into from
Feb 16, 2022

Conversation

Kanishka-Chandra
Copy link
Contributor

The code will now open a new instance of the browser for every upload/sales of a NFT. This is slower, but is a great fix for the time being.

The code will now open a new instance of the browser for every upload/sales of a NFT. This is slower, but is a great fix for the time being.
@maximedrn
Copy link
Owner

Hi, thanks for your work! Are you sure it works every time or will the reCAPTCHAs be constantly present after a few restarts of the webdriver?

@maximedrn
Copy link
Owner

I'll do some research before I make a sweater request. I think it's possible to disconnect from OpenSea after each upload and clear the webdriver cache to start the task again, this will save much more time than relaunching the whole webdriver + connecting to the wallet.

However I will propose this solution in the open issue until I find if what I propose is possible.

@Kanishka-Chandra
Copy link
Contributor Author

As far as I have tested it, it works. But after around 100 NFTs there is a reCaptcha which need to be manually completed, nevertheless. :(

PS. I am also a programmer like you and like to contribute to open-source, so need to thank me :)

@Kanishka-Chandra
Copy link
Contributor Author

Kanishka-Chandra commented Feb 15, 2022

I'll do some research before I make a sweater request. I think it's possible to disconnect from OpenSea after each upload and clear the webdriver cache to start the task again, this will save much more time than relaunching the whole webdriver + connecting to the wallet.

However I will propose this solution in the open issue until I find if what I propose is possible.

Sure if this can be done it will no doubt be better and faster. Especially because my tests so far show a substantial reduction in upload speeds using this method.

@maximedrn
Copy link
Owner

I am merging the pull request (to add you as a contributor and to thank you) but I will modify the code to make sure that when the connection to MetaMask/OpenSea fails, the bot restarts.
My bot loops on the connection if it fails so I had to add a counter to stop the webdriver after a certain number of failures.

@maximedrn maximedrn merged commit b425745 into maximedrn:master Feb 16, 2022
@Kanishka-Chandra
Copy link
Contributor Author

I am merging the pull request (to add you as a contributor and to thank you) but I will modify the code to make sure that when the connection to MetaMask/OpenSea fails, the bot restarts. My bot loops on the connection if it fails so I had to add a counter to stop the webdriver after a certain number of failures.

That's great, hope this code help many more.😊

And, to be honest I should be the one thanking you in the first place to write this code and give me a starting point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants