Topic: Just-Dice.com : now with added CLAMs : Play or Invest - page 184. (Read 454769 times)
My bot is sooper good. I don't have one though.
What are you doing to make the browser unresponsive? Use setTimeout() to wait without burning CPU.
Thanks, I was using the pause function from vlees' bot (? I may remember wrong) that does seem to jam with any higher ms number.Code:
function pausecomp(ms) {
ms += new Date().getTime();
while (new Date() < ms){}
}
ms += new Date().getTime();
while (new Date() < ms){}
}
Without that the browser indeed does stay operational. Still need a fix to the response parsing to adjust bet amount progression after the recent changes though.
Good luck with that lol
Haha yea I know. I figure cause that's what I've lost on JD
It's a perfectly viable business model, just not something with guaranteed short-term results.
Thanks Rannasha for taking all these questions while I was sleeping. I love how investors feel - uh - invested - and so take responsibility for helping out newcomers. It's this feeling of community that I was hoping for when I made the site the way I did, with on-site chat and shared bankroll.
Speaking of community, this single thread with 60+ pages is daunting. Are there any plans for a JD forum or wiki? I just found out about the blog! (OK, now I see that there are 3 threads.)
Gamblers can keep busy placing bets. Investors have spare time, and could help with organizing, documenting, moderating, etc.
I couldn't find the database dump Rannasha mentioned. Can I get a copy?
I understand that the minimum bet size policy prevents the House from going bust... but I'm more interested in questions like: "Given the observed behavior of the whales, how likely is a 10% drawdown over the next month?"
Good luck with that lol
I wonder how many low number accounts people have lost access to. Will they have stories in the future similar to people that have lost access to bitcoins they mined back when they were only worth fractions of a dollar?
I don't think I've seen anyone with an ID of 200-299
I'm actually ID #200. Maybe I'm the only one left in the 200s lol.
KOS offered 0.05 you might want to PM him.
Not sure about 0.05 but I would sell it for around 1 if anyone was interested in it
Will there soon be an API?
I am using wait of 3000ms between every 0.00002 bet to start with. Despite that the whole browser becomes unresponsive, which is a grand change to the worse from yesterday when the forced intervals were working but you could still bet appropriately.
What are you doing to make the browser unresponsive? Use setTimeout() to wait without burning CPU.
Sooo many accounts on this site.
It's a perfectly viable business model, just not something with guaranteed short-term results.
Thanks Rannasha for taking all these questions while I was sleeping. I love how investors feel - uh - invested - and so take responsibility for helping out newcomers. It's this feeling of community that I was hoping for when I made the site the way I did, with on-site chat and shared bankroll.
As for amounts wagered and invested, I occasionally update https://just-dice.com/wagered.txt with the amount wagered each day (UTC), and http://blockchain.info/charts/balance?address=14o7zMMUJkG6De24r3JkJ6USgChq7iWF86 pretty closely tracks the amount invested over time (it's the cold wallet balance, which doesn't include the amount I keep online to process day to day withdrawals, and does include player balances, which pretty much cancel each other out).
wagered.txt was just updated, btw.
The throttle limiters have done something to the socket interface. Bots are malfunctioning and the whole connection jams up when trying to use one that worked with Chrome flawlessly prior to yesterday.
It's not the throttling that broke the bots, it's the message that says "your bet is being delayed because you only bet X BTC". Previously, when a message was received, it always came when the bet was finished, and so bots were coded to send their next bet whenever they saw a message. This "your bet is delayed" message necessarily has to come before the bet has finished, so people can understand why the site seems slow.
If the bots wait for a 'result' message, they'll be fine. Or if they just ignore the 'jdmsg' messages, that'll work too.
Can't they just add in waits?
I am using wait of 3000ms between every 0.00002 bet to start with. Despite that the whole browser becomes unresponsive, which is a grand change to the worse from yesterday when the forced intervals were working but you could still bet appropriately. The throttle limiters have done something to the socket interface. Bots are malfunctioning and the whole connection jams up when trying to use one that worked with Chrome flawlessly prior to yesterday.
Can't they just add in waits?
The throttle limiters have done something to the socket interface. Bots are malfunctioning and the whole connection jams up when trying to use one that worked with Chrome flawlessly prior to yesterday.
Hi everyone, I'm new to JD, looking to invest on the House side.
I look at the theoretical 1% house edge and the .26% actual profit on the Stats tab, and I just have to wonder, is the House managing risk properly? Is this actually a viable business model?
The way I see it, bad luck has already eaten away 74% of the house edge.
I look at the theoretical 1% house edge and the .26% actual profit on the Stats tab, and I just have to wonder, is the House managing risk properly? Is this actually a viable business model?
The way I see it, bad luck has already eaten away 74% of the house edge.
It's a perfectly viable business model, just not something with guaranteed short-term results. The site has had a single gambler bettings very large amounts and having above average luck, which took the house profit on some big swings. The house was up more than the theoretical 1% before, went down to something like -0.5% and has since then recovered to the current .26%. These results are still well within you can statistically expect.
Quote
Also, does anyone know the turnover? (Average amount wagered per day, divided by the amount invested.)
4 days and 6 hours ago, dooglus made a database dump for people to run stats on. We can use that to make an estimate. At that point, 556K BTC had been wagered. Right now it's 624K. That translates to 16,000 BTC wagered per day, which is a little less than half of the invested amount. So with these numbers, you expect a little less than 0.5% daily increase on your investment. But these stats are extremely sensitive to variation.
Hi everyone, I'm new to JD, looking to invest on the House side.
I look at the theoretical 1% house edge and the .26% actual profit on the Stats tab, and I just have to wonder, is the House managing risk properly? Is this actually a viable business model?
The way I see it, bad luck has already eaten away 74% of the house edge.
Also, does anyone know the turnover? (Average amount wagered per day, divided by the amount invested.)
I look at the theoretical 1% house edge and the .26% actual profit on the Stats tab, and I just have to wonder, is the House managing risk properly? Is this actually a viable business model?
The way I see it, bad luck has already eaten away 74% of the house edge.
Also, does anyone know the turnover? (Average amount wagered per day, divided by the amount invested.)
I have been on JD for some time, I believe "Always roll low" strategy gets people nowhere. Cos everyone's hash (the seed where roll results are derived from) is different. What's important is to "know your own unique hash". Use hundreds of really low bets to get a feel of the "character" of your hash and then bet accordingly.
For example, my one frequently gives >90 after a <10 roll, so I bet high after a <10 roll
I wonder if there really is a system that works since these numbers are only pseudo-random? Maybe the server sheet should automatically change every X rollsFor example, my one frequently gives >90 after a <10 roll, so I bet high after a <10 roll
The system is fine as it is. As an investor (most of the time anyway), I'm more than happy with people thinking they have a system or a 'feel of the character' of their hash.
Also, while the 'lo' roll has a higher chance of winning than 'hi', the probability that this effect comes into play is 4.4 * 10^-34, which means it's a lot less likely than winning every lottery on the planet in the coming year and getting struck by lightning a few times along the way.
I'm 15, but I won't accept offers lower than 10 BTC. Because my account has magic seeds in it.
Actually, I do agree with you. I like my seed/hash and it is infinitely more valuable than the usernumber
I wonder if there really is a system that works since these numbers are only pseudo-random? Maybe the server sheet should automatically change every X rolls
yes, it may be more difficult to "know" your hash if the hash is refreshed every x rolls, it doesn't make it "more random".
random or pseudo-random is not important, what's important is the roll/seed/hash is "extremely difficult to predict" and "provably fair".
I'm 15, but I won't accept offers lower than 10 BTC. Because my account has magic seeds in it.
What are magic seeds? They grow your profit through the roof and up into the sky.
What are magic seeds? They grow your profit through the roof and up into the sky.
Jump to: