Sign up for our daily briefing
Make your busy days simpler with Axios AM/PM. Catch up on what's new and why it matters in just 5 minutes.
Catch up on coronavirus stories and special reports, curated by Mike Allen everyday
Catch up on coronavirus stories and special reports, curated by Mike Allen everyday
Denver news in your inbox
Catch up on the most important stories affecting your hometown with Axios Denver
Des Moines news in your inbox
Catch up on the most important stories affecting your hometown with Axios Des Moines
Minneapolis-St. Paul news in your inbox
Catch up on the most important stories affecting your hometown with Axios Twin Cities
Tampa Bay news in your inbox
Catch up on the most important stories affecting your hometown with Axios Tampa Bay
Charlotte news in your inbox
Catch up on the most important stories affecting your hometown with Axios Charlotte
Photo: Omar Marques/SOPA Images/LightRocket via Getty Images
Twitter announced Friday that it has discovered a "complex" flaw in a developer library, known as an API, that may have sent tweets and direct messages intended for one account to app developers who should not have received them. That glitch has since been repaired.
What they're saying: In a blog post announcing the bug, Twitter wrote that, "based on our initial analysis, a complex series of technical circumstances had to occur at the same time for this bug to have resulted in account information definitively being shared with the wrong source."
The bottom line: If the company's initial analysis is correct, there is a good chance you were not affected. The blog post specifically says a lot had to go wrong at the same time for this to be an issue, and that the bug only affected messages to those accounts using the API — often companies that could afford custom apps.