43 years ago Glitch

[Sho]

This happened to me last night, made me giggle

[Chippiewill]

Well its back again... I guess Ive been online for 43 years wheres my badge habbo?.



So yeah Wd habbo once again you messed up

The timestamps were probably getting loaded from their database wrong leaving them as null or 0 aka the UNIX Epoch 00:00:00 1/1/1970 (Rounding is why it says 43 years rather than 42)

[Nick]

The timestamps were probably getting loaded from their database wrong leaving them as null or 0 aka the UNIX Epoch 00:00:00 1/1/1970 (Rounding is why it says 43 years rather than 42)

lolwhat

Anyway they have fixed it haha

[Chippiewill]

A Unix timestamp is the number of seconds since 0:00:00 1/1/1970, lots of computers store the time stuff occurred like this as it's easy to perform calculations on seconds in this case working out how long ago the message was is fairly easy as you minus the seconds of the messages time from the seconds for the current time and you get the number of seconds in between. If the seconds doesn't get loaded properly with the message then it'll be equal to 0 so the system will think the time since the message was 43 years roughly.

[God]

A Unix timestamp is the number of seconds since 0:00:00 1/1/1970, lots of computers store the time stuff occurred like this as it's easy to perform calculations on seconds in this case working out how long ago the message was is fairly easy as you minus the seconds of the messages time from the seconds for the current time and you get the number of seconds in between. If the seconds doesn't get loaded properly with the message then it'll be equal to 0 so the system will think the time since the message was 43 years roughly.

The timestamps were probably getting loaded from their database wrong leaving them as null or 0 aka the UNIX Epoch 00:00:00 1/1/1970 (Rounding is why it says 43 years rather than 42)

Smart people

[Samantha]

A Unix timestamp is the number of seconds since 0:00:00 1/1/1970, lots of computers store the time stuff occurred like this as it's easy to perform calculations on seconds in this case working out how long ago the message was is fairly easy as you minus the seconds of the messages time from the seconds for the current time and you get the number of seconds in between. If the seconds doesn't get loaded properly with the message then it'll be equal to 0 so the system will think the time since the message was 43 years roughly.

This is why some rares on the main site have the release date as that.

They were quick to fix the glitch, nice.

[LiquidLuck.]

This is so annoying. -.- It's fixed now though.