Right now we need > %50 to attack the network and impose will or make Hive a dead project.
If > %50 feels something is good, that is actually a majority. Even if they are blocked, > %50 wanting something bad enough to do this spells bad news moving forward. I know calling it a consensus is stupid, but technically >80% isn't a consensus either.
If your changes are done an attacker will need %20 > to make Hive a dead project. Attackers will get what they want because they won't move their votes until it happens. Imagine if it was done immediately after a hard fork with a bug that could be exploited?
The proxy.token did this when Steemit, Poloniex, Binance and Huobi were attacking the Steem network. For weeks proxy.token ensured no one would get a consensus and started asking for stupid things like banning certain witnesses, removing of downvotes, quicker power downtimes (so exploiting the network would be even easier), and a bunch of other crazy changes the majority of people disagreed with. It was so screwed up Hive was forced to be created. This permanently damaged the reputation of DPOS and subsequently both networks.
Lowering the number of witnesses one can vote for is not making the network safer. A lot more thought and complicating factors go into this. For now, allowing people to vote for anything less than 17 witnesses is dangerous because it will make a coordinated attack easier rather than more difficult. The majority will lose their power to prevent attacks.
If it ain't broke don't fix it. Please think of a solution that doesn't make attacking Hive easier.
RE: Hive Hardfork 24: Upcoming Release Candidate, Testnet, and Other Info