> potentially all your users might go with the fork That's the issue right there. Why would you care? Clearly, the maintainer is invested in having a "communi

> potentially all your users might go with the fork That's the issue right there. Why would you care? Clearly, the maintainer is invested in having a "community". Why? They must expect something positive coming out of it, so they are invested in having that community, which then means they have something to lose if that community moves somewhere else and they are left behind. That's what enables this social exploit. A takeaway can be not to get so invested in having a community. These are users of your software, and their "utility" is in helping find bugs, perhaps suggest improvements or even provide patches, making the thing you as the original author made better. But that can clearly become a burden.