the bitcoin clock is now owned by mc_lovin
Topic: Bitcoin clock (Read 7685 times)
LOL, yeah sure, $8M is not enough...
Is your name Ian Grice or Ian Greed?
Ian tries to get rid of that ol' pirate-passthrough story.
Don't expect any reaction whatsoever, no matter where and how you contact him regarding bitcoinmax.
Ente
Sure, and when eventually pirate comes back, we all hug him and everything is forgotten.
And everybody wonders why there are so much scams in the Bitcoin world...
As long as we as a community accept such a behavior we deserve no better.
80 mil sent.
your ideas are intriguing and i'll look into in more detail next time i decide to spend time on the site. As usual it was more of a little hobby site so not really a lot of time to make things complicated. the update for the graphics on the clock face was well overdue, being over a year since i made the original blue and red one.
I'm pleasantly surprised by the open-minded response. I have little experience with programming so cannot say how hard this would be to do. Right now, it seems that the page refreshes temporarily so I think smooth rotation would take more work than its worth. The angle of the second hand would be:
Code:
1 - (1 / 2)^(time_since_last_block / average_time_per_block)
Anyway, consider this a friendly suggestion and notes for the future should you find the time and interest to give this a go.
And thanks Ente for the support
LOL, yeah sure, $8M is not enough...
Is your name Ian Grice or Ian Greed?
Ian tries to get rid of that ol' pirate-passthrough story.
Don't expect any reaction whatsoever, no matter where and how you contact him regarding bitcoinmax.
Ente
LOL, yeah sure, $8M is not enough...
Is your name Ian Grice or Ian Greed?
update! the clock has just had a little makeover.
Nice work. May I send a tip?
I must admit I've never liked the second hand. Each cycle of the hour and minute hands mark a Bitcoin event but a cycle of the second hand only represents an approximation to 24 hours.
I would have a cycle of the second hand represent the addition of a single block. Of course, the classic notion of angle symbolising "progress" toward an event would have to be weakened. I submit the most natural mechanic would be to measure time since the last block, with 10 minutes represented by a half turn, 20 mins by 3/4, 40 mins by 7/8, et cetera. The second hand could then move smoothly. Another consequence is that the position of the second hand at a random time would be uniform, just as with a normal clock. Bonus points for having a more accurate expected block frequency than 10 minutes.
I'm certain the idea of cycles of the second hand representing block creations has been raised before. I can't think of a more elegant way of graphically representing the exotic nature of block-chain activity in a clock than with a smooth and gradually slowing second hand.
tips always welcome at http://payb.tc/donate
thanksyour ideas are intriguing and i'll look into in more detail next time i decide to spend time on the site. As usual it was more of a little hobby site so not really a lot of time to make things complicated. the update for the graphics on the clock face was well overdue, being over a year since i made the original blue and red one.
Hello User25846/E&G/payb.tc/Bitcoinmax/Ian Grice! Wow, you have more names than Atlas...
Does the clock show when you will finally answer in your very own ponzi thread? https://bitcointalksearch.org/topic/m.1582668
Or even better, it should show when you will return the 150k+BTC! For those that did not follow those events, Ian Grice successfully "collected" some $8M+ at todays value...
Does the clock show when you will finally answer in your very own ponzi thread? https://bitcointalksearch.org/topic/m.1582668
Or even better, it should show when you will return the 150k+BTC! For those that did not follow those events, Ian Grice successfully "collected" some $8M+ at todays value...
update! the clock has just had a little makeover.
Nice work. May I send a tip?
I must admit I've never liked the second hand. Each cycle of the hour and minute hands mark a Bitcoin event but a cycle of the second hand only represents an approximation to 24 hours.
I would have a cycle of the second hand represent the addition of a single block. Of course, the classic notion of angle symbolising "progress" toward an event would have to be weakened. I submit the most natural mechanic would be to measure time since the last block, with 10 minutes represented by a half turn, 20 mins by 3/4, 40 mins by 7/8, et cetera. The second hand could then move smoothly. Another consequence is that the position of the second hand at a random time would be uniform, just as with a normal clock. Bonus points for having a more accurate expected block frequency than 10 minutes.
I'm certain the idea of cycles of the second hand representing block creations has been raised before. I can't think of a more elegant way of graphically representing the exotic nature of block-chain activity in a clock than with a smooth and gradually slowing second hand.
Haha I like that idea! ..a gradually slower and slower hand, which will never quite reach "12" by itself, but only when finding a block!
I agree, no better way to show the "odds and variance" thingie of our blocks! :-)
But surely a heck of more complicated to program.
Ente
update! the clock has just had a little makeover.
Nice work. May I send a tip?
I must admit I've never liked the second hand. Each cycle of the hour and minute hands mark a Bitcoin event but a cycle of the second hand only represents an approximation to 24 hours.
I would have a cycle of the second hand represent the addition of a single block. Of course, the classic notion of angle symbolising "progress" toward an event would have to be weakened. I submit the most natural mechanic would be to measure time since the last block, with 10 minutes represented by a half turn, 20 mins by 3/4, 40 mins by 7/8, et cetera. The second hand could then move smoothly. Another consequence is that the position of the second hand at a random time would be uniform, just as with a normal clock. Bonus points for having a more accurate expected block frequency than 10 minutes.
I'm certain the idea of cycles of the second hand representing block creations has been raised before. I can't think of a more elegant way of graphically representing the exotic nature of block-chain activity in a clock than with a smooth and gradually slowing second hand.
Awwwee I thought it was an actual clock 
That's okay still very cool!!
That's okay still very cool!!
it is an actual clock... or do you mean a physical one?
Awwwee I thought it was an actual clock
That's okay still very cool!!
That's okay still very cool!!
Nice! Thanks for your contribution.
Very nice. Easy visual reference for quite a few important stats. Bookmarked!
update! the clock has just had a little makeover.
you may need to hard (SHIFT) refresh the first time you go there.
(i still don't have explicit cache control worked out for individual files)
p.s. could the owner of litecoinclock.com please get in touch? cheers
you may need to hard (SHIFT) refresh the first time you go there.
(i still don't have explicit cache control worked out for individual files)
p.s. could the owner of litecoinclock.com please get in touch? cheers
Nicely done sir.
I have the litecoinclock.com and would love to get it back up.. I had altered it to use ajax calls so there would not be a refresh all the time.. I think moving the minute hand for every block found is a really good idea.
Will try and dig up the code and at least get the old version working soon.
Jim
update! the clock has just had a little makeover.
you may need to hard (SHIFT) refresh the first time you go there.
(i still don't have explicit cache control worked out for individual files)
p.s. could the owner of litecoinclock.com please get in touch? cheers
you may need to hard (SHIFT) refresh the first time you go there.
(i still don't have explicit cache control worked out for individual files)
p.s. could the owner of litecoinclock.com please get in touch? cheers
edit: just for the sake of documenting it here, it is currently estimating 2012-12-05 11:30:22
wow! the eta has crept forward more than 24 hours in just over a week.
if these trends continue, the drop will actually happen in late november, not early december as was most-widely predicted.
Yep.
That's some pretty steep stuff here, huh?
Ente
edit: just for the sake of documenting it here, it is currently estimating 2012-12-05 11:30:22
wow! the eta has crept forward more than 24 hours in just over a week.
if these trends continue, the drop will actually happen in late november, not early december as was most-widely predicted.
I would have the second hand move every time a block is generated.
me too! luckily, it already does this.
But on another tack - does your clock auto adapt the ETA as we get closer to it or do you have to manually set an actual ETA as we approach?
the ETA is calculated every time the page loads. it's not manual... it uses php with that formula i posted above.
yeah even i wouldn't rate it A-
i'm no javascript guru, i just found a clock and tried to modify it to create the right angles.
no idea what to use the second hand for either, so that's why i disabled it
I would have the second hand move every time a block is generated. So you just refresh a static image upon each block. Or add one of those little fast moving little mini-clocks in side the main clock like this super fancy watch below. In fact, why not use a face like this one and have the small sub-face move according to hash rate. i'm no javascript guru, i just found a clock and tried to modify it to create the right angles.
no idea what to use the second hand for either, so that's why i disabled it
But on another tack - does your clock auto adapt the ETA as we get closer to it or do you have to manually set an actual ETA as we approach?
edit: darn it. I just saw this was a resurrected thread... what is up with everyone digging up old threads nowadays? It must be boredom with nothing new actually happening around here. I guess we need a new hack to keep tongues wagging.
You use IE ?? 
IE doesn't support Gopher URLs.
Jump to: