Permanently Closed Marketplace Sales Thread

Status
Not open for further replies.
Paid via Paypal but did not receive the serial nor does using my email or paypal account info work with activation of software. Express

Checkout Payment Sent (Unique Transaction ID #18647657R0625832E)
 
Paid via Paypal but did not receive the serial nor does using my email or paypal account info work with activation of software. Express

Checkout Payment Sent (Unique Transaction ID #18647657R0625832E)

I apologize for the inconvenience! Your email was replied to. ;) You signed up to our website with an email other than your PayPal email thus that is the email you should use as per the instructions.
 
"Hi Hat, I am sorry for the inconvenience but that is standard format for CSV files and it will not be modified. Quotes are used because otherwise how else would you encapsulate a comma inside of a value?
wink.png
If you look up "CSV Parse <your target programming language here>", there is most likely a built-in way to properly parse CSV, or somebody else has already written the code."

We forgot another solution... filter out those by country filtering with comma's in them.... ;)

Congo, The Democratic Republic of the
France, Metropolitan
Iran, Islamic Republic of
Korea, Democratic People's Republic of
Korea, Republic of
Moldava, Republic of
Macedonia, the Former Yugoslav Republic of
Micronesia, Federated States of
Palestinian Territor, Occupied
Tanzania, United Republic of
Virgin Islands, British
Virgin Islands, U.S.

Less hassle.:)
 
Last edited:
JRim, in automation mode, if I set my interval to say 1 hour, why do I have to wait a full hour before the proxies get tested after the program starts? This is a terrible waste of time for me.

Can't you start testing immediately after your scraped to start off the scheduling and setting the timer at *that point* The longer the duration of the automation interval, the longer we have to wait for the proxies to be tested.

PM should trigger proxy testing immediately after the scraping is done and setting the "time to start" at that point rather than, say when the program starts.

hope this makes sense.
 
"Hi Hat, I am sorry for the inconvenience but that is standard format for CSV files and it will not be modified. Quotes are used because otherwise how else would you encapsulate a comma inside of a value?
wink.png
If you look up "CSV Parse <your target programming language here>", there is most likely a built-in way to properly parse CSV, or somebody else has already written the code."

We forgot another solution... filter out those by country filtering with comma's in them.... ;)

Congo, The Democratic Republic of the
France, Metropolitan
Iran, Islamic Republic of
Korea, Democratic People's Republic of
Korea, Republic of
Moldava, Republic of
Macedonia, the Former Yugoslav Republic of
Micronesia, Federated States of
Palestinian Territor, Occupied
Tanzania, United Republic of
Virgin Islands, British
Virgin Islands, U.S.

Less hassle.:)

What do you mean filter out those? Can you try to explain it differently for me?

JRim, in automation mode, if I set my interval to say 1 hour, why do I have to wait a full hour before the proxies get tested after the program starts? This is a terrible waste of time for me.

Can't you start testing immediately after your scraped to start off the scheduling and setting the timer at *that point* The longer the duration of the automation interval, the longer we have to wait for the proxies to be tested.

PM should trigger proxy testing immediately after the scraping is done and setting the "time to start" at that point rather than, say when the program starts.

hope this makes sense.

Hi Hat, perhaps a button will be added to trigger automation on-demand in a future release; thank you for the suggestion! ;)
 
I bought Proxy Multiply and its great I get around 500 tested and working anon proxies in around 15 mins (my net speed is very slow). I also bought the addon as it will increase your speed to get working proxies fast. This is a must have tool if you are using scrapebox.

One suggestions: Add an option to filter proxies by speed in automation and otherwise (Say I only want to keep fast & medium speed proxies)
 
"What do you mean filter out those? Can you try to explain it differently for me?"

Your wonderful feature to filter out by country solves the problem.

Configure | Country Filtering
Then click on radio button "Do NOT accept proxies from these countries"
Then, tick off each of the countries I listed above with a comma in it

