Forum Posts

Great, Thanks for support Robin.

Hi Robin, Thanks for the quick fix. I like to mention something, prior then your fix the "reverse stack count" was used to return the projects sorted by popularity (e.g, Firefox, Subversion, Apache ... [More] ...), but now "stack count" returns project this way, though I'm not sure if this change is intentional or not, I'd like warn of a potential bc break (yeah I know what beta means :) [Less]

When I pass the "stackcountreverse" as sort option, API returns a failed response with error message: "An unknown application error occured." The other endpoints (I mean except projects.xml which ... [More] accepts sort) are all fine, and projects.xml works fine too with other parameters or even other sort options (e.g, createdat or createdatreverse), but only fails with stackcount_reverse. [Less]

Hi, There's two different registered projects (#10861 and #9667) pointing to the same project (Open Komodo), one is named "OpenKomodo" and the other one is "Open Komodo" (note the space). Since these ... [More] two are actually one project, I think it'd be better to remove one of 'em as it probably cost Ohloh (Am I right? you do download, analyze and ... twice, once for each of them). It'd be really nice if you add a "Report this project" or something like this to each projects information page, that way reporting Spams, Duplications and ... would be a more pleasant job. btw. It's the second time my Facebook Application which uses Ohloh API helped me out to find a problem in projects registration/information, the other one was when a user changed the name of Ubuntu project ;) [Less]

Uh, I forgot. Something else, Now, the API represent the response status in entity body of HTTP response, ``HTTP Response Codes'' could play this role better.

Hi, I'm in the middle of writing a bootleg WADL for the Ohloh API, and the API is great, but something annoying me a little, and that's the way the resources are URIed. I think that would be far ... [More] better if the .xml extensions being removed from URIs and the API get more of its food through GET params, rather than URLs. I mean: http://ohloh.net/api/projects/?appkey=foobar&v=1&projectid=1 instead of http://ohloh.net/projects/1.xml?appkey=foobar&v=1&projectid=1 According to the REST definitions the application has to provide one endpoint for each method, but not multiple endpoints for one method (retrieving a project's details is one method, and we need some scoping informations indeed, but those parameters are better to be provided using HTTP's POST or GET). I guess, the current implementation is on this basis that you prefer to serve static data (which will be (re)generated only on changes and are less-resources-hog) rather than generating them on the fly. And another thing, IMHO, another improvement (not so important though) is to move the resources base from "http://www.ohloh.net" to something like "http://api.ohloh.net" or "http://www.ohloh.net/api/". I think when you're providing us a read-only API, making it a truly RESTful one would be great (and easier), cause you could be mentioned in different papers as a great example of a RESTful web service then ;) Thanks again. [Less]

A nice new feature could be displaying recent (e.g., last 10) requests beneath the API key usage report.

Not a bug, but a typo in API's docs. In http://www.ohloh.net/api/reference/project at the Collection URL section, there're some options for the sort parameter, it says that "stackcountreverse" is the ... [More] default one, but it seems that the default value is "name". [Less]