Permanently Closed Marketplace Sales Thread
- Thread starter Jrim_Software
- Start date
- Status
Jrim_Software
Senior Member
- Aug 1, 2011
- 915
- 345
Update log:
utuxia, I believe you can still use the proxies in SB as Google proxies without testing them first. That is what is recommended. As mentioned, the proxies passing a Google test in PM are able to submit a Google search for a designated keyword and find a specific search result on the data Google sends back, indicating that the proxies are Google-enabled. I cannot speak as to why the proxies do not work in SB. Perhaps try contacting SB? Have you tried actually using the proxies in your browser to search Google?
Code:
1.0.0.51
-------
- Added the option to exclude ports from proxy scraping (Configuration -> Port Filtering).
- Proxy Multiply will now automatically test the initially scraped proxies after harvesting from the default leech list.
- Added an option to always test proxies after harvesting them and before continuing to scrape search engines (Configuration -> General).
- Added an option to disable search engine scraping after the initial proxy scrape (Configuration -> General).
- Added YouTube and TicketMaster proxy filtering to main window Proxy Type menu.
- Added checkboxes for enabled/selected proxy type in main window Proxy Type menu.
- Automation will now export the text file or send an e-mail after every proxy test cycle rather than only after finishing its automation cycle.utuxia, I believe you can still use the proxies in SB as Google proxies without testing them first. That is what is recommended. As mentioned, the proxies passing a Google test in PM are able to submit a Google search for a designated keyword and find a specific search result on the data Google sends back, indicating that the proxies are Google-enabled. I cannot speak as to why the proxies do not work in SB. Perhaps try contacting SB? Have you tried actually using the proxies in your browser to search Google?
Jrim_Software
Senior Member
- Aug 1, 2011
- 915
- 345
Hey jb, Proxy Multiply is self updating
Just open the software (close it if you have it opened) and it will update.
HatIsBlacked
Regular Member
- Dec 30, 2010
- 227
- 57
Gave a few test runs to the new update.
Feedback:
1) Turning off search leech list is working. Thanks for that.
2) ProxyType button looks better.
Bugs:
1) Ticking OFF the checkbox "When harvesting proxies, test the proxy list .... " has a bug. OFF to me means don't do that automatically. ON means automatically. It is kicking in automatically when OFF.
2) Menu has remnants of "toolStripMenuItem2" which does nothing.
3) Sometimes when I press ProxyType button, the configuration dialog box comes up. Likely due to the toolStripMenuItem problem.
4) Reload Default URLs does not work.
5) Rather than use ProxyType as a configuration option only, if there are existing records in the proxy panel, use it as a filter. So if I go press the proxytype button and choose elite only, show me only elite proxies. Hold all the proxies of course in a main array but slice the view to only show relevent chosen filter.
Suggestions:
1) Create a pause button to temporarily pause all threads for whatever operation is running. This is to avoid having to stop, and then start all over again (low priority)
2) In the total box area I would rather see this type of info:
Total | Trans | Anony | Elite
3) Add to proxytype menu in general section "Transparent proxies only"
4) Working is reporting the same as Total and is redundant
Feedback:
1) Turning off search leech list is working. Thanks for that.
2) ProxyType button looks better.
Bugs:
1) Ticking OFF the checkbox "When harvesting proxies, test the proxy list .... " has a bug. OFF to me means don't do that automatically. ON means automatically. It is kicking in automatically when OFF.
2) Menu has remnants of "toolStripMenuItem2" which does nothing.
3) Sometimes when I press ProxyType button, the configuration dialog box comes up. Likely due to the toolStripMenuItem problem.
4) Reload Default URLs does not work.
5) Rather than use ProxyType as a configuration option only, if there are existing records in the proxy panel, use it as a filter. So if I go press the proxytype button and choose elite only, show me only elite proxies. Hold all the proxies of course in a main array but slice the view to only show relevent chosen filter.
Suggestions:
1) Create a pause button to temporarily pause all threads for whatever operation is running. This is to avoid having to stop, and then start all over again (low priority)
2) In the total box area I would rather see this type of info:
Total | Trans | Anony | Elite
3) Add to proxytype menu in general section "Transparent proxies only"
4) Working is reporting the same as Total and is redundant
Last edited:
Where is the automatic testing of proxies before it moves on to the next list? My success rate in proxies is still the same as before. After testing for 5 hours I get just 400 proxies half of which are dead in 2 hours. And only maybe 30-40 Google enabled proxies. There are surely more public proxies on the net than this so why are the numbers so low?
Jrim_Software
Senior Member
- Aug 1, 2011
- 915
- 345
You are quick, thanks for the feedback!
1. The checkbox is working as intended. However, now Proxy Multiply will always test the proxies after the first initial scrape when the proxy list is empty. This was put into place to simplify the program and make it easier to use. The program does not allow this option to be toggled off as it currently works now; it is hard-coded to always test after the first scrape because most users don't even utilize configuration settings and simply use the program as it is provided to them. I think everybody's first step after scraping proxies is to test them anyway. It forces a test of the proxies after the initial scrape to improve proxy scraping thereafter, thus improving the functionality of the program as a whole. You can tell that the program is performing the forced first-scrape test by the text:
Code:
Cleaning up initial scrape proxy list to improve proxy scraping from search engines (testing ### proxies)2. D'oh! It is outside of the default program window size and thus didn't notice that, nice catch
3. Hmm. The button at the bottom of the Proxy Type menu will open the configuration window (as intended), but it shouldn't be opening spontaneously. Please let us know if the issue is resolved with the removal of the empty toolStipMenuItem2 object you mentioned earlier, in the latest update.
4. Are you referring to the button that is in the Proxy Fetching URLs configuration section? It is working properly on our end. Do you receive a prompt after clicking it (e.g. URLs reloaded successfully)? An error? Are any URLs added to the list or does the button just do nothing?
5. This may make sense functionally but I would not consider it a bug. The only issue with forcing the button to function as you described is that it may unexpectedly wipe out a proxy list for users. The 'Delete Proxies' button is more purposeful for filtering/deleting proxies as you mentioned. The "Proxy Type" button simply sets the testing requirements for future proxies. The tooltip on the "Proxy Type" button has been clarified to indicate such.
1. This will be considered but it seems to be more confusing to have both a 'Pause' and 'Stop' button for most users. Furthermore, the idea of suspending hundreds of threads (possibly infinitely if the program freezes or has some sort of failure) opens Pandora's box for memory issues.
2. Great idea.
3. Great idea.
4. Not necessarily. You will only see the number of 'Working' proxies match the number of 'Total' proxies after a proxy test. If the proxiesa re untested, your Total could be 100 with working showing 0. Even with the addition of the Anon/Trans/Elite boxes, you still need an 'Alive' or 'Working' box - not all users test for anonymity.
Hi jb, you can find the option under the General tab of the configuration menu (see screenshot):
1.0.0.52 update log
Code:
1.0.0.52
-------
- Added a 'Transparent only' proxy type to the main window Proxy Type.
- Added Twitter proxy filtering to main window Proxy Type menu.
- Added a search box to the main window.
- Added counters for Transparent and Elite proxies to the main window.HatIsBlacked
Regular Member
- Dec 30, 2010
- 227
- 57
Test of new update 1.0.0.52
New features
---------------------
Search proxy list feature looks good. I like the way it highlights rows if they have the specified term. Start,ends w/port,contains is great idea. Tested and works.
The total/working/trans/anony/elite box is clean and now more useful. Tested but a bug (see below).
Autotesting on first scrape works but I have a bug (see below)
Confirmed fix:
-----------------------
1) Menu glitch no longer exists
Bugs
---------------
1) I continue to get problems when clicking on the proxy type button. It brings up the proxy menu some times and at other times the config dialog box. Seems to be a focus or hit rectangle issue. Hard to reproduce. But seems to happen more frequently when I click towards the lower right bottom hand corner of the proxy type button
2) The reload default does not bring up the original urls that were part of the installation. Does it mean to bring up the original list state that existed at startup? Or what was shipped in the installation? To test, clear list and then save. Then hit the load button. Nothing gets loaded. I would store a separate default list with the product - call it defaulturl.txt. Then load that text file when this feature is used. Also prevents the case when people test and forget to save the original list (like I have right now. I need the original list again)
3) Dead proxies aren't listed in the proxy table even though I told config not to delete them. I want to see which are dying. Sometimes they can be retested. I expect to see those that failed listed as "HTTP: dead" status
4) I'm getting wrong anonymous proxy counts. Clear the fetch list and put in one or two urls in to fetch. Get the proxies. After testing is done observe the anonymous count against whats in the table. The reported number of anonymous proxies is not the same as whats listed in the tested proxy list (hit status column to sort and then count). Elite and transparent counts seem fine.
5) You are still going out and fetching search engines results.. After I did a test with a limited number of fetch urls and setting the limit to 25000 proxies, I let it sit idle. Only 1000 urls were fetched originally. Strangely, several minutes later, PM started to go out and fetch from the leech list. The scrape proxies from search engines was turned OFF. The total was at 25000 and the working/trans/anony/elite reflected only the state from the first run.
Potential Bugs
---------------
Some proxy websites I entered into the fetching url list do not scrape the proxies (see my pm to you)
Suggestions
---------------
Stats box
{Fetched|Working|Dead|Trans|Anon|Elite}
I want to know how many were fetched, how many are good, how many are bad, and the count for each type.
Add to the right click menu "Export". This saves us time by saving all criteria by making the workflow faster. So for example, if I decided to highlight all transparent proxies, I can select them all, then right click on the table and save to file. Then do the same for elite, dead, etc. This is as opposed to having to jump back and forth to a program to copy, paste, and save. Most of use these lists stored in separate text files that are loaded into our tools. Saving to CSV, loading Excel, data filtering and then saving each to a text file takes a lot more manual work.
New features
---------------------
Search proxy list feature looks good. I like the way it highlights rows if they have the specified term. Start,ends w/port,contains is great idea. Tested and works.
The total/working/trans/anony/elite box is clean and now more useful. Tested but a bug (see below).
Autotesting on first scrape works but I have a bug (see below)
Confirmed fix:
-----------------------
1) Menu glitch no longer exists
Bugs
---------------
1) I continue to get problems when clicking on the proxy type button. It brings up the proxy menu some times and at other times the config dialog box. Seems to be a focus or hit rectangle issue. Hard to reproduce. But seems to happen more frequently when I click towards the lower right bottom hand corner of the proxy type button
2) The reload default does not bring up the original urls that were part of the installation. Does it mean to bring up the original list state that existed at startup? Or what was shipped in the installation? To test, clear list and then save. Then hit the load button. Nothing gets loaded. I would store a separate default list with the product - call it defaulturl.txt. Then load that text file when this feature is used. Also prevents the case when people test and forget to save the original list (like I have right now. I need the original list again)
3) Dead proxies aren't listed in the proxy table even though I told config not to delete them. I want to see which are dying. Sometimes they can be retested. I expect to see those that failed listed as "HTTP: dead" status
4) I'm getting wrong anonymous proxy counts. Clear the fetch list and put in one or two urls in to fetch. Get the proxies. After testing is done observe the anonymous count against whats in the table. The reported number of anonymous proxies is not the same as whats listed in the tested proxy list (hit status column to sort and then count). Elite and transparent counts seem fine.
5) You are still going out and fetching search engines results.. After I did a test with a limited number of fetch urls and setting the limit to 25000 proxies, I let it sit idle. Only 1000 urls were fetched originally. Strangely, several minutes later, PM started to go out and fetch from the leech list. The scrape proxies from search engines was turned OFF. The total was at 25000 and the working/trans/anony/elite reflected only the state from the first run.
Potential Bugs
---------------
Some proxy websites I entered into the fetching url list do not scrape the proxies (see my pm to you)
Suggestions
---------------
Stats box
{Fetched|Working|Dead|Trans|Anon|Elite}
I want to know how many were fetched, how many are good, how many are bad, and the count for each type.
Add to the right click menu "Export". This saves us time by saving all criteria by making the workflow faster. So for example, if I decided to highlight all transparent proxies, I can select them all, then right click on the table and save to file. Then do the same for elite, dead, etc. This is as opposed to having to jump back and forth to a program to copy, paste, and save. Most of use these lists stored in separate text files that are loaded into our tools. Saving to CSV, loading Excel, data filtering and then saving each to a text file takes a lot more manual work.
Last edited:
HatIsBlacked
Regular Member
- Dec 30, 2010
- 227
- 57
Good question.
It is dependent upon the authority who is making that determination. In this case, the software itself.
The determination of what type of proxy can be made on the client side in the software itself or it can be done through asking a server side proxy judge.
What is transparent to one authority maybe anonymous to another. The devil is in the details. It should be noted that because you are using open public proxies from which are obtained from public websites you never really know what you are getting. It could be some 9 year old kid with a laptop in China for all you know.
Determination of the type of proxy is based on looking at the returned response header, in particular HTTP_VIA, VIA, X_FORWARD but there are many others and variations.
JRim, I would like to know what are the specifics you use in determining:
- What is a transparent proxy-
- What is an anonymous proxy
- What is an elite proxy
That is, what fields are you checking for existence and non-existence.
Last edited:
I might be using this wrong, but why does PM keep scraping for proxies?I have set it to pick up 10,000 proxies and then scan them. I have set the automation to keep scraping until there are 100 good proxies and then e-mail them to me.
However, PM just keeps scraping on and on. If I press the 'stop' button, then it starts testing automatically. If I press stop again, then it starts testing again on its own.
It just never stops and never e-mails me the list.
Any ideas what is wrong?
Last edited:
utuxia
BANNED
- Feb 14, 2011
- 673
- 113
I updated and after 12 hours of scanning, it found 92 ip addresses. I put those ip addresses into scrapebox google test and only 4 are any good. Still no files created or emails sent -- I have it set to send every 60 minutes.
Also your google test should really do a search. Because that's what scrapebox does. Your test passes, but searches fail in scrapebox.
Also your google test should really do a search. Because that's what scrapebox does. Your test passes, but searches fail in scrapebox.
I'm still having this same problem. It is basically making the software useless for me.
It's good that it keeps searching. But it's pretty bad that it won't stop when you ask it to.
Jrim_Software
Senior Member
- Aug 1, 2011
- 915
- 345
1. This issue is fixed, will be resolved in next update.
2. I apologize that you are still having this issue but it does not exist on our end. Can you please click the 'About' button and provide your authorization key via private message? We can then examine if your copy of the software is requesting the URLs properly.
3. For purposes of the automation process, dead proxies are removed from the list during the initial proxy test. Again, most users prefer that dead proxies are removed from the list anyway as they are of no use. Deleting the dead proxies allows search engine scrapes to produce more working proxies based on the logic that only working, alive proxies are used as the search query.
4. Whoops, looks like it was including the elite proxies in the count. Thanks.
5. If PM started to 'strangely fetch' several minutes later than it is due to your automation settings. If you have it set to maintain a certain proxy list size, it will do that, bearing that the proxy list test resulted in less proxies in the list than you desired by the threshold. If it was fetching from the leech list as you said I don't see an issue.
Regarding your suggestions, the Fetched counter will not be added due to the shortage of real estate (space) in the counter boxes. The total counter serves to count the number of total proxies and will remain in place. If you are suggesting simply renaming the label from 'Total' to 'Fetched', I think many users would find that more confusing.. The 'dead' box is not necessary as you can see how many are dead by subtracting the number of Working from the number of Total proxies. However, the 'export' request is certainly reasonable and usable.
Hat's response is more than sufficient
Thank you for your assistance in explaining what the transparent proxy is.
Transparent proxies: leak your real IP in some way.
Anonymous proxies: hide your real IP but have some sort of 'tell' that they are proxies; e.g. an X-FORWARDED-FOR flag or something of that nature.
Elite proxies will hide your IP and avoid giving any sort of indication that a proxy is being used.
Sorry, an unintentional bug was introduced in the latest update. The issue will be resolved shortly.
Thank you for bringing this to our attention.Hi utuxia, as previously mentioned, our Google passed proxies actually perform a Google search
I'm sorry for the inconvenience jamin but I'm glad you got it worked out.
Unintentional bug introduced in the last update; will be resolved shortly. Thank you for your patience.
Again, see above; unintentional bug.
HatIsBlacked
Regular Member
- Dec 30, 2010
- 227
- 57
I quick tested the new export feature and it works great. That one feature alone saves 10-15 minutes of manual spreadsheet operations. Thanks for that JRim.
Now if you can figure out a way to scrape any url with proxy/port it will be a big win. Maybe through use of a DOM parser that looks for all table nodes and then peers into the first two rows of each table to see which column the ip address and port lies (first row may be a header column). Some websites will list ip in a separate column from port. Some will also put them together (i.e. 123.123.123.123:80). PM isn't parsing all url pages that I throw at it. By doing this, PM should be able to parse more pages and users can specify new url's to be added to the proxy fetch url list as they find them.
Now if you can figure out a way to scrape any url with proxy/port it will be a big win. Maybe through use of a DOM parser that looks for all table nodes and then peers into the first two rows of each table to see which column the ip address and port lies (first row may be a header column). Some websites will list ip in a separate column from port. Some will also put them together (i.e. 123.123.123.123:80). PM isn't parsing all url pages that I throw at it. By doing this, PM should be able to parse more pages and users can specify new url's to be added to the proxy fetch url list as they find them.
uditbhansali
Regular Member
- Aug 16, 2010
- 488
- 292
Can you add this feature where one can compare the live saved proxies with the new the proxies scraped, this will prevent duplicate proxies from being saved and all the proxies on the list will be unique.
- Status