I see the lack of documentation and user friendly APIs to be the most frustrating experience ever and MAL is just digging itself a hole for not having a functional and easy to use API. AniDB have well documented API and so does other social networking sites like Twitter and Facebook which is more developer friendly than MAL will be unless they shape up... Having most of the functions not implement and having a not so friendly API is going to bite them in the butt if they do not act soon (and I'm losing patience with the lack of usable APIs)
Hi guys, I've been working on an unofficial MAL API to supplement the current official API. The main reasons I'm working on this are:
* development of the official API has been rather slow (which I totally understand because it's probably secondary to a lot of things MAL wants to focus on - I'm not attacking anyone :)),
* to focus on the more commonly used features on MyAnimeList.net,
* to provide a developer-friendly API following HTTP REST principles, and
* most importantly, because I need an API for an app I'm working on and need some features that are currently unavailable on the MAL API yet.
It is not production-ready yet and I'm looking for testers and feedback. You can check out the docs here: http://mal-api.com/docs/
@Xinil or MyAnimeList owners: I just want to help and not trying to steal your content or do anything evil. I'd love to help work on the official API and am willing to contribute all code or share ideas. I am a huge MAL fan and would like to help make it more developer friendly :)
Well gzip compression is no big deal to implement even without mod_gzip: you just compress the data with gzip and set the HTTP response flag of Content-Encoding to gzip. Moreover you need to make a check on the Accept-Encoding flag on the request to support old browsers.
Just output the list to a string, use zlib's gzcompress ( http://us3.php.net/manual/en/function.gzcompress.php ) and echo it, would be awesome. Maybe have a cache compressed also somewhere, only re-processed after the user has submitted any change to her list.
rather than gzip id rather the list just be compressed with gzcompress proc, no need for headers and file info etc if it's not a pack of files. I'm using that for the airing data xml and is working great, ~10x faster loading.