Thank you for your response and I congratulate the team on the <first>
steps to truly behaving like a responsible open source project. I
just received an email in response to the letter I wrote this morning
to the President of the University of Washington. I am saddened that
I had to go to that level of escalation to elicit a response from the
team. I am heartened by the actions that Yoshi and the team have
taken today in response, and I hope they continue on the right path.
I see that new home page content has just been pushed. It states:
"WARNING Adeona is currently not working because the back-end service
(OpenDHT on PlanetLab) is proving to be unreliable. If you would like
to help us, please see subscribe to the adeona-developers mailing list
and see this initial post. Users may wish to subscribe to adeona-users
for announcements."
This, along with the other actions, are a very good first step,
however I think that it is CRITICAL to prevent and actively discourage
further downloads and installation of the Adeona software until the
new architecture discussed above is determined and incorporated. The
download links on the home page are still available and working and I
think these need to be removed as well to prevent further
installations by those who ignore warnings.
I also think the team should spend some time thinking about ways to
notify existing users. If there is no way to do so it should be a key
requirement for the next version to have a notification mechanism to
alert users in the future about critical issues, software updates or
warnings.
If you are interested, here is a link to the letter I sent this
morning including some of my suggestions as well as Yoshi's thoughtful
and constructive response..
http://gist.github.com/99315
Regarding the architectural questions. Obviously the pro's and cons
of various solutions should be discussed on the open developers
mailing list, now that there is one. I will join this list and
provide insight or guidance as appropriate and desired, and in my area
of expertise. There are many new services available that would
provide this type of service layer. Amazon SimpleDB, as well as
Google's AppEngine come to mind. They both provide the scale as well
as simple HTTP based API's. If a self hosted solution is desired
something like Tokyo Tyrant or CouchDB could be fronted with an API
like CloudKit to provide a REST interface. I am pretty certain that
through donations you could afford any of these solutions. There are
a lot of discussion that needs to happen.
I wish the project good luck and I will help where I can as long as
the core team is committed to staying involved and active. If not,
then the project should be shuttered now, or a new team of owners
sought ought from the open source community.
Cheers.
Glenn