You are viewing a single comment's thread from:

RE: Proposal #39 - Funding On Pause

in #steemdao5 years ago

:-)
I decided. But not exactly that. I think I will stop voting for my own proposal. Even though it's awesome. I'm awesome too. Also modest and humble.

Now to be serious, the idea is to vote for all proposals you like AND return proposal. Then, after some time when system reaches some balance, check if your desired proposals are on top, and unvote return proposal until your all or most of your besties are above it... and unless there's other proposal that you definitely don't want to be funded having more approval than return proposal.

Sort:  

Hahahaha.

Well, my stake can't affect anything...but I do hope that the heavyweight accounts read this comment

I'm aware this has been mentioned before but would it not make sense to allow stakeholders to be able to 'slide' VESTS on the return proposal to give them more flexibility? BT's account, unless he chooses to split it up, is a bit like a master switch at present!

It will unnecessarily complicate things a lot, and ultimately it really doesn't matter that much, because regardless of how big voter is, idea is same: vote for all they like, don't vote for one you don't like, vote or not for return proposal.
True, big vote moves return proposal up a lot, but it also does same with other proposals voted for.

Disagree, and I'll quote you to explain why:

Then, after some time when system reaches some balance, check if your desired proposals are on top, and unvote return proposal until your all or most of your besties are above it [emphasis added]

This can't be done when the only choice possible on a huge account is 100% or 0%.

For the system to work properly people have to be able to vote not just yes or no but also on the specific ordering of proposals, and people with large accounts can't currently do that (other than by splitting their accounts, which is generally undesirable).

Can't be done precisely. True.
I'm not saying that it wouldn't be more convenient but it adds a lot of complexity (vs current implementation) to add precision to individual preferences, but those shouldn't matter much because (well, if) more big accounts will be voting?

It is possible but seems a little bit like wishful thinking.

I mean, to make a very specific and personal case here, there is only 1.3 million SP votes between the documentation for developers proposal and the closed source web site proposal. I'm very much in favor of one and very much not in favor of the other. Right now it isn't an issue because return is much higher than both, but it could very easily turn into a situation where unless I split my accounts (which by the way I am in the process of doing), I have to support both or neither, which is not at all what I want.

I understand it could be complicated to implement, but I don't think the accounts with the stake to make a difference would be confused.

It is a shame that salmon cannot read, or I'm sure they would want to see the proposal discussed in the post supported.