@theghostoftomjoad
Yeah, those folks and a bunch of other groups. I've been out of the community for a while now, so I'm not quite sure where the core of it is now. I can ask a friend if you're serious about it, though.
Long braindump on why you want to collaborate with people from the existing activist security community:
The technical knowledge in e.g. security in the box is a tiny part of it — there's much more depth in how messages are delivered and framed, what strategies for self-defence are relevant and which a aren't, and the worldview encoded in the text, all of which have a bigger impact on the outcome for the people you're trying to help than anything technical in the book. That might seem improbable, but I've seen folks encounter bad training, give up on technical security as simply impossible for them, and end up less safe than they were before, with real consequences. Most of the actual security wins for activists also come from changing the social patterns of how they organize rather than the technical changes that might happen at the same time. Being able to write the technical text is, for someone with a conventional security background, pretty easy, but the rest is really hard. Writing a book like this is a ton of work even just for the technical side and much more if you do the social side well. It also needs updating as the technical, social, and legal environment changes, and translation (at least into Spanish even if you only care about the US). Putting in the work for a resource that will be dated quickly and not updated doesn't make sense, but that means the project needs a sustainability plan.