So, the AOLserver.com site, which has been hosted at SourceForge for years, is effectively “down” right now as requests to it are returning a “Error establishing a database connection” error. I’ve been a paying subscriber for SourceForge since 2004 because they claim to provide “priority support”–whatever that means.
Well, I went and opened “priority” support tickets to try and get the AOLserver.com site back online. To put it gently, the response I received was less than useful. I mean, three hours before I get a response–a canned response–which doesn’t even resolve my problem?
I recognize there’s not much I can do at this point, but what I can do is “vote with my wallet” … I’ve cancelled my SourceForge subscription today:

The clock is now ticking: they have just under a year to show that they can seriously run a valuable service correctly, or I won’t be renewing my subscription next year.
Update: Jacob Moorman, Director of Operations at SourceForge.net, emailed me to point out that the IP addresses for SourceForge’s VHOST had changed. Sadly, the DNS for aolserver.{com,net,org} had been set up as A records instead of as CNAME records.
So, I’ve sent a request to have the DNS updated.
Tags: SourceForge, subscription, cancelled








November 6th, 2009 at 6:44 pm
Good question. I suspect the twitter user community who was accustomed to the old pre-oauth ways of dealing with authorization ...
November 5th, 2009 at 6:21 pm
Another question that occurred to me -- how is this different than cookies allowing access to a site when browsing? ...
November 5th, 2009 at 5:57 pm
I agree with that option as well. It largely depends on what the outstanding tokens allow access to in my ...
November 5th, 2009 at 5:48 pm
I would paraphrase what Terrence said a bit: Most users expect that when you change your password, having known the ...
November 5th, 2009 at 3:22 pm
Alex: That's a great analogy -- hopefully, that helps others understand why the "expected" behavior that Terence suggests is both ...