Well, first of all: people who claim that this isn't possible because "we're just developing tools" do have _some_ ground to stand on, but it's shaky. What you

Well, first of all: people who claim that this isn't possible because "we're just developing tools" do have _some_ ground to stand on, but it's shaky. What you can do is knowingly bias your software so that the functionality it provides, workflows it makes easy, messaging, and community all lean towards and encourage positive purpose. Ideally without artificially restricting anything, although it's a balance, and it's fine to ban and censor -- preferably with guidelines -- within your own project. Additionally, where possible you can add friction and costs for bad actors by anticipating how they might want to misuse or bend your software (or community), and work to make that challenging for them. Transparency helps a lot in both cases: it can illustrate your project's principles to the wide set of benevolent users, while making it more expensive for negative influences to gain a foothold (and more obvious in retrospect).