First, lose the ornamental display font you've set all your copy in. I almost gave up reading. Setting type in apps like this is a solved problem. Google [font stack], pick a conservative one, and use it. If you want to play with fonts, do it in your headers.

Second, you should know that this has been done before, most notably probably by Bettween, which ultimately failed. Do people really have the problem of tracking conversations on Twitter?

Note that Bettween had a pretty effective marketing tactic that you could steal: finding really interesting conversations and promoting them, so that their site functioned both as a sort of Twitter aggregator (key function of an aggregator that you don't have: most interesting stuff bubbles to front page) and as a vector for sharing conversations in places like HN, which spread the Bettween app around.

Your super-effective caching engine, described with words like "query" and "request" and "server" and "cache", is not relevant to your users. Like, at all. Try to develop an allergy to describing technology. If the benefit of some technical feature you build is "speed", then just say your site is super-fast. Don't waste time justifying it. Does that turn a whole paragraph into a 5 word sentence? GOOD. Users don't like reading your marketing copy.