I have talked to sal in PM's (After the quoted post, I believe). I have no issue with him using CCE as an information source. I had already white listed one of CoinChoose addresses and was unaware of a second address.
The Coinchoose address that was blocked was only one of many address I had to block. Unfortunately I have no way of knowing which addresses are from legit service providers and which are not until communications are opened.
I do not believe ABE was designed for the amount of traffic that CCE experiences. Once CCEIII is up and running, this types of issues should disappear as my redesign is centered around high traffic while serving one coin. ABE was designed with handling multiple coins at a time and I do not use it that way. Each coin is on its own instance of ABE. With CCEIII there might be a master Cherrypy server to direct traffic to the correct coin server, but each coin will be running under its own instance of explorer and web server.
Sal, you do not need to stop using CCE. I just need to know all your addresses, so when I bring the ban hammer down, you don't get accidentally banned.
Before I get 10000000 posts yelling - CryptoCoinExplorer in an effort to reduce bandwidth has banned my polling of their block explorers. This has affected ANY coin they have listed on their site as having a block explorer (FTC, CHN, NVC, PPC, TRC, BBQ, BTE, BTB, DGC, JKC, Franko, GLD, WDC, CRaftcoin). They offer a great service and unfortunately, CoinChoose has impacted their service for other users, and we have agreed not to work to resolve it.
It will take some time, but I will just be bringing up coin daemons for each of these and downloading the block chain. I apologize for any inconvenience.
