"OddScott" wrote:
I'm going to speculate that some of the "other API functionality" includes NTP / time & date service. I had a channel mysteriously fail on Dec 24 and start working again on Dec 25. The channel uses signed time-expiring S3 URLs to get its feed file, and the only thing I can think of that would break it is if the player had a bogus date & time. S3 was not affected by the outage.
Quite a few people claimed that the time was wrong on their Rokus. I had a similar issue with my Instant Watch Browser channel, which uses timestamped URLs when communicating with Netflix. Of course, the general Netflix outage was a bigger issue for me on that one..
😛
My Channels: http://roku.permanence.com - Twitter: @TheEndlessDev
Instant Watch Browser (NetflixIWB), Aquarium Screensaver (AQUARIUM), Clever Clocks Screensaver (CLEVERCLOCKS), iTunes Podcasts (ITPC), My Channels (MYCHANNELS)