DOITQ: The coincidence is in the timing

Re >>2931038 (pb)

Twitter "media" filenames encode a monotonically increasing number using a 64 character alphabet. They are not a cryptographic hash.

https://twitter.com/realDonaldTrump/status/928325667556548608

https://pbs.twimg.com/media/DOITQJ8UIAAowsQ.jpg

https://twitter.com/realDonaldTrump/status/928286153672970240

https://pbs.twimg.com/media/DOHvQZkX0AEjfL9.jpg

'H' < 'I' ="DOHvQ" < "DOITQ"

Recent filenames start with "DmS" ('O' < 'm' in ASCII).

The coincidence is that POTUS tweeted in the timeframe where Twitter image names started with "DOITQ". A number of images posted on Twitter around the same time also start by the same letters.

So to estimate the (im)probability, we need to know the duration of the "DOITQ" timeframe. Is it seconds, minutes, hours, or days?

>>2933591

This is terrible math, same as saying the odds of tomorrow being 11/9/2018 are 1/10000000.

>>2933472

>>2933591

>>2933614

DOHvQZkX0AEjfL9 https://twitter.com/realDonaldTrump/status/928286153672970240

DOITQJ8UIAAowsQ https://twitter.com/realDonaldTrump/status/928325667556548608

DORdAssVwAA6QGX https://twitter.com/realDonaldTrump/status/928969836897583104

DObaCfAVoAIwVO1 https://twitter.com/realDonaldTrump/status/929670192434745344

Pattern. Need more?

>>2933608

>What are the odds if the timeframe is only minutes?

The odds relate to the probability of a POTUS tweet within that timeframe. It can be mathed. I don't think it's anywhere near one in eighty-two trillion.

>Is there any other info that can be decoded from these filenames?

I don't think so.

If the filenames are just a timestamp, timing could be used to encode information (easy for the first few characters, more timing precision needed to affect later ones).

If the filenames are based on a (possibly distributed) counter, it would be much harder to target a specific number, you'd have to maybe monitor the Twitter firehose API, and know more about the Twitter infrastructure.