I've played with it in the past and built some prototypes. With
changes to Twitter's RSS feeds they don't work any longer, but could
likely be dusted off at some point.
The answer I found was to utilize a simple web app that scrapes a
designated Twitter feed (could be a user's feed, a list's feed, a
hastag, etc.) and displays that to a technician. The tech can then
approve content as they go, creating a new, private list of curated
messages. The option to manually modify a tweet could be added ,
too. For example, replace a curse word with @%#$ to be able to use
some bluer messages.
On the display side, I had leveraged QuartzComposer to create a
composition that would go and get that data feed that my web app was
cooking up and display it in a visually pleasing fashion.
Depending on the strength of your system, the web app could run on
your operator's display while the Quartz data is being fed into Qlab.
Of course, you ARE inviting the internet into your production
environment. Always dicey.