for browser mining you need a webgl compatible browser
Not for cpu mining. You can do that with javascript.
Topic: Posturing (Read 1188 times)
Let me guess, you were watching on Mtgoxlive or something using the same feeding method.
This is one of two known bugs. Ignore it, it didn't happen. The two bugs are on new changes: one does and undoes them frequently, the other adds it twice, then undoes it a few iterations later.
Don't trust these order book pages, they're written by people who think it's funny to never do any sanity checks, never correct the view and induce extra madness. Best proof: the scale on the right side of Mtgoxlive. Come on, after seeing that, it's your fault for taking the site all too seriously. And the CPU usage should remove any remaining doubt of the joky nature of the page. It's CPU mining, isn't it? I hope so, because it's the only sane explanation for the performance.
I kinda miss Bitcoinity. That one was slower in updates, but fairly decent in what it displayed.
This is one of two known bugs. Ignore it, it didn't happen. The two bugs are on new changes: one does and undoes them frequently, the other adds it twice, then undoes it a few iterations later.
Don't trust these order book pages, they're written by people who think it's funny to never do any sanity checks, never correct the view and induce extra madness. Best proof: the scale on the right side of Mtgoxlive. Come on, after seeing that, it's your fault for taking the site all too seriously. And the CPU usage should remove any remaining doubt of the joky nature of the page. It's CPU mining, isn't it? I hope so, because it's the only sane explanation for the performance.
I kinda miss Bitcoinity. That one was slower in updates, but fairly decent in what it displayed.
CPU usage is caused by JS engine in a browser which constantly updates the page. before suggesting CPU mining check page's html and js sources. from what i remember seeing some other sites in the past implementing browser miner - browser would throw a red flag notification that something maybe going on in the background and whether you want to proceed or not.
The fan on my poor little netbook goes into hyper-drive when I use mtgoxlive.
Let me guess, you were watching on Mtgoxlive or something using the same feeding method.
This is one of two known bugs. Ignore it, it didn't happen. The two bugs are on new changes: one does and undoes them frequently, the other adds it twice, then undoes it a few iterations later.
Don't trust these order book pages, they're written by people who think it's funny to never do any sanity checks, never correct the view and induce extra madness. Best proof: the scale on the right side of Mtgoxlive. Come on, after seeing that, it's your fault for taking the site all too seriously. And the CPU usage should remove any remaining doubt of the joky nature of the page. It's CPU mining, isn't it? I hope so, because it's the only sane explanation for the performance.
I kinda miss Bitcoinity. That one was slower in updates, but fairly decent in what it displayed.
This is one of two known bugs. Ignore it, it didn't happen. The two bugs are on new changes: one does and undoes them frequently, the other adds it twice, then undoes it a few iterations later.
Don't trust these order book pages, they're written by people who think it's funny to never do any sanity checks, never correct the view and induce extra madness. Best proof: the scale on the right side of Mtgoxlive. Come on, after seeing that, it's your fault for taking the site all too seriously. And the CPU usage should remove any remaining doubt of the joky nature of the page. It's CPU mining, isn't it? I hope so, because it's the only sane explanation for the performance.
I kinda miss Bitcoinity. That one was slower in updates, but fairly decent in what it displayed.
+1 on MTGOxLive. I can't believe that in 2012 it is still impossible to display a live graph on the screen.
I used to have issues with Bitcoinity too though, always messing up the graphs.
Let me guess, you were watching on Mtgoxlive or something using the same feeding method.
This is one of two known bugs. Ignore it, it didn't happen. The two bugs are on new changes: one does and undoes them frequently, the other adds it twice, then undoes it a few iterations later.
Don't trust these order book pages, they're written by people who think it's funny to never do any sanity checks, never correct the view and induce extra madness. Best proof: the scale on the right side of Mtgoxlive. Come on, after seeing that, it's your fault for taking the site all too seriously. And the CPU usage should remove any remaining doubt of the joky nature of the page. It's CPU mining, isn't it? I hope so, because it's the only sane explanation for the performance.
I kinda miss Bitcoinity. That one was slower in updates, but fairly decent in what it displayed.
This is one of two known bugs. Ignore it, it didn't happen. The two bugs are on new changes: one does and undoes them frequently, the other adds it twice, then undoes it a few iterations later.
Don't trust these order book pages, they're written by people who think it's funny to never do any sanity checks, never correct the view and induce extra madness. Best proof: the scale on the right side of Mtgoxlive. Come on, after seeing that, it's your fault for taking the site all too seriously. And the CPU usage should remove any remaining doubt of the joky nature of the page. It's CPU mining, isn't it? I hope so, because it's the only sane explanation for the performance.
I kinda miss Bitcoinity. That one was slower in updates, but fairly decent in what it displayed.
CPU usage is caused by JS engine in a browser which constantly updates the page. before suggesting CPU mining check page's html and js sources. from what i remember seeing some other sites in the past implementing browser miner - browser would throw a red flag notification that something maybe going on in the background and whether you want to proceed or not.
I saw the ask wall going up and down on btccharts.com and bitcoin.clarkmoody.com. Didn't check the buy wall on clarkmoody, it was pretty brief. Doesn't mean it wasn't a glitch, of course.
And the CPU usage should remove any remaining doubt of the joky nature of the page. It's CPU mining, isn't it? I hope so, because it's the only sane explanation for the performance.
has someone checked this?! This would be such a K.O. for me. Mining with my nice little hot CPU.
Let me guess, you were watching on Mtgoxlive or something using the same feeding method.
This is one of two known bugs. Ignore it, it didn't happen. The two bugs are on new changes: one does and undoes them frequently, the other adds it twice, then undoes it a few iterations later.
Don't trust these order book pages, they're written by people who think it's funny to never do any sanity checks, never correct the view and induce extra madness. Best proof: the scale on the right side of Mtgoxlive. Come on, after seeing that, it's your fault for taking the site all too seriously. And the CPU usage should remove any remaining doubt of the joky nature of the page. It's CPU mining, isn't it? I hope so, because it's the only sane explanation for the performance.
I kinda miss Bitcoinity. That one was slower in updates, but fairly decent in what it displayed.
This is one of two known bugs. Ignore it, it didn't happen. The two bugs are on new changes: one does and undoes them frequently, the other adds it twice, then undoes it a few iterations later.
Don't trust these order book pages, they're written by people who think it's funny to never do any sanity checks, never correct the view and induce extra madness. Best proof: the scale on the right side of Mtgoxlive. Come on, after seeing that, it's your fault for taking the site all too seriously. And the CPU usage should remove any remaining doubt of the joky nature of the page. It's CPU mining, isn't it? I hope so, because it's the only sane explanation for the performance.
I kinda miss Bitcoinity. That one was slower in updates, but fairly decent in what it displayed.
when the slope down to around 6.4 occurred, there was a wall on the ask side, just above the bid prices, of about 1500 BTC being taken up and down continuously. Now there's one, about 1500 BTC, going up and down all the time on the bid side. Glitchy data, or something else?
Something else. Somebody is having a bit of fun today.
when the slope down to around 6.4 occurred, there was a wall on the ask side, just above the bid prices, of about 1500 BTC being taken up and down continuously. Now there's one, about 1500 BTC, going up and down all the time on the bid side. Glitchy data, or something else?
Jump to: