2 ms·
I wonder why Twitter has banned the two accounts that found the bug. I'd have given them a bug bounty instead...
by mschuster91 9y ago
I wonder why Twitter has banned the two accounts that found the bug. I'd have given them a bug bounty instead...
- dunblend 9y agoProbably covered by: > Spam & Security > Access, tamper with, or use non-public areas of Twitter, Twitter’s computer systems, or the technical delivery systems of Twitter’s providers (except as expressly permitted by the Twitter Bug Bounty program). > Interfere with or disrupt the access of any user, host or network, including, without limitation, sending a virus, overloading, flooding, spamming, mail-bombing Twitter’s services, or by scripting the creation of content in such a manner as to interfere with or create an undue burden on Twitter. https://support.twitter.com/articles/18311 https://support.twitter.com/articles/18311 I agree this was not a spam issue (many found it informative), but, depending on how this tweet was done, it could be a security issue.
- 0x0 9y agoProbably a quickfix attempt to get the site working while waiting for engineering to deploy a proper fix. These tweets seem to trigger some crazy 100% cpu javascript edge case for dozens of seconds on every page load at least on desktop web.
- mschuster91 9y agoYep, screwed up my whole Twitter feed - especially as a couple of my followers also picked up this thing.