Author: Nick Statt
A bug in how Twitter’s platform is accessed by third-party app developers may have exposed certain Direct Messages of select users to developers who do not work for Twitter, the company disclosed in a blog post today.
Twitter says the bug was active starting sometime in May 2017, and it issued a fix within hours of discovering the bug on September 10th, 2018. It affected less than 1 percent of users, and the Direct Messages affected were between users and accounts or businesses that relied on a certain API designed for customer service interactions. Twitter’s example is a Direct Message with an airline that uses a developer account to access the affected API, which is known as the Account Activity API (AAAPI).
Twitter says it mostly...
Continue reading…
Continue reading...
A bug in how Twitter’s platform is accessed by third-party app developers may have exposed certain Direct Messages of select users to developers who do not work for Twitter, the company disclosed in a blog post today.
Twitter says the bug was active starting sometime in May 2017, and it issued a fix within hours of discovering the bug on September 10th, 2018. It affected less than 1 percent of users, and the Direct Messages affected were between users and accounts or businesses that relied on a certain API designed for customer service interactions. Twitter’s example is a Direct Message with an airline that uses a developer account to access the affected API, which is known as the Account Activity API (AAAPI).
Twitter says it mostly...
Continue reading…
Continue reading...