djnyce, Could you share how you tested oauth? I'm not very familiar with web coding and data structures, but here some of the results of my research and testing so far: http://kineme.net/forum/DevelopingCompositions/OAuthwNetworkTools I tested mattgolsen's solution in the above link, by installing the plug in for Twitter posting. I managed to sign in and get the passkey, but was more or less stuck there. That being said, even if that plug in works, it's for posting to twitter, not extracting tweets. One additional comment from me: Although it is stated in the v1.1 API that stream only supports json, I get the following behaviour when I call the new api using rss and json. (In the QC XML Extractor) https://api.twitter.com/1.1/search/tweets.json etc returns me an empty structure https://api.twitter.com/1.1/search/tweets.rss etc returns me a BAD AUTHENTICATION reply. Well at least for rss, I get a reply, whereas when I use json, I get NULL.
