Zaph

Yup, I'm having the same problem (@wcarle)

Connection log of my bot's 24 hours prior to a ban http://paste.ubuntu.com/25465253/ (ban begins line #3212). It seems to be within the rules - no more than 200 requests per hour or 1 per second. I average out under 3 requests per minute.

The only thing I can think of is the XML feed is more trigger happy than the API? Of those 3 requests, one is to the mashup feed.

Thanks for allowing such a hassle-free private scripts provision, I was able to fix my Alfred workflow with only a single line change.

Question about a small bug. Almost all images attached to the video API are in JPG format, with the occasional PNG. However, some videos are listed with PNG urls but are actually JPGs, so unless you manually change the extension, you get an API error - example http://www.giantbomb.com/api/video/2300-10909/?api_key=. Any chance of a fix, or is it part of a larger problem?

I created an Alfred Workflow to browse latest GB videos and open them in Safari. While in the middle of updating it with a convoluted login script to allow playback directly in Quicktime (massive battery saver vs webplayer), I noticed my api key provides direct access to video urls.

Is this a permanent change? Or should I keep my login script handy...

@rorie:

@nicknotch: ahh, nice one!

Not really gaming related, but I think I know what's behind the equipment theft...

Come launch, I would bet that activating a 'used' game (and paying the fee), would deactivate the original install. Without this the math would get very sketchy and Microsoft would have to set the 'used fee' at the full $60 just to avoid exploitation.

No idea how to upload GIF's on this site, but here http://i.minus.com/i7IOB4yod6aKA.gif

@lordandrew: Yeah, I thought the problem lies with the Nexus 7 having quite a high pixel density for a 7" tablet, so when browsing in portrait mode, it's triggering the full two-column site. But you're right, the Chrome reports a viewport of 603 to stop things getting too small.

Oddly enough, if you hit the 'Request Desktop Site' option in Chrome, you'll actually get the proper single column mobile/tablet site - but clicking/tapping still doesn't work.

I suspect they'll have to do some specific viewport + user agent detection to fix this. Hopefully it won't take too long.

Not sure if this has been reported (can't get the search working), but using the Chrome app (both release and beta), the site loads up the desktop (two column) style, instead of the more touch-friendly single column 'mobile' style. This isn't a big deal, but the full site doesn't work at all because you cant 'click'/tap anything. All taps are detected as mouse-overs, making the site completely unusable. Resolution is 1280x800.