Quote from: stingleword on December 20, 2015, 03:31:33 PM

Quote from: nachoig on December 20, 2015, 05:26:49 AM

Excuse me, but websites like this MUST work properly with HTTPS (and enabled by default). It's unacceptable the use of HTTP in this type of thing, due to the risk of MITM attacks.

Unfortunately, trying to use it with HTTPS (inserting 'https://' before the domain name) just redirects to the CloudFlare page with the 522 error.

LuckyBit doesn't use HTTPS because it doesn't need it. LuckyBit does not hold user funds for any significant time and all plays are conducted "on-chain", i.e. they occur in response to blockchain events, not website events. A MITM attack against LuckyBit could - at worst - replace the game addresses with malicious ones. If you are unsure about where you are sending your funds, simply double-check on the blockchain first; the game addresses are public information that is easily verified independently. One could play LuckyBit without even opening the website.

There has never been a report of MITM attacks against LuckyBit.

I've actually have played many times with out the site... .... and now sarcastic side... how did luckyb.it make it so long with no issues if y all miss Something that ob vious... lol I ahave faith administration and stinglinstration are on top of things