Why is it impossible to determine tweet time from the id? The snowflake github page says that the first 41 bits are the “timestamp with custom epoch”, (appears to be 1288834974657L, or November 3rd 2010), which would imply the ts is recoverable.
However, the first 41 bits of 95178332215312385 are 1452306094594, which is 46 years! That’s in the future relative to unix time zero, let alone the custom epoch. Was my math wrong? Is it not possible to recover the time this way? We use a rotating collection of recently seen tweet ids in our app to minimize requests to the API, and it would be very helpful to determine approximate time/ordering from these.