That's quite amazing!
One thing is that the data center ids are in the tweet ids, so it could be used to get a rough location of Twitter users.
One thing is that the data center ids are in the tweet ids, so it could be used to get a rough location of Twitter users.
Then ran it on a few Twitter accounts: https://pastebin.com/w8Dnj5kM
It does work, and it's going to be hard to patch
edit: I realized you don't only get one location but the whole location history of a Twitter user. Also locating Twitter's data centers as it doesn't seem to be public information
I wish it was not so easily fixable, because this will break the key space reduction trick ;), but unfortunately such a solution is feasible and would come with the side-effect of drastically increasing the required scanning space.