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:
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.