Double or triple proxy in the working list

[futurnet]

I notice that when new proxy are added in awaiting proxy list, NHP not care if they was already checked before, so this is a
unecessary overload and in the working list there are many dupe or triple proxy.
For ex. now I have in my working list 4320 proxy, but only 3100 are unique proxy, this mean that I have in list 1200 dupe.
should be nice if nhp can check any new awaiting list against the working list and erase the dupe.

[jimbobo2779]

There are checks when adding a proxy to the internal list to ensure that it is not already entered, if it already exists in the list it won't be added. Proxies at the same IP but using a different port are treated as a new proxy as one port may not work where another works fine.

I have periodically checked that duplicate proxies were not added to the working list that is displayed to the user and have never seen it happen but I will look into it again and release an update if a fix is necessary.

[futurnet]

I don't know if that can help you to fix.
I work in this way:
firstly I load a personal list of proxy in the awaiting list (about 10000) and start to run.
I can confirm that in working list there are many dupe ( same IP same port).

[jimbobo2779]

For the manually imported proxy lists it was assumed that users that would take the extra step to manually scrape proxies would also dupe check the proxies before entering.

I have now added the usual dupe check from when proxies are scraped to when they are added manually. I am uploading the update and it will be available by the usually means in about 10 minutes.

[futurnet]

In fact my personal proxy list is filtred without dupes, so I guess the dupe come when nhp start to scrape new proxy from google or the checker check twice the same proxy and add double in working list.
Anyway i will test the new version and I will report to you.