I would say the site has a pretty nice look and layout
But you would be missing the best dice experience around if you are on TOR .
@Doog try it without any vpn's ,I see a huge difference in the performance with and without it.
The PM option should be added too.
I guess you saw me in the on-site chat, but I think you've misunderstood.
Here's the situation:
When I use my satellite Internet connection, it takes about 40 seconds to load the site, and once it is loaded I can't bet, chat, claim the faucet, or do anything at all. Even if I use Tor over the satellite connection it is the same.
Then I tried using a cellphone as a hotspot. With that the site loads quickly and everything works. Even if I use Tor over the phone Internet everything works.
So I can't understand what is going on. The satellite connection works with every other site I've tried, just not fastdice. It can't be a routing issue, because Tor does its own routing. It can't be the satellite internet router, because the site works over SSL, so there's nothing in the data that the router could be failing on. So what could it be?
The only thing I can think of is that the ~700ms lag on the satellite connection is causing the problem. The phone connection has much lower latency (due to not having to bounce every packet off a satellite in space).
Edit: I deposited yesterday, and withdrew 1 BTC a few minutes ago. The withdrawal was instant - like it took less than a second.
Edit2: My withdrawal also seems 'stuck'. It was made with a transaction fee that is too small:
Consider using your own wallet rather than blockchain.info to avoid these kinds of trouble. Blockchain.info is really quite unreliable and will end up causing you problems.
Edit3: I tried rebroadcasting the transaction myself, to help spread it to more miners, but it doesn't have a big enough txfee for my node to even accept it:
$ bitcoin-cli sendrawtransaction 0100000009ff0118ec56919f28392a8d5fb113d7da19476fb20d05db53b5710d682efb063701[...]
error: {"code":-26,"message":"66: insufficient priority"}
Edit4: I discovered that the reason my node wouldn't accept the transaction is because I had "minrelaytxfee=0.0001
" in my bitcoin.conf, to avoid low-fee transaction spam. Removing that fixed the problem:
$ bitcoin-cli sendrawtransaction 0100000009ff0118ec56919f28392a8d5fb113d7da19476fb20d05db53b5710d682efb063701[...]
856cb56ac42a89c342296f4b5e788d1f530d5dbb401531a22d01853b8a1155e6