Twitter Notifies Developers About API Bug That Shared DMs With Wrong Developers (zdnet.com)
Twitter has started notifying developers today about an API bug that accidentally shared direct messages (private messages) or protected tweets from a Twitter business account with other developers. From a report: According to a support page published today, Twitter said the bug only manifested for Twitter business accounts where the account owner used the Account Activity API (AAAPI) to allow other developers access to that account's data. Because of the bug, the AAAPI sent DMs and protected tweets to the wrong person instead of the authorized developer. Twitter said it discovered the bug on September 10, and fixed it the same day. They also said the bug was active between May 2017 and September 2018, for almost 16 months. The bug represents a serious privacy issue, especially for Twitter business accounts that use DMs to handle customer complaints that in some cases may include private user information.
I kept getting all these crazy ranting tweets from Donald Trump like every morning.
We accidentally banned a bunch of conservatives.
We accidentally shared your private messages.
We accidentally made a profit.
... is that the DM's didn't get redirected to the right wrong people, but rather, to the wrong wrong people.
usually after a court- and gag-order are served. It's the often disguised in a way that looks unintentional, but still makes no sense when you wonder how it actually got there.
Remember that SSL security bug that Apple put into macOS, where a single misplaced goto made no sense as accidental, but opened the computer wide for anyone aware of it, and which Apple stubbornly refused to fix for 10 months? That's what it looks like when court- and gag-orders are served.
This is no different.
Amateurs. Let the business world know that these clowns can't be trusted with serious matters.
Populus vult decipi, ergo decipiatur...
"Force shits upon Reason's back." - Poor Richard's Almanac
They're sharing dungeon masters?
This is why some training is good. If all you're told is to write tests you won't be writing good tests. Proper testing not only tests that A can access B when it's supposed to, it also tests that C can't access B as well. You need to test all cases, including complements and opposites.