You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 12, 2019. It is now read-only.
It's really simple code that just hits their API and returns a random, verified proxy's address and port. This works pretty dang well but the API service costs $15 a month - I don't want to spend $15 month on this.
Write a Ruby version of check-proxy and proxy-lists and use that.
I think I like solution two the best as it's the least amount of work that solves the problem. However, it'll add additional management complexity to the application.
The text was updated successfully, but these errors were encountered:
As of right now, proxies are generated by making API calls to gimmeproxy as evidenced by this code here:
It's really simple code that just hits their API and returns a random, verified proxy's address and port. This works pretty dang well but the API service costs $15 a month - I don't want to spend $15 month on this.
To get an understanding of the problem, I highly suggesting reading the three blog posts published by gimmeproxy's founder http://256cats.com/gimmeproxy-source-part1/
So, there are a few alternatives to using gimmeproxy:
I think I like solution two the best as it's the least amount of work that solves the problem. However, it'll add additional management complexity to the application.
The text was updated successfully, but these errors were encountered: