In amongst these knee-jerk reactions, the impulse to fork is the most sensible, as it is akin to an actual protest or strike, but that requires organisation, willpower, commitment, goals, infrastructure, people.
People seem to think it's easy to fork something like Linux. It's not? It's not a fork when you clone some source code over to another server. GitHub etc have trivialised the word I guess, because their absurd web based patch submission model abuses the word. "Forks" on Github are just wasteful clones.
An actual fork is an attempt to spin up a new collaborative project. A hostile fork is a form of protest and an attempt at occupying and taking over infrastructure, because SOFTWARE IS INFRASTRUCTURE. Software is not a product. It's not a consumable.
When you declare (for) a fork you should understand what kind of commitment it is. You should know what you're doing. You should be able to foster or provide the necessary expertise to take over and continue an existing thing that already has momentum and an ecosystem around it.
Otherwise you're wasting everyone's time.