See this tweet from Twitter Comms: https://twitter.com/mgrooves/status/192303330876334082

to be fair, the whole point about Tiddlywiki (the subject of this article) is that it doesn't require any infrastructure to back it.

You can get ~1% of public tweets streamed to you at http://stream.twitter.com/1/statuses/sample.json (see docs at https://dev.twitter.com/docs/streaming-api/methods). You could develop a proof-of-concept using that.

Is that open to anyone now? I thought the process was you developed against user streams then once you scaled beyond those you requested access to the stream api? And, you need to request access to the user streams api too right?

I decided not to do real time streaming for my current project so never followed up on it.

*edit: Actually looks like I'd want access to statuses/links which would solve the problem of filtering for links on my the scanning end.