3 ms·

I recently joined nfl.com as a FE dev; I see a lot of 404s on Game Center data feeds. The feeds are being requested past the end of the data (the feed tells you

by potench 13y ago

I recently joined nfl.com as a FE dev; I see a lot of 404s on Game Center data feeds. The feeds are being requested past the end of the data (the feed tells you where to look for new data until last feed returns 200 with no data - beyond that it's a 404). Not sure how to reduce the 404s, suppose we could document the feeds and make them openly available. Hmm. I like finding projects in the wild that do creative things with nfl.com data. This guy is building an Arduino Fantasy Football trophy: https://github.com/sambrenner/future-trophy https://github.com/sambrenner/future-trophy And this person built an OSX app using score strip XML for current scores: https://github.com/kchau/NFL-Menu https://github.com/kchau/NFL-Menu

burntsushi 13y ago
> I recently joined nfl.com as a FE dev Wow, nice! Tell me, how many different unique identifiers to you have for each player/game? :P (Elias id, GSIS id, profile id, ...) > I see a lot of 404s on Game Center data feeds. Hmm, I'm not sure what you mean? It seems like the URL stays the same: http://www.nfl.com/liveupdate/game-center/2012080953/2012080953_gtd.json http://www.nfl.com/liveupdate/game-center/2012080953/2012080... > Not sure how to reduce the 404s, suppose we could document the feeds and make them openly available. Yeah, that'd be great! I had figured that you guys kept quiet about them purposefully. One of the things that has bit me is that the JSON feeds at the URL above only exist back to 2009. I haven't been able to discover a similar feed for older games. Any ideas? :-) Those projects are pretty neat, btw. The trophy one is really cool.