Rambling about sites that are NSFW Show more
So this is a tip for all you webdevs out there:
- Provide your API in JSON. XML gives me 20 ways and more to get my data and it's a pain to figure out how to do so in ETree. Contrast JSON which I can parse to a dict in a single command. (Faulty: Paheal)
- If you're gonna do pagination, report back how many pages or at the very least how many resources there are on a page and the total resource count (Faulty: Nhentais old API)
- Finally, DOCUMENT YOUR API SPEC! While usually I can figure out a lot from a list of endpoints, a proper API spec tells me everything I can expect and need to know for a project. (Faulty: Too fucking many to count.)
Final reply to this chain (I SWEAR I DIDN'T INTENT FOR IT TO BE THIS LONG!)
Also, if your site is having overload issues, don't be afraid to make your API toss results in a queue (looking at you archive.is!)
What is not acceptable is simply timing out the connection because the site is overloaded.
It's like Twitter but you can like host it yourself n crap. This instance will probably contain high dosages of weeb. TO GET APPROVED, READ THE ABOUT PAGE!