If you read the last image in the article, Twitter's security team already responded (within 2 days) that because this wasn't reproducible, there was nothing they could do to attempt to fix it.