Here you do nothing other than cast accusations. On the other thread however, you made some more interesting points:
So it's not actually an API - rather a centralised site for handling ebay-style reputations? With an API?
The core philosophy to this looks to me like an attempt to de-anonymise the currency (and I'm not sure that that is a good thing) by putting all participating payments through a central system (and I'm not sure that's a good thing) in a non open-source/transparent way (and we all know that's a bad thing)... for money.
It is JUST an API. It is designed to build a layer of trust over a users transactions, like described on the site
It's designed to allow app developers a central system for quick development in three ways, 1) they can use the API and develop quick apps off that data and API, 2) they can launch quickly with an established user base of offers by sellers and push their users / offers to them buyers. 3) it provides the missing layer of trust between unknown anonymous parties who would like to possibly transact but without any form of past history see each other as
he looks really dodgy to me
in your words
We're at war basically - and the attacks on wikileaks highlighted major weaknesses in the system... a decentralised currency is just a part of it. We need to decentralise everything... and the "troubles" that bitcoin had about a month ago were all down to centralisation.
Sounds like you're a little paranoid and given the state of affairs within the governments, legal systems etc. you are more than rightly aware of the issues. But decentralizing everything is not possible IMO. Building an API based on data means it will have to live in a server somewhere to operate, you cant build a database on bit torrent. And yes I am a developer in answer to this:
"Well versed in SQL Optimization" - riiight... not really a developer then?
The best one could do would be to use an open database such as fluidDB see here : http://techcrunch.com/2010/05/24/fluiddb-aims-to-become-the-wikipedia-of-databases/
This is an idea I will investigate as it could well be the closest we can get to openness for an API which works on a database operation like we're discussing here. However, what concerns me slightly is by opening up the data totally, could really expose traders and loose some of the anonymity which would be attractive in some places to be designed in. I will think more about this.
As regards development, I'm here to discuss this in an open way. Happy to take constructive feedback and take on board and hopefully address any concerns and adapt accordingly. I believe in getting as much feedback as possible while in development and hence why I have put this out there, instead of waiting till we had what we thought was "IT" then launched and then learned later that we had in some way gone in the wrong direction.