Not implying this is the case AT ALL, but wouldn't it be an epic scam if Inaba gave a down-to-earth review proving that the magic box works as described, several hundred orders roll in at full price, then it turns out he was in cahoots..... Again, I'm not even suggesting this is the case, I just let my mind wander.  |
|
|
|
The software will support Linux, Windows and I believe Mac.
I am reviewing the driver source code prior to compiling it for tomorrows test as we speak. I don't know how much or little BFL wants me to talk on the subject at the moment, so I am not providing any additional information. But to the best of my knowledge at this point, the live demo is still on tomorrow evening CST at my data center. They've already OK'd me to keep a unit overnight for further testing at another location. I will inquire as to if they mind if I disassemble the unit and take pictures as well, presuming the tests go as BFL expects tomorrow.
Have you signed an NDA with them? Have you met them in person yet? |
|
|
|
it's even crashed one time...
Start a new thread with debugging information so that it can be fixed. |
|
|
|
Trying to figure if javascript and php is good enough for an idea I have, and if not, what language(s) I need.
A player clicks something which modifies the database, immediately the values from the database that were showing on the page are updated, no page refresh needed.
Another player who is currently viewing the same values on their page also needs to be instantly updated.
What is it best and will scale well? Database of ~10k players, several hundred logged in, ~50 columns if any of that matters.
And what about handling a "who pressed first" scenario? I don't really care if it is super accurate, just that it can pick one winner. I think this part is trivial, just want verification.
Didn't want to bog down with details, let me know if more is needed.
You can easily do all of that with Javascript to make an AJAX call to the back end PHP script to update the database. The who pressed first scenario is easy in that the first one to update the database wins. The only iffy part is updating all other players' pages. Another player who is currently viewing the same values on their page also needs to be instantly updated.
Being stateless, the HTTP can't handle push notifications from server to client. The way this is typically handled in Javascript is to set a timeout and poll the server for updated values at a given interval. If things don't have to be instantaneous, this works well. If you want instant or near instant updates, then you would have to poll the server for updated information every second or every 500 ms or so. If you have lots of online users, this can be a bottleneck unless you beef up your web server and database server to handle all the poll requests. |
|
|
|
|
They could even stage a break-in and call the local cops. And it might be reported in the local crime blotter as proof for us.
|
|
|
|
|
The main problem is causing the block chain to grow a lot larger than it should be.
|
|
|
|
For all you solo mining haters, I hit three blocks so far this month at 3.8 ghash. Still worth solo mining.
You should immediately switch to a pool. Do it while you're ahead. |
|
|
|
|
Now I just have to pay off a mod to lock the thread and then wait. :evil:
|
|
|
|
Does 6/1 mean january 6 (which is what I assumed) or June 1? I heard americans like to use MM/DD format.
June 1, lol I could be giving away $5000! Or $0.25 you never know. |
|
|
|
For people playing with multiple wallets/clients: * open/close wallet(s), switch between wallets, merge/split wallets, transfer keys/coins between wallets. * import different wallets from other clients. * import/export keys, purge keys (for example, after an export). Of these, using multiple wallets and importing from other clients should be a priority. I'm just sorry my GUI development skill are non-existing  . Yes!!! |
|
|
|
|
Yes, this confused me a bit at first. But you also have to pay attention to what you're doing.
Hopefully the UI will improve from where it is now.
|
|
|
|
|
I think he means spamming the block chain with thousands of tiny (in coin value) transactions to bloat it (and cause other problems that come as side effects).
|
|
|
|
this would simplify the life a lot.
Yes it would. |
|
|
|
This might blow some of y'alls minds, but I just dropped a Smiley in this bizznatch..>ON MY FIRST POST. Don't be jelly, but feel free to provide applause and adulations my way. Now that's an original intro. |
|
|
|
|
teflone-- are you running bitcoin.exe or bitcoin-qt.exe?
|
|
|
|
|
Because they believe in it.
|
|
|
|
If there are limitations resulting from the way transactions and the blockchain works, then that is just something we need to deal with.
Unless my understanding of Bitcoin is way off, I don't know if they can be dealt with, without completely changing the bitcoin protocol. If I have 100BTC at address X and I send you 1BTC, then 99BTC gets sent back to me via a "change" address. All Bitcoin sees is 100BTC going to 2 addresses, how is it supposed to know to only charge the fee on 1BTC as opposed to the full 100BTC? |
|
|
|
|
Show Posts
