I shall vote to give them all their money and reasonable compensation for their lost oppertunity and pain and suffering.

When will you airdrop my fork coins  to my wallet. 
Thank you.
I am waiting .

@funtraveller - I don't see your name in the list. Please check this out. 

Not gonna lie that really fucking sucks missing the original airdrop, just happy it’s being corrected. 

I propose that those who were accidentally excluded are awarded a delegation until the airdrop. 

Hi. Can you airdrop me too?
I have already posted my fault. Please airdrop me too.


![image.png](https://images.hive.blog/DQmc15w8ELcTkJ9jF9NNAQjgteKwpNfHMkvE6wEepgFmH87/image.png)




https://hive.blog/hive/@bencana0523/please-give-me-my-hive

appreciate the recording, just a friendly suggestion, next time cut out the beginning, while everyone is gathering and there is just noise. it is 5 min of work, saves some minutes in upload time, and looks more professional. 

case by case is the only way. 
whoever made a mistake will not have a problem asking for it. 
those that don't want to be part of hive will not ask for it. 
those that try and lie that they made a mistake will not get it.

more work for everyone but this is the right way.

they had a choice vote for justin or against him. 
  

Fantastic to be able to hear the dev meeting! It makes a big difference to have an open and predictable workflow. Thank you for arranging all of that!

I don't know why I am excluded from the airdrop. I didn't receive any Hive.

Isn't dailychina run by Justyy?

You guys did such a mess with that exclusion list!
It was a mistake in the first place. Not on board with that one.

Keep the updates coming. Currently settling down to watch the YouTube video. 

Hi i'm one of the excluded from the airdrop, and excluded again after script correction, i can say a lot of poynt of view etc etc, but who voted for sockpuppet can't put in one group and tag him as traitor, i think is better ask to people WHY, you can't pretend all have the some information or time to obtain or simply have a decent english understanding to know what is happening.
if i can explain WHY i have SOME vote (not the total) on JS Witness i'm happy to explain, the tag of traitor is a big error for me and other people in my situation

Good and fresh news. Fortunately I can see there some well know accounts that would be corrected from The airdrop exclusion. Hope they would take this into account and are able to take appart emotions and get onboard as they used to.
Thanks for updating us with what’s going on and providing useful links to follow 👍👍👍
Best wishes for you all, stay safe and Hive on! 🤗

Quickly sweep that sketchiness under the rug, and onward with #NewNewNewNewHive!!

Awesome! Let's bring SteemWorld to HIVE!

@steemchiller plz make hiveworld :)

I'm very very glad to see this mistake getting reverted slowly. This was an utterly unfair mistake - such things must not happen in blockchain code which is taken live. I know that the hardfork was very rushed, but that does not excuse this mistake in my opinion.
What I expect to see is an apology by those responsible for this error to the accounts whose funds got seized due to the error. I know errors happen, and errors are human. What needs to happen in such situation is that you own up to your mistakes.

Now to the  new script. That one looks pretty solid overall, and I'm very sure it puts out the right results. There's a thing about it that bothers me a little though. [Here](https://gist.github.com/drov0/545f1bad3e5a6c6a047ba2ce82ebe164#file-ascript-L431-L471) `voters_with_errors` and `errors_names` get defined. The former is a list of accounts that voted on Justin Sun's puppets either directly or by proxy. The latter is a list of accounts which had puppets in their witness votes, but had a proxy activated. The problem with those lists is that those lists more or less come out of nowhere and are so to say hardcoded into the script. They should've been created in the script from zero. The only hardcoded account names that should be in the script are those of Justin Sun's puppet witnesses and maybe those whose Hive stake was removed at the Hardfork in order to make the script more resource efficient. I suppose that those lists were created by another script, which is okay, but that script should've been included in the gist, or been part of the main script.
In addition to that the `voters_with_errors` seems to have been tinkered with. The first entry in the list `"justyy"` uses `"` opposed to all other entries which use `'`. While this is no difference at all for the computer it shows that someone tinkered around manually, which is a no-go in my opinion.
As I said, I don't doubt the results, but I believe that the script should be reworked in order to fix the aforementioned problems. That takes the unknown out of the script and makes it very transparent and easy to confirm the results, as it then only requires a quick check of the list of the Sun puppets and running the code and comparing the results. As of now, in order to confirm the results you actually have to write code yourself in order to create the `voters_with_errors` and `errors_names` lists.
I already discussed part of this with @pharesim (thank you for providing information and your time!) but I thought it might not be bad to put this out here as well.

To be clear, it's a group proposal I have to apply for? There is no individual proposal/judging?

So... are you up for a hiveworld @steemchiller?

I view it as a mistake to exclude any accounts beyond those affected by the 22.2 soft fork + the obvious sock puppet witnesses that were implemented to run 22.5.

Imo, we fork to get a chain that is true to our convictions of the purpose of the STINC fund that people had invested in, and thus to settle the dispute that occurred with the 22.2 fork, not to get what's most convenient and in the best interest to us. I'm sure we can all think of 10 accounts in a minute that we don't want to share a chain with. But building a successful economy means having people with polarized opinions still finding value in the same currency, not migrating away from eachother.

Of course I see how those who may have been previously excluded, and are now instead looking to build a good relationship with JS, would be more likely to dump their Hive tokens. Thus I see why some may think it is in our best interest _short term_ to not airdrop them any tokens. But still, that's an ugly road to go. For many different reasons:

- We want to defeat the age old criticism of Steem having been launched with an unfair advantage to a small group of people. Having an exclusion list created by a dev team means we'll still carry that impression. Whether we like or agree with it or not.
- While not airdropping any tokens to them may not technically be taking away anything they don't own, combining it with hoping that STEEM fails (the way many now seem to do) still end in the same practical result. At least then allow the two chains to each pursue their own ambition, rather than trying to tear the other down in the hope of leaving them empty-handed.
- It lessens the demand for the token when stakeholders know that they may be omitted from any future fork as opposed to looking to invest in a protocol that will yield opportunities long term.
- It significantly harms the likelihood of attracting any further investment and user growth from the demographics mostly affected by the exclusion. Ones that have been an eager early adopter of crypto and Steem in particular.

I don't think this should be our judgement to make. Sure, theoretically, we are free to run whatever new fork we want to. But practically, there will only be so many forks that have a token people know of or care about. If we choose to be rigid about the reason for the HF and previous SF being related to the intended use of the STINC stake and its significance, then answering future questions will be easy. But when one starts to arbitrarily add accounts based on subjective votes, then it will raise a lot of questions, concerns and distrust by future investors and projects. As well as the overall PR and public perception.

I think the best move is to let the market decide which platform holds value, and instead focus on building a more attractive product with a more ambitious goal than surpassing a #66 token by market cap.