5 ms·
It's probably because modern tweet IDs are larger than a 32-bit integer. Presumably some JSON parsers aren't too hot on parsing bigints, so they give you the op
by russss 14y ago
It's probably because modern tweet IDs are larger than a 32-bit integer. Presumably some JSON parsers aren't too hot on parsing bigints, so they give you the option of having a string instead.
- napoleond 14y agoAhh, that makes sense. Thanks! (And thanks to andrewf as well!)