It’s not the overflow that’s the issue, but a calculation failure that causes the date value to be “0” and thus list the date as January 1, 1970. It’s happened to me several times with Pokemon GO.
But yes, some programs erroneously fall back to 0 in case of a null value, which corresponds to 1970-01-01. That’s why so many geotags were recorded for Null Island.
It’s not the overflow that’s the issue, but a calculation failure that causes the date value to be “0” and thus list the date as January 1, 1970. It’s happened to me several times with Pokemon GO.
In this case, it is the overflow as
01111111...11111111+1in binary becomes10000000...00000000.But yes, some programs erroneously fall back to
0in case of anullvalue, which corresponds to 1970-01-01. That’s why so many geotags were recorded for Null Island.Fuck the specs. If Pokemon GO says it, that’s good enough for me.