[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


I want to build a simple API (any topic is fine). What kind of APIs do you think are missing or would be fun to create?
>>
>>106790788
pussy API (no authorization needed please)
>>
>>106790788
API for what? API can means different things, chud. It can be a library API or a web API.
>>
make a wrapper that talks to rtorrent and exposes a transmission RPC compatible API, so that you can use GUIs like https://github.com/openscopeproject/TrguiNG and https://github.com/equeim/tremotesf2 with a bittorrent client backend that sucks less
>>
>>106790788
One API project I was tinkering with throughout the years was a game content database. EAV setup with games and entity categories, each category having attributes. Replacement for wikis.

For example Dark Souls game, entity categories for monsters (with attributes health, defenses), items (attributes for stats, upgrades), achievements, areas etc. Allows for nice JSON representation and UI with eg DataTables. Different games have their own category, bit of a multi-tenant setup. Each game with their own (sub)website.

Still too lazy to continue to tinker with this. Shit got complicated fast, especially trying to data model relations (item x drops from monster y, but could also be found on the ground in area z).
>>
reinvent 4chan api



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.