Entries this day: humanClockpics

humanClockpics

>This is a semi-canned message from Craig at humanclock.com.
>About 2,254,107 seconds ago (ok...about 26 days), you submitted
>11 photos for the website.
>
>Sorry it took so long to get the pictures into the 
>site.  I had to rewrite all of the code that processes 
>submissions and puts the photos into the clock....but
>things are all better now.  Future submissions to the 
>website will now  only take a few days to put onto the
>site, instead of a few eons.
>
>Here is a rundown of what I did with your 11 photos:
>
>(dude_1143.jpg) * put into the website as 11:43 pm *
>(dude_1145.jpg) * put into the website as 11:45 pm *
>(dude_1151.jpg) * put into the website as 11:51 pm *
>(rob_1100.jpg) * put into the website as 11:00 pm *
>(rob_1143.jpg) * put into the website as 11:43 pm *
>(rob_1144.jpg) * put into the website as 11:44 pm *
>(rob_1145.jpg) * put into the website as 11:45 pm *
>(rob_1146.jpg) * put into the website as 11:46 pm *
>(rob_1148.jpg) * put into the website as 11:48 pm *
>(rob_1150.jpg) * put into the website as 11:50 pm *
>(rob_1150_v2.jpg) * put into the website as 11:50 pm *
>
>
>
>Quick note concerning accepted photos:
>
> Your photo(s) shares a timeslot with other photos,
> so it might not always come up at the specified time.  If
> the clock has more than one photo for a given time, it chooses
> a picture at random.  If your photo does not come up, hit 
> reload/refresh on your browser during that minute and it
> should come up eventually.  If it doesn't come up at all
> when I said it would, write me and tell me I need to write
> better code or something.