Quote from: xrobau on April 06, 2014, 09:49:53 PM

Quote from: miaviator on April 06, 2014, 05:41:59 PM

Did you already open a support ticket?

Just in case you missed it, lots of people DON'T LIKE the way sessions are expiring continuously. If that's deliberate, please don't. If it's accidental, please fix.

Agreed! So irritating. That said, the captcha seems to be working correctly again, so that's something.

Quote from: hutnik on April 07, 2014, 11:50:44 AM

To me looks like LR is no longer showing time as in CET timezone. Why is that? I almost shortened lease on one of my rigs because 24h lease looked like 26h.

It's showing in UTC, as it always should have been. A better system would be to have the time localized. CET is PITA to try to convert for anyone not in Europe. It was just not worth complaining about in the past.

Quote from: miaviator on April 06, 2014, 10:15:43 PM

You mean can we make our site use a plain-text cookie to store a password and username which gives access to a bitcoin wallet and stays logged on indefinitely?

We could. If customers and providers really wanted that.

The second security release is almost complete which will do away with the annoying captchas in favor of longer session times and 2FA.

Yes, I mean: 'Can you make your site use a plain-text cookie to store password and username, and stay logged in indefinitely?'. E.g. Coinbase never logs me out, Cryptsy logs me out twice a day. Cryptsy=annoying, Coinbase=not.

Reserve 2FA for any transactions would could be deemed harmful. From a provider's perspective lowering prices and changing pools are about it. Create a set of trusted pools which require 2FA to change, and email notifications for any price or pool changes. The worst that could happen is someone could try to lower your prices, then rent your rigs for nothing. You would get emails about all of that and be able to terminate the lease immediately. Security can be further improved by logging IPs to transaction records and displaying them in the history.

Official request:

Customer POOL HISTORY! Today is the third day in a row someone has rented from me with problems. I got a PM from a customer this morning that my rigs were down, but they weren't, and 3 minutes later everything was okay. I have no idea what the problem was because I have no way to tell from the graph if the pool was bad or the rigs weren't responding. LRP is capable of telling the difference between no/bad pool authorization and rigs disconnecting or down. The graph should indicate with different highlighting which is which. A list of all the pools with user/pass that the customer has tried to connect with (stored for current renting session only) would be extremely useful in further narrowing down configuration problems vs provider problems. I don't mind extending leases due to equipment or network malfunctions, but I would like to be confident of the problem before I make that choice.