5 ms·

I'm working on an API that doesn't suck that will represent TV, Movies, Podcasts, WebTV, and other forms of media. A stack-overflow inspired reputation system

I'm working on an API that doesn't suck that will represent TV, Movies, Podcasts, WebTV, and other forms of media. A stack-overflow inspired reputation system will reward community members to contribute translations, new shows, movies and corrections. Background workers interface with EPGs, other APIs and streams of data from other sources.<p>An image proxy server means openmedia.io will do the heavy lifting delivering images in the dimensions that you want, backed by a speedy CDN.

carbuncle 14y ago
For movies only (I understand that you service does more than just movies, but for my application this is currently irrelevant), are there key differences (benefits and weaknesses) compared to TMDb : http://www.themoviedb.org/ http://www.themoviedb.org/ Or just scraping imdb
theallan 14y ago
This looks really interesting for a project I'm working on. The license being used is obviously very open, but at the say time, does it effectively preclude proxying requests or caching returned results? Basically, if I wanted to offer the data from this system as a data layer to my front-end, would I need to hit your server for every request?
ClayM 14y ago
are you thinking about other forms of media, maybe something like comic books? there's actually a pretty large need for a comic api and there's only one right now (comicvine) that has been neglected for 2 years.
- codebeaker 14y ago
  I'm keen for any media which is a) structured and b) is an essentially append-only dataset. I fear that existing APIs, through design and coincidence fail to address the needs of flexibly covering media of all types. Join the list, look me up, or feel free to contact me to discuss
- nicholassmith 14y ago
  I'd second this, there's distinct datasources for it (IIRC Diamond publish release dates for all titles they ship, which is practically everything in North America and England), but there's no way to consolidate it. Could create some cool tools with it as well.

carbuncle 14y ago

For movies only (I understand that you service does more than just movies, but for my application this is currently irrelevant), are there key differences (benefits and weaknesses) compared to TMDb : http://www.themoviedb.org/ http://www.themoviedb.org/ Or just scraping imdb

theallan 14y ago

This looks really interesting for a project I'm working on. The license being used is obviously very open, but at the say time, does it effectively preclude proxying requests or caching returned results? Basically, if I wanted to offer the data from this system as a data layer to my front-end, would I need to hit your server for every request?

ClayM 14y ago

are you thinking about other forms of media, maybe something like comic books? there's actually a pretty large need for a comic api and there's only one right now (comicvine) that has been neglected for 2 years.

codebeaker 14y ago
I'm keen for any media which is a) structured and b) is an essentially append-only dataset. I fear that existing APIs, through design and coincidence fail to address the needs of flexibly covering media of all types. Join the list, look me up, or feel free to contact me to discuss
nicholassmith 14y ago
I'd second this, there's distinct datasources for it (IIRC Diamond publish release dates for all titles they ship, which is practically everything in North America and England), but there's no way to consolidate it. Could create some cool tools with it as well.