You just got super unlucky. The bounty value was changed a few seconds before you click 'Send'. Because of this I've sent 0.015 BTC to your sig address  Thanks! |
|
|
|
|
There might be a bug.
I just visited your site and it offered 0.011btc so I typed in the captcha. I wasn't sure if one of the letters was a "I" or "l" so of course I typed in the wrong one.
When it told me that the captcha was incorrect, I entered the new one but then got the error message "Invalid amount" instead. I tried a few times but always got the same error.
I reloaded then, but now I only get 0.001btc.
|
|
|
|
|
At least three.
I noticed that my old client (0.3.x) was stuck at 176947 too when I was waiting for an incoming transaction. A backup only updated to the same block too.
Bitcoin had been closed normally before, no crash or anything.
Downloading the nightly blockchain snapshot and running bitcoin with the rescan option fixed the problem and the client just finished updating the last few missing blocks.
Seems like that block somehow differs from all the others.
|
|
|
|
i think alakim may be right about the point values degrading. It used to be "For a given Search Query, how relevant are the 30 shown items?" for 12 points. Now its "For a given Search query, how relevant are the 36 shown items?" for 8 points. Oh well, Im still gonna do it anyways...
They are just testing how low they can go until users quit working. The pay already is very low, even when they offer more points. I refuse to do any of those offers because the work required doesn't justify it, not even if you just do it to waste some time. That aside, crowdflower doesn't seem to be very interested to help users who complain either. Their support forum has quite a few posts from people who ran into problems and only a minority gets answers. |
|
|
|
|
Similar to what jim618 already suggested:
- file down the 4 edges of the back (opposite site of the plug) to remove the backside
- file down one of the long edges
- now you should be able to carefully pry the cover open since it doesn't seem to be glued in
If all goes well, you'll have the PCB now. Guessing from the pictures, the USB plug-angle suggests the PCB there is broken. I'd use a very fine saw to cut it off completely (after making detailed pics).
Fortunately, USB itself is pretty forgiving and it shouldn't be much trouble to solder a few thin wires in to act as a bridge between the plug and the PCB tracks. Worked fine for me when someone I know did exactly the same (he had a plastic case that was easy to open though).
Plug it back in and hope for the best. In case of success, teach your sister about the importance of backups. In case of failure, she learned her lesson the hard way.
Depending on how important the data is, it might also be a case for a professional data rescue service.
Also, before throwing the leftovers away, destroy it physically ("Hammer, meet PCB") since it contains financal data.
|
|
|
|
|
Add a button that lets the player donate the prize to you.
I'd let you keep a price now and then if I could.
|
|
|
|
LOL! Those "hundreds" do not give flying fuck what you write and most of them are bots and porn spammers. What is the point? (this was a rhetorical question)  From your site: I’ll follow you on twitter for 2 BTC, until your tweets get too boring for me.
|
|
|
|
I understand that upgrading hardware and operating systems is expensive but why make it worse by adding hosting a bitcoin node as one of the functions that this server performs?
Hopefully you aren't storing more than two bitcoins on that box.
I know I should, but I just don't have the time to migrate everything to a new system. With some luck I can do it in my next vacation. Simple version:
No and even if/when they exist you will only be able to prune spent outputs.
Even that would compact the blockchain nicely. This doesn't quite answer your question, but you only need to back up the wallet.dat file, which should be quite small. The rest could be downloaded again from the network if lost.
True, but it would take really long for me, so adding the blockchain to the backup is the fastet restore option. |
|
|
|
Are you running the latest (0.6)? It has improvements with regard to the database.
Not on the server in my Lan which has the client running. It still runs on W2k, and the new versions don't work on that anymore sadly. |
|
|
|
|
Is there any tool around which compacts the blockchain, or prunes transactions older than x days?
My Bitcoin folder is a little over 1.5GB now, and the automatic daily backups start to get noticeable.
Also, is there a way to reduce the heavy disk I/O? It's annoying on harddrives, and it will wear down Flash based drives faster.
|
|
|
|
I think you might have a bug. When I break a crate, the page telling me the amount says that I need at least 0.0025btc before it's paid out. After trying it two times, I received each 0.001btc I won to the same address in two transfers. Perhaps you can add an option so that a user can check his current balance and request a transfer if a certain minimum is reached? I would not mind leaving the coins I won in your care until I request them  |
|
|
|
thank you! these bugs & dead links have been fixed
please create an account on thebitcoinreview.com, poke around, write some reviews.
post your efforts on this thread and your account will be credited
If you don't mind, you can simply use the BTC address in my signature |
|
|
|
I agree. 0.4 is a little high, 0.2 BTC threshold would work better.
I don't understand why any payment is held until a certain level is reached. If someone only wants to do one task to try it out why shouldn't they be paid for it? That's better than receiving a tiny amount every few mins while you spend your time doing tasks. Perhaps there will be an option to request a payment at some point, but for now the 200 point minimum is fine. |
|
|
|
|
I tried a few tasks yesterday and received a couple of small transactions. Per se that's great, but at the same time it clutters up my client.
I'd definatively would use it more if I could trigger the payment myself, or if you'd switch to a daily transfer.
|
|
|
|
i agree. i find the way it's set up at the moment to be quite spammy.
sure they save on tx fees by using sendmany. but you're almost guaranteed to have tx fees yourself when you go to consolidate all those tiny inputs.
would be much better if you could let your balance accumulate.
He can still save tx fees. Just replace "pay now" with "request payment" and he could wait for a bunch of requests; and if notbody else does a request in eg 6 hours, send a single tx. I mean, we're talking about cents here. It's not like waiting for a payment would ruin your financial existence. Heck, even a single payout at midnight would be ok with me. |
|
|
|
|
Looks good so far. I hope there are more tasks than just those few.
Personally, I'd like it if there was some sort of "pay now" button on the activity page. All those little transactions make it hard to keep track. So a user could collect points/coins over some hours/days and then request a payment. Of course such a button could be pressed by anybody, but worst thing that could happen is receiving a payment. Adding a captcha would help there.
|
|
|
|
The system has a IP range filter, so it blocks some IPs from receiving payment.
Only IPs from eg open proxies, or could a "normal" user end up on the filter too (by reloading)? What brings me to my next question: Is the payout always the same, or can a user reload and get a bigger payment, like at Dailybitcoins? |
|
|
|
|
Something that should be pointed out: using * in queries is generally a bad idea. Fetch the columns you need, not everything.
(Yeah I know I've been lazy in my examples too)
|
|
|
|
You could always write a function if you need this more than once. function mysql_fetch_all($q) {
$r=array();
while ($tmp=mysql_fetch_array($q, MYSQL_ASSOC)) { array_push($r, $tmp); }
return($r);
}
function mysql_fetch_all_query($q) {
$q=mysql_query($q);
$r=array();
while ($tmp=mysql_fetch_array($q, MYSQL_ASSOC)) { array_push($r, $tmp); }
return($r);
}
$id=mysql_query('SELECT * FROM miners');
$tmp=mysql_fetch_all($id);
print_r($tmp);
// or
$tmp=mysql_fetch_all_query('SELECT * FROM miners');
print_r($tmp);
Of course this could be made prettier, but bascially it's working. |
|
|
|
|
Show Posts
