This could work, but there's two separate problems to solve: knowing when a verified account tweets, and capturing the tweet in a way that doesn't provably infr

This could work, but there's two separate problems to solve: knowing when a verified account tweets, and capturing the tweet in a way that doesn't provably infringe on the TOS. A crowdsourced capture solves the second stage, but only if someone in the crowd happens to be browsing the right page at the time an update is made. To make this work, someone can set up a 'shell company' that signs up for the Twitter API for a seemingly legitimate reason, and captures the actual events of verified accounts tweeting. Then, this service sends out events to all the crowdsourced clients to browse to the Twitter page and capture the content, and submit it to the project. The behavior of the crowdsourced clients would be undetectable from a normal web user, and there would be a layer of indirection between the client signed up for the Twitter API and the curators of the submitted tweets.