From: https://blog.twitter.com/developer/en_us/topics/tools/2018/details-for-developers-on-Account-Activity-API-bug.html https://blog.twitter.com/developer/en_u

From: https://blog.twitter.com/developer/en_us/topics/tools/2018/details-for-developers-on-Account-Activity-API-bug.html https://blog.twitter.com/developer/en_us/topics/tools/2018/d... We have validated that this bug might have occurred when all of the following technical circumstances were true during the relevant time period for this issue: 🞄 Two or more registered developers had active Account Activity API subscriptions configured for domains that resolved to the same public IP; 🞄 For active subscriptions, URL paths (after the domain) had to match exactly across those registered developers -- e.g. https://example.com/[webhooks/twitter] https://example.com/[webhooks/twitter] and https://anotherexample.com/[webhooks/ https://anotherexample.com/[webhooks/ twitter ]; 🞄 Those registered developers had activity relevant to their subscriptions occur in the same 6-minute time period (relevant because of a cache-like behavior); and 🞄 Those registered developers’ subscribers’ activities originated from the same backend server from within Twitter’s datacenter Under those circumstances, if the bug occurred, the issue (transmission of activities to the wrong webhook URL) could have persisted until one of the following conditions were met: 🞄 For up to two weeks, OR 🞄 Until no relevant activity occurred for 6 minutes, OR 🞄 Until the IP address of the developer whose data was being misdelivered changed