Not enough people are advertising the site I guess. Either that, or people just don't want to participate.

I'm thinking it could be interesting to have a reverse style bubble, where the last advertisement is on top, and pushes the others down. So whoever has the last bid gets the most viewed ad. Could also make it so new bids only reset the timer if they are greater than or equal to the previous bid.
Not real sure right now, some ideas are floating around. If I get enough ideas I may create a site :-/

*EDIT* Traded, no longer available.

Thanks to kpriess for the trade of 0.5 BTC

Well, I'm bored and my Bank has imposed a new rule where inactive checking accounts will be charged a fee.
So... I've decided to use my PayPal and DWOLLA account to let people transfer money into MtGox, then they can exchange it for bitcoin themselves.
I will not impose any fee (except any given by PayPal or the $0.25 DWOLLA fee.) (However bitcoin donations would be appreciated after a successful transfer.)

The catch? Time. You'd have to wait about a day for the paypal funds to show in my bank, and then I believe MtGox has like a 12 hour window for verifying incoming payments.

If you're interested, click my signature for my email, and we can work out the details.
Thanks for your time.


*EDIT*
After reviewing options, it doesn't appear as if this is something people would be interested in. However, I'll leave this post here just in case some random person stumbles upon it and sees it as the best option for their needs.

I emailed an offer, however the delivery failed.

Just one thread. I don't currently have my pc set up to compile the source, so I can't really give any details of what thread :-/

Anyway, I'm able to cause this issue just by using the RPC getwork command. Calling it once causes the RPC server to just start running full cpu usage (Quad Core, 25%, one thread.) And the only way for me to "fix" it is to force the process to end and restart bitcoin :-/

If there's any more info you need, please elaborate...

Hmm.
Windows 7 Pro x64
When I start my local miner, bitcoin.exe goes up to a constant 25% CPU usage (Quad Core) Even after closing phoenix, and bitcoin, the process remains (at 25% CPU) until I manually terminate it.

No issues with 0.3.21 though. Any ideas?

I was considering buying an ad pack (guess I would have been the first, since it showed 0 upgraded members)... now the site just vanishes. Glad I didn't waste my bits :-|

Loads near instantly for me.

Only loads in FF4 and Chrome 11.
IE9 and Opera 11.11 aren't displaying it for me. Not sure how much HTML5 support they have though :-/

I'm just a FF whore (mainly due to the addons I've become accustom to.)

Shows for me on Chrome 11.0.696.68
Also, the scroll wheel does zoom in Chrome... doesn't seem to work in Firefox 4, though it could be due to an addon.

Not via scroll wheel.

Up and Down arrows work, but it's basic. No detail enhancement.

*Edit* Put the wrong keys lol

The correct link is: http://www.weusecoins.com/globe-bitcoin/
And you can spin it manually by clicking and dragging.

Hm. Someone got a bubble within 30 seconds of the timer expiring...
Unless this loses interest, I don't see it ending anytime soon lol.

Question though, what logic is there behind submitting a bubble at the end of the timer? If you want to win the jackpot, wouldn't it make more sense to buy a bubble asap after someone else. That way they are less likely to notice, and you have less time for someone else to jump in? Or maybe people are trying to keep it going? I'd like to get in on a new round seems like it would be more active then.

Anyway, just a stupid thought I had as I woke up at 3AM and decided to check the sites :-/

Just for my own curiosity, would you mind making a copy of your script, stripping out anything that shouldn't be seen, and sending me a copy? I'd like to see just what would be involved to implement something like this.

If that's too much of a hassle, or you have 'private' code that you don't want exposed, I understand. This would be more like a "play thing" for me, so I have no real expectations :p

Spam eh... I probably used my throw-away yahoo. I always use it when I'm not sure where my message will go ;-)
Gmail is my primary.

Anyway, I wasn't expecting you to switch over to BC Math, I understand that would cause more trouble than it's probably worth... just a thought for future projects I guess.

Thanks for taking the time to keep us informed. I look forward to the outcome of this site.

Glad to hear an update rather than just waiting for something to happen.

About the numbers, couldn't you use BC Math? It's been a long time since I used it, but my understanding was that it allowed for numbers as strings, so insanely high values could be computed.

Also, I emailed the 'support', but never heard anything back.. I just had a small idea, could you implement a small counter for each drawing to show how many blocks until the draw? I'm lazy (or stupid, however you prefer to pronounce it) and instead of looking at the current block number via blockexplorer/my rpc and doing a quick subtraction, it'd be much quicker to just glance at your page and get the number of blocks in one step.

Anyway, thanks for taking the time to read this, and for filling us in on what you're doing in the background!

First "week" was a low turn out... hope you keep it going though, could become interesting.

Just an idea, but wouldn't it be a bit more interesting if the timer only resets if the last payment bursts a bubble?
Thoughts? Concerns?

Thanks for taking the time to read my idea :-)

Small request... but could you please add a display for an "efficiency" ratio/percentage? It's easy to just glance at accepted/rejected, but I'd like to see a comparison of "get works" vs accepted.
Currently I have to manually count how many times the log prints that it received new work, then compare that to the accepts and rejects (rejects have been very rare as of the new version.)

Also, probably a dumb question, but when I load the miner, I get a double request... is this something that can be addressed, or is it a server-side issue?

Example:
I always get new work after a new block, but there's always a 'new' block after I start the app.

Also... could there be a way to dump a temp file on close, so if you're just restarting, it can resume the work unit it had previously instead of requesting a new one? Most likely I'd expect it would be timestamped, and ignored if older than a few seconds. One such instance where this is useful is when you release a new version and I want to close out, extract the new files, then relaunch it.

If I was on a linux box, I'd just manually edit the source and merge with your svn changes, but since I'm on windows I am relying on your binary. I'll probably end up just learning the basics of python and compiling this myself, but for now I'm just being lazy and hoping you'd be kind enough to consider these modifications. Especially since it may benefit people other than myself.

Thanks for your time, sorry if I'm incoherent, drowsy from allergy meds about to pass out :-|

Thanks for the input, but this is irrelevant to my question. I know I'm not using a great mining card, but this is what I have, and it's better than nothing.

My question was to the concern of closing the console window via WM_CLOSE causes the video driver to basically cut performance in half, and requires a restart of the driver.
While simply terminating via Ctrl+C closes out cleanly. I'm a C++ dev, and not familiar with python, so I'm not sure if this is just an issue with the windows compiled binary, or if the cleanup code is missing something.

Either way, it's not an important issue (since I have the work-around method), but I do like to know 'why' stuff happens, not just that it does :-/

Thanks for your time.

Slightly confused here... Running a GTX260 (216 core) at about ~50Mhash/s on Windows 7 Professional 64bit.
If I close the console window, then relaunch the miner, my hash rate maxes around ~25Mhash/s (halves)

To fix this, I have to reboot (or, because I'm impatient, disable then re-enable the videocard via device manager.) I'm then back to full hash rate.
However, if I simply break execution of the program (via Ctrl+C), it seems to terminate properly and when relaunching I remain at the full hash rate.

Clearly, the simple answer is to always just terminate it via Ctrl+C... but I'm curious if anyone knows 'why' it seems to crash the video drivers by just closing the console window?

Thanks for any input :-/