I think it's too late for them to fix that matter... They should've seen the problems right away and fixed them before putting that list into the code.
You are viewing a single comment's thread from:
I think it's too late for them to fix that matter... They should've seen the problems right away and fixed them before putting that list into the code.
It isn't too late. By design it can be corrected in a later HF or even directly via an SPS proposal. Make your case and if Hive stakeholders agree then it will be done.
But that is not really a smart way of approaching such matters. In dubio pro reo. You should take the list to a usable content before applying it. What you are doing is equivalent to putting innocent people into jail because you slightly suspect they might maybe be criminal.
You're approaching that matter in a shoot first talk later fashion which I don't like.
I don't think there is anything wrong with the list, except for one technical error I'm aware of.
People should take responsibility for their actions. If you support centralizing a chain in any way then don't expect a new chain built for the entire purpose of decentralization to give you free coins.
Everyone on that list or not still has their Steem. Nothing has been taken away.
There is at least two I know of on the list that voted the top 20 not realizing that some of them were sockpuppets. First time witness voters trying to do the right thing - there might be more.
It will have to be sorted out via the SPS, but when the two seem a little older and less technical than the average age group, I am not sure how that is going to work.
@lichtblick is on this list as well! Can't be right!!!
Seems there was an error in the script, so I am guessing it will be sorted out once all the other technical things are taken care of.
This reaction is kinda silly.
I remember when I wasn't on the list for the Palnet airdrop. I kindly pointed it out. Asked if they could look into it. Didn't make a fuss. Received the airdrop.
These people have the same opportunity here to be professional and respectful.
They choose not to. Irrational decisions got many in this mess. I'm not surprised to see an irrational reaction.
Are you going to fix that prior to taking that list live? Because that's a thing fixed in 3 Minutes if you know what you are doing.
Otherwise I think we can peacefully disagree on that. I don't have the stake to change such things, so I'll have to live with what you are doing...
No, it isn't feasible to change the code so soon before a hardfork. There are already exchanges running the release, and they already complained that getting it only a day or two before was way too late. (Ideally hard fork code is frozen and release a month before, but this was considered an emergency situation.)
This will need to be addressed on the Hive side.
That's very bad for all the users which are affected despite not applying to your criteria. I expect a quick solution for those accounts from the top 20 hive witnesses. ASAP after the hardfork. Those users shouldn't have to do anything more than others to get what they deserve.
I'm in favor of a quick fix for that, yes.
It's absolutely not too late. They can do copies later on, with consensus to do so.
Of course they can. What they are too late to do is to gain my trust. Knowingly implementing faulty code which unfairly distributes funds is very trust-breaking in my opinion.
Read the latest post on @hiveio
This can be corrected and was necessary to avoid further being broken down. It was basically now or never. I have seen projects that took longer to prepare/do it perfect. They mess up at least as much, and they don't have any justification for mistakes any more. Things are being fixed quickly now, including this. Also, remember that feedback of the people involved is very much necessary. Now we have the feedback.