Or place your coins in a coinlenders CD and earn interest 
But CoinLenders is only 20% per year. PrimeDice is at minimum 1% per roll (roll over 2). hehehe. But you're right, when I get more coins, I'm going to put some there as well.
Topic: Primedice.com | Since 2013 | Longest Running Crypto Casino | 113 BTC Jackpot! - page 1628. (Read 1989554 times)
June 08, 2013, 08:50:22 AM
But CoinLenders is only 20% per year. PrimeDice is at minimum 1% per roll (roll over 2). hehehe. But you're right, when I get more coins, I'm going to put some there as well.
June 08, 2013, 08:14:44 AM
Or place your coins in a coinlenders CD and earn interest
June 08, 2013, 06:48:08 AM
Maybe you could set options for how slow & fast you want the rolls to be 
This was my first thought, too.
I had a funny idea: allow the player to set the roll delay to anything they like. Then they can set it to "24 hours" for a self-enforced break from the site. It would effectively tie up their account, preventing them from losing their funds. "Sorry, you still have a roll in progress - 23 hours until it completes". For those people who just can't help themselves, but are capable of moments of strength...
A good feature all sites should consider imho
June 08, 2013, 03:49:21 AM
Maybe you could set options for how slow & fast you want the rolls to be
This was my first thought, too.
I had a funny idea: allow the player to set the roll delay to anything they like. Then they can set it to "24 hours" for a self-enforced break from the site. It would effectively tie up their account, preventing them from losing their funds. "Sorry, you still have a roll in progress - 23 hours until it completes". For those people who just can't help themselves, but are capable of moments of strength...
June 08, 2013, 12:01:50 AM
Maybe you could set options for how slow & fast you want the rolls to be
This was my first thought, too.
If there's a demand for it I'd look into adding something like that but it seems pretty unnecessary. I feel like roll speed if reasonably fast is simply something people subconsciously think about.
June 07, 2013, 08:15:57 PM
Maybe you could set options for how slow & fast you want the rolls to be
This was my first thought, too.
June 07, 2013, 07:07:27 PM
That's possible, I haven't seen that result at all, it seems to not like our copy paste button. 
It's on a new laptop with on-board Radeon graphics. I run Linux, and it does seem to be a video card driver issue. I switched from the open source driver to the proprietary one and the problem fixed itself.
Note: Roll speeds boosted again
Do you have any players saying the rolls are too fast?
I've been working on a dice game and initial feedback I've gotten is that it's too fast. Gamblers like a second in which to stress about whether they're going to win or loss. Instant feedback apparently takes away the fun. I hadn't thought of that, but maybe I'm going to have to put in a delay - it seems maybe there's a sweet spot - too slow and it's frustrating, but too fast and it doesn't feel like gambling?
From what I've seen it depends on the player. Users that bet small amounts for fun generally like the quick rolls, but someone who is betting big usually likes a bit of suspense to build up. It's hard to find the "sweet spot" because each person prefers something different. Best bet would be to go for somewhere in-between those two points. Consistency of speed is probably more important than the actual speed though in my opinion.
I much prefer the slow rolls when I'm betting 'big' (Well to be fair, I only bet big when rolls are going slow
), but when I'm just playing around messing with 0.1 BTC or something, slow rolls is insanely annoying. It's a really hard one to figure out I'm assuming. Maybe you could set options for how slow & fast you want the rolls to be June 07, 2013, 05:59:29 PM
That's possible, I haven't seen that result at all, it seems to not like our copy paste button.
It's on a new laptop with on-board Radeon graphics. I run Linux, and it does seem to be a video card driver issue. I switched from the open source driver to the proprietary one and the problem fixed itself.
Note: Roll speeds boosted again
Do you have any players saying the rolls are too fast?
I've been working on a dice game and initial feedback I've gotten is that it's too fast. Gamblers like a second in which to stress about whether they're going to win or loss. Instant feedback apparently takes away the fun. I hadn't thought of that, but maybe I'm going to have to put in a delay - it seems maybe there's a sweet spot - too slow and it's frustrating, but too fast and it doesn't feel like gambling?
From what I've seen it depends on the player. Users that bet small amounts for fun generally like the quick rolls, but someone who is betting big usually likes a bit of suspense to build up. It's hard to find the "sweet spot" because each person prefers something different. Best bet would be to go for somewhere in-between those two points. Consistency of speed is probably more important than the actual speed though in my opinion.
June 07, 2013, 05:49:29 PM
That's possible, I haven't seen that result at all, it seems to not like our copy paste button.
It's on a new laptop with on-board Radeon graphics. I run Linux, and it does seem to be a video card driver issue. I switched from the open source driver to the proprietary one and the problem fixed itself.
Note: Roll speeds boosted again
Do you have any players saying the rolls are too fast?
I've been working on a dice game and initial feedback I've gotten is that it's too fast. Gamblers like a second in which to stress about whether they're going to win or loss. Instant feedback apparently takes away the fun. I hadn't thought of that, but maybe I'm going to have to put in a delay - it seems maybe there's a sweet spot - too slow and it's frustrating, but too fast and it doesn't feel like gambling?
June 07, 2013, 03:36:49 PM
That's unusual, does the problem persist, or was this a one time error?
I closed the tab after seeing that glitch.
I just went back to primedice and saw something similar but different:
I'm beginning to suspect this is an issue with my graphics card driver though.
That's possible, I haven't seen that result at all, it seems to not like our copy paste button.
Sent .01 BTC to fool around with, did 100x of .0001 BTC, over 99.90 and on the 2nd to last round I got 99.89 haha so close! 
So close...
June 07, 2013, 03:48:15 AM
Sent .01 BTC to fool around with, did 100x of .0001 BTC, over 99.90 and on the 2nd to last round I got 99.89 haha so close!
June 07, 2013, 02:36:21 AM
Stunna, may I suggest that you also publish a hash of future secrets? So we know that the secret was made at least a day before, and it did not change when you reveal it.
Although you already can't change the secret because the bets would not match later on.
However, a secret that is generated a day or two in advance will not pose much of a security risk, particularly if you don't store the secret on your web server until it is needed.
If you publish a hash of it 1 week and a day in advance, that would be ideal. Plus I get to use it for my own purpose. (My Lotto game.)
SD published their hashes good for many years into the future, but I don't think that's necessary. Someone might attempt to brute force their secret for a date 10 years from now, and when they succeed, they will win a lot of bitcoins from SD. (no matter how small the chance, someone will "gamble" that it's possible and attempt it anyway.)
No one is going to brute force the hash of any secrets you reveal 1 week from today.
Although you already can't change the secret because the bets would not match later on.
However, a secret that is generated a day or two in advance will not pose much of a security risk, particularly if you don't store the secret on your web server until it is needed.
If you publish a hash of it 1 week and a day in advance, that would be ideal. Plus I get to use it for my own purpose. (My Lotto game.)
SD published their hashes good for many years into the future, but I don't think that's necessary. Someone might attempt to brute force their secret for a date 10 years from now, and when they succeed, they will win a lot of bitcoins from SD. (no matter how small the chance, someone will "gamble" that it's possible and attempt it anyway.)
No one is going to brute force the hash of any secrets you reveal 1 week from today.
Something to look into definitely, but I don't see a big advantage to doing that. As you mentioned if we modified the secret previous bets would not add up so it doesn't add any more security to the bettor.
Note: Roll speeds boosted again
June 07, 2013, 01:56:16 AM
Stunna, may I suggest that you also publish a hash of future secrets? So we know that the secret was made at least a day before, and it did not change when you reveal it.
Although you already can't change the secret because the bets would not match later on.
However, a secret that is generated a day or two in advance will not pose much of a security risk, particularly if you don't store the secret on your web server until it is needed.
If you publish a hash of it 1 week and a day in advance, that would be ideal. Plus I get to use it for my own purpose. (My Lotto game.)
SD published their hashes good for many years into the future, but I don't think that's necessary. Someone might attempt to brute force their secret for a date 10 years from now, and when they succeed, they will win a lot of bitcoins from SD. (no matter how small the chance, someone will "gamble" that it's possible and attempt it anyway.)
No one is going to brute force the hash of any secrets you reveal 1 week from today.
Although you already can't change the secret because the bets would not match later on.
However, a secret that is generated a day or two in advance will not pose much of a security risk, particularly if you don't store the secret on your web server until it is needed.
If you publish a hash of it 1 week and a day in advance, that would be ideal. Plus I get to use it for my own purpose. (My Lotto game.)
SD published their hashes good for many years into the future, but I don't think that's necessary. Someone might attempt to brute force their secret for a date 10 years from now, and when they succeed, they will win a lot of bitcoins from SD. (no matter how small the chance, someone will "gamble" that it's possible and attempt it anyway.)
No one is going to brute force the hash of any secrets you reveal 1 week from today.
I don't think that changes anything unless you're worried about the first bet of the day being manipulated. It seems like an almost unneeded security risk which doesn't set out to achieve all that much.
Not sure though, I guess it won't hurt if it doesn't pose any risk
June 07, 2013, 12:09:20 AM
Stunna, may I suggest that you also publish a hash of future secrets? So we know that the secret was made at least a day before, and it did not change when you reveal it.
Although you already can't change the secret because the bets would not match later on.
However, a secret that is generated a day or two in advance will not pose much of a security risk, particularly if you don't store the secret on your web server until it is needed.
If you publish a hash of it 1 week and a day in advance, that would be ideal. Plus I get to use it for my own purpose. (My Lotto game.)
SD published their hashes good for many years into the future, but I don't think that's necessary. Someone might attempt to brute force their secret for a date 10 years from now, and when they succeed, they will win a lot of bitcoins from SD. (no matter how small the chance, someone will "gamble" that it's possible and attempt it anyway.)
No one is going to brute force the hash of any secrets you reveal 1 week from today.
Although you already can't change the secret because the bets would not match later on.
However, a secret that is generated a day or two in advance will not pose much of a security risk, particularly if you don't store the secret on your web server until it is needed.
If you publish a hash of it 1 week and a day in advance, that would be ideal. Plus I get to use it for my own purpose. (My Lotto game.)
SD published their hashes good for many years into the future, but I don't think that's necessary. Someone might attempt to brute force their secret for a date 10 years from now, and when they succeed, they will win a lot of bitcoins from SD. (no matter how small the chance, someone will "gamble" that it's possible and attempt it anyway.)
No one is going to brute force the hash of any secrets you reveal 1 week from today.
June 06, 2013, 10:17:32 PM
That's unusual, does the problem persist, or was this a one time error?
I closed the tab after seeing that glitch.
I just went back to primedice and saw something similar but different:
I'm beginning to suspect this is an issue with my graphics card driver though.
June 06, 2013, 08:08:00 PM
Stunna, I'm still not on the leaderboard and I have more points than Dickbag. (That's the username in 10th place.)
We'll be adjusting the hiscores to rank by Prime points not BTC wagered very soon.
I just went to primedice for the first time in a week or so, and it looks weird:
Probably a browser glitch rather than a fault with primedice, 'cos that's the chromium icon I see there where the deposit address should be.
Probably a browser glitch rather than a fault with primedice, 'cos that's the chromium icon I see there where the deposit address should be.
That's unusual, does the problem persist, or was this a one time error?
June 06, 2013, 07:41:08 PM
Stunna, I'm still not on the leaderboard and I have more points than Dickbag. (That's the username in 10th place.)
June 06, 2013, 07:14:38 PM
Oh nicely done with the client seed update. That makes things a lot easier now 
I just went to primedice for the first time in a week or so, and it looks weird:
Probably a browser glitch rather than a fault with primedice, 'cos that's the chromium icon I see there where the deposit address should be.
June 06, 2013, 05:20:12 PM
Oh nicely done with the client seed update. That makes things a lot easier now
June 06, 2013, 12:03:37 AM
Ok. I should be on the Leaderboard now. Maybe it's not updating?
Jump to: