twitter mashup privacy snafu
by bear
The whole Twittervision protected updates snafu is one of the reasons my super-sekrit Twitter project was designed from the start to not require any Twitter user account info.
The Twitter Blog outlines what was happening behind-the-scenes to cause the issue – turns out it wasn’t a hole in the API but rather an inadvertent use of data that was flagged as protected by Twittervision.
For me it was just easier to do without that data but I can see how Twittervision needed the info because of some of the extra features Dave added.
Update: Oh gnarly issue indeed - a comment in the meish.org article outlines that it was happening to people who didn’t even create Twittervision accounts but rather by people in their friends list who had accounts. Because anyone you have friended can see all of your posts Twittervision was able to also see them. New phrase of the day: Unintended Consequences