43 years ago Glitch

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

http://i50.tinypic.com/29yqbsz.png

So yeah Wd habbo once again you messed up

Its just a glitch, not Habbo messing up, for some reason it's resetting to unix time.

Some glitch are freaky and woo you were talking to Luke

lol why did you go over his name when we could see in anyway?

o/t yeah i seen this last night. I has happened before and its been fixed so im sure it will be fixed soon haha

Yeah agree with @Nick; why do that :P?

Anyway, bit of a silly glitch but I won't lose sleep over it.

Quote:

---

Originally Posted by Nick

lol why did you go over his name when we could see in anyway?

o/t yeah i seen this last night. I has happened before and its been fixed so im sure it will be fixed soon haha

---

Well I was told by someone we needed to cover their name.

And didnt even notice the tiny print below stupid me

Quote:

---

Originally Posted by Dragga

Well I was told by someone we needed to cover their name.

And didnt even notice the tiny print below stupid me

---

I think that's if you're naming scammers/hackers etc. :).

Such a funny glitch imo :P. Habbo hasn't even been around for 43 years xD.

Wait why does it do that anyways? you think if habbo fixed it once it wouldnt happen again...

Quote:

---

Originally Posted by Dragga

Wait why does it do that anyways? you think if habbo fixed it once it wouldnt happen again...

---

They might have updated something or backtracked which either set off the glitch again or restored it.

This happened to me last night, made me giggle :P

Quote:

---

Originally Posted by Dragga

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

http://i50.tinypic.com/29yqbsz.png

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)

Quote:

---

Originally Posted by Chippiewill

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

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.

Quote:

---

Originally Posted by 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.

---

Quote:

---

Originally Posted by Chippiewill

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

Quote:

---

Originally Posted by 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.

---

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

They were quick to fix the glitch, nice.

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