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:
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.
RE: Community Discussion and Updates: Hive Airdrop Exclusion List and Code Corrections, Core Developer Meetings