Image source: Variety

Due to the bug in Tweeter which is there for more than four years is hitting the Twitter Android app which made some of the users private message exposed in the public. In which Twitter replied that the bug is only affecting when users turned on the “Protect your Tweets” settings and make some small changes in their account such as changing or you can say updating an email address.

The “Protect your Tweets” setting will make your account secure and private also block anyone account who doesn’t follow you back from viewing your tweets and need new followers to take your specific approval.

Image source: Variety

Twitter does not provide any other information on account changes which will harm and accidentally disable the privacy feature. The backend team of Twitter replied that they have already fixed this bug a few days ago, on 14 January, but the main point is it has affected users since 3 November 2014.

Twitter define this in its blog post that they have already reached out to users who were affected by the issue or bug which is exposing private tweets of the users, but they have told that it ” can not confirm every account that could have been impacted. And the Twitter team also turned the “Protect your Tweets” setting on back to its place for the users who had the feature disabled.

Twitter backend team tell that they do not have a full list of affected users account, and also tell that it “provides a wide notice so if anyone is affected by this bug then by this he can secure their privacy setting show their preferences.”

“Twitter understand and appreciate the trust you place in us, and are committed to earning that trust every day,” Twitter also post that they’re very sorry this happened and we’re handling a full review to help prevent this from happening again.”

If any users who think that they have already set their Tweets as “Protect your Tweets” should take a look at their privacy setting again. And if you are an iOS and web users then there is no need to take tension because this bug was Android App specific.


Please enter your comment!
Please enter your name here