@episod, ‘you can poll your own store of tweets’ interests me. I read the Developer Rules of the Road, and 4.A.ii states:
You may export or extract non-programmatic, GUI-driven Twitter Content as a PDF or spreadsheet by using “save as” or similar functionality. Exporting Twitter Content to a datastore as a service or other cloud based service, however, is not permitted.
I’d interpreted the second sentence of that as meaning that it’s against the RotR to store tweet content in our own data store (where ‘tweet content’ includes the ‘text’ key of a JSON response from the API) if we’re intending to show it later; we can just store IDs, and have to link to twitter.com to display the tweets. Is that interpretation correct?