That solves the problem for CSV issues on my end and for developers who maybe automating output and don't want the hassle of having to parse based on dual double quotes with commas inside the data. That is, we just dont include the data at all. Get it? :)
 
"Hi Hat, perhaps a button will be added to trigger automation on-demand in a future release; thank you for the suggestion"

Do you really need a new button?

When automation is enabled
If I press Get proxies, it starts fetching proxies immediately. Then, proxies sit there in the queue waiting for testing until the first automated run time.
If I press the Test proxies button, proxies are then tested.

So *manually*, when automation is on, I can perform these steps after the program boots up.

Ideally for all the automation people out there, to eliminate the long wait, it would be ideal to do this:

if automation enabled
get proxies
test proxies
next scheduled run = current time + automation interval

somewhere in your algorithm, you are blocking the first automation run from starting immediately

hope that makes sense
 
Last edited:
can i use these proxies with xrumer and just copy the proxies suppose my server is in france and i only need france proxies is this possible?
 
"One suggestions: Add an option to filter proxies by speed in automation and otherwise (Say I only want to keep fast & medium speed proxies)"

Yes, I would like that too. I ran into that issue a few days ago when some of the proxies I was using were extremely slow.
It would avoid having to do any filtering on the data, especially for automation. When you look at the table, its the only column that doesnt have a filter for it.

I would think it would be appropriate to have it in the HTTP Proxy Testing Anonymity and Filtering section.
A checkbox with the words "Delete proxies slower than" and then an edit box that takes a millisecond number between 1 and 10,000

that would make my day!
 
resistosai111: Proxy multiply has the ability to filter by country. So you can choose which proxies based on countries you want or dont want to use.
 

Attachments

  • pmc.jpg
    pmc.jpg
    69.4 KB · Views: 37
"One suggestions: Add an option to filter proxies by speed in automation and otherwise (Say I only want to keep fast & medium speed proxies)"

Yes, I would like that too. I ran into that issue a few days ago when some of the proxies I was using were extremely slow.
It would avoid having to do any filtering on the data, especially for automation. When you look at the table, its the only column that doesnt have a filter for it.

I would think it would be appropriate to have it in the HTTP Proxy Testing Anonymity and Filtering section.
A checkbox with the words "Delete proxies slower than" and then an edit box that takes a millisecond number between 1 and 10,000

that would make my day!
Why not just use this setting to select the slowest speed of proxies you want to keep?
dsafsdfasdf.jpg
 
kickapooh: Hmmm i just tested this. You maybe right. It filters based on seconds. I think what is confusing is that it doesn't say "speed" to give us any indication that this is what it really is.
I thought it was the maximum timeout value used in testing each proxy before PM would go onto the next one.

Although I would like to see the edit box take milliseconds than seconds to tune it better as looking at the real time in the reported CSV file, they are all over the place.

Example:
1000 = 1 second
800 = 6/10 second
500 = 1/2 second
etc.
 
Last edited:
kickapooh: i dont believe thats the proxy speed. Its the timeout between testing proxies, not the performance of the proxies themselves.

Notice its in seconds, rather than in milliseconds.
You may be right but wouldn't a timeout between seeing if a proxy is dead or alive be basically the same thing. For example setting PM to 5 seconds and it waits 5 seconds before trying a new one (declaring the previous one dead). I may be way off base here. Jrim, help us out here homie...
 
Hi guys, thank you all for providing support to each other as it is sincerely appreciated! It certainly makes my life a bit easier :)

Hat, we will add an option to trigger automation when the program first opens (if it is enabled). :)

With regards to the timeout and speed questions, it looks like there has been some ambiguity introduced into the program with the new "broad" speed rating system and the timeout delays. This will be addressed in a future update. :)
 
Hi Jrim, is there still any discount available? I'm late for your software.
 
Status
Not open for further replies.
Back
Top