Anyone still reading this later, here's some more info. I took a nap so am just getting back. The photos are real time. There's no caching on my part. As they

Anyone still reading this later, here's some more info. I took a nap so am just getting back. The photos are real time. There's no caching on my part. As they are coming in from Twitter, they go right back out. The time of day has the biggest effect on the types of images shared. For example, during peak Japan/Korea hours you see lots of anime, food, cute pets, and jpop singers. When it's America time, it's largely food, porn, penis photos, fucked up images, and cute cats. After watching this for well over a year, I'm seriously concerned about America. We are really a fucked up people. For technical questions, I would advise people to seriously take a look at the code. There are a ton of optimizations in there. At a high level, an in-memory array of image objects prevents a massive memory leak I found in every tested browser last year in regards to garbage collecting image objects. Also, using in-memory canvas objects before drawing them to the display canvas gives a really nice performance boost. I experimented with different display styles. A fixed random pattern provided the nicest display vs time on screen for images. Basically, the old image stays on screen as long as the stream is fast. There are some UI features that need tweaking, so leave comments about good/bad stuff and I'll take a look. If you swipe up/down or hit the space bar it will pause the stream.