You are viewing a single comment's thread from:

RE: My accounts are on the Hive blacklist

in #steemworld5 years ago

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.

Sort:  

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.

except for one technical error I'm aware of

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.

Can you use your connection in order to get me the following (very important) informations:

  1. Will the affected users have to do something in order to receive the airdrop they deserve? Or otherwise stated will your error be reversed or will the users have to "fight" for their stake?
  2. Can you give a timeframe in which their stake becomes available to them? Is it a matter of hours, days, weeks, months? I deem this an urgent issue for those affected, of whom I know a handful at the very least!

If you are referring to the script error, in my opinion that will be simply corrected in due course, without the affected users needing to do anything. Of course I can't commit to that as I don't have such control or authority.

In terms of timeframe, again I can only give my opinion but I think several weeks for the next hard fork to be ready and deployed. If someone wants something sooner, I suppose they could propose to Hive's version of SPS to take a settlement in HBD, and in return removing themselves from the airdrop list in the next hard fork. Again I can't promise that would work, and getting enough attention from enough stakeholders to pass a proposal is a challenge, but for someone who really doesn't want to just wait, this might be possible.