I want to voice support of this decision. I build third party apps that are 100% about consuming, purposing, and displaying tweet streams. If different clients inevitably begin selling tweet injections, I really don't want to deal with those on my end. The tweet stream should remain a pure data entity. Dick has already said apps can opt out of displaying tweets, but if other apps are injecting, I lose control of that, and it will wreck the integrity of my app. Trust is ensuring that tweets coming to me through streams, are, to the best of twitter's ability, not spam.
On Mon, May 24, 2010 at 10:18 AM, Duane Roelands <duane.roela...@gmail.com>wrote: > > The way this reads, you can't even have a WordPress blog that puts ads > > near a Twitter stream. Please correct me if I'm misinterpreting this. > > You're misinterpreting it. There's not a problem if you're displaying > a Twitter feed on a page and there are ads -near- it. What is now > forbidden is the injection of ads into the stream itself. >
