Which would be 10000 days inclusive of May 14. (Wolfram says in this case that it was Sept. 29, which is correct. (ie Mark is celebrating the wrong day. But kudos to him for being aware of it in the first place. I celebrated mine July 23.))
The like updates are timed improperly and the number keeps going down and then up and then down. I got a lot of shit at work for a similar bug on a JS ticker, I'm glad I'm not the only one!
Doing a little network sniffing this seems incredibly inefficient. Apparently the page is polling the server up to 8 times per second and getting back a 7-800 byte chunk of Javascript. The infrastructure to support this at Facebook's scale is mind boggling. This is the kind of stuff that Websockets was invented for.
web sockets or, in most browsers, long polling. long polling is easy to implement and they must already have the infrastructure built out since they have chat...silly Facebook.
[edit]
just took a closer look at the network activity. this really is the worst way to implement this feature. polling several times a second, sending back a bloated response, and updating much more of the DOM than necessary. this is just terribly hacky. probably done very quickly at the last minute though.
It has done the exact same thing for my friends posts for a looooong time. This isn;t specific to his account, its just more prominent because there are more people "liking" it.
If they keep adding people at the rate they are, in 10 years they'll have wired together the entire human race. I'm not sure if I should be scared or thrilled or skeptical.
[+] [-] ahupp|14 years ago|reply
https://www.facebook.com/note.php?note_id=496077348919
[+] [-] schlichtm|14 years ago|reply
This is different. Facebook is showing the actual like count change in real time. This is fantastic feedback for big brands.
[+] [-] staunch|14 years ago|reply
http://www.wolframalpha.com/input/?i=May+14%2C+1984+to+today...
[+] [-] baddox|14 years ago|reply
[+] [-] baddox|14 years ago|reply
http://www.wolframalpha.com/input/?i=May+14%2C+1984 shows it being 10,000 days ago (if you view it before midnight on the 1st), but performing explicit ranges shows a different number.
[+] [-] hennypenny|14 years ago|reply
Which would be 10000 days inclusive of May 14. (Wolfram says in this case that it was Sept. 29, which is correct. (ie Mark is celebrating the wrong day. But kudos to him for being aware of it in the first place. I celebrated mine July 23.))
[+] [-] orijing|14 years ago|reply
It says 9855 days, which is 365 * (2011 - 1984), which is obviously not right and missing leap years.
[+] [-] biot|14 years ago|reply
http://www.wolframalpha.com/input/?i=days+since+May+14%2C+19...
[+] [-] ptarjan|14 years ago|reply
http://nerdiversary.com/1984-05-14
[+] [-] kalleboo|14 years ago|reply
[+] [-] nicholasreed|14 years ago|reply
[+] [-] guelo|14 years ago|reply
[+] [-] kwamenum86|14 years ago|reply
[edit] just took a closer look at the network activity. this really is the worst way to implement this feature. polling several times a second, sending back a bloated response, and updating much more of the DOM than necessary. this is just terribly hacky. probably done very quickly at the last minute though.
[+] [-] DiabloD3|14 years ago|reply
[+] [-] chunkyslink|14 years ago|reply
[+] [-] rehashed|14 years ago|reply
[+] [-] unknown|14 years ago|reply
[deleted]
[+] [-] unknown|14 years ago|reply
[deleted]
[+] [-] cellis|14 years ago|reply
[+] [-] hack_edu|14 years ago|reply
[+] [-] jarin|14 years ago|reply
[+] [-] plainOldText|14 years ago|reply
[+] [-] william42|14 years ago|reply
[+] [-] zem|14 years ago|reply
[+] [-] charliesome|14 years ago|reply
[deleted]
[+] [-] indigoviolet|14 years ago|reply
[deleted]
[+] [-] NHQ|14 years ago|reply