You are viewing a single comment's thread from:

RE: The maximization curve

in #steem7 years ago (edited)

We will research it, but you would need to store private secrets on the backend, which is often not something people want to do and it is much more risky for us since someone then may decide to start attacking our servers, for example.

From the technical perspective, there is nothing like that implemented in Steeve yet, so it would be a non-trivial effort. Considering our limited resources right now, not sure this is really feasible right now. But @mor created an issue in the tracker:

https://bitbucket.org/steeveproject/steeve.app/issues/134/enable-automatic-postponing-of-votes

Anyway, what is the benefit of doing this exactly?

Edit: Right, to skip the first 15 minutes...

Posted using Steeve

Sort:  

It would be rather easy, though, to do it on frontend purely, i.e. the queue would be in your browser and you would be voting from the web app still. But closing the browser would postpone voting until your start it up again.

Posted using Steeve

I think for many people that might be enough. I actually don't mind the timing so much as I don't worry too much about curation. I don't vote early though because I don't want to close anyone out.