We're using the Web Database API to store Rem's tweets, so there's no Twitter API hit on load.

In addition, I'm using the since_id when we make new requests, so I shouldn't be doubling up on tweets.

Status: ready

  1. None loaded up yet :-(