It only works if it stops being mine.
Wyrm is one person right now, building tools against something a lot bigger than one person. That’s fine as a start and hopeless as a finish. If you want your privacy back and you’re willing to help, there’s room, and you don’t need to be an engineer to take it.
The most useful thing you can do isn’t glamorous. Run a build on your own machine, use it for a week, and tell me where it lies or breaks. A tool that fights surveillance has to actually be right, and being right takes a lot of different computers and a lot of honest reports.
If you write code, the repositories are on GitHub and the tools are AGPL. Fix a bug, sand a rough edge, take on a feature. You don’t have to ask first. Clone it, break it, send a patch, and the work is the introduction.
If you don’t write code, there’s still plenty. Surveillance isn’t an English problem, so translations matter, and I care more about them being exact than fast. Plain guides for people who aren’t engineers are worth as much as the code. If you break things for a living, breaking mine before someone else does is the most valuable help there is. And if all you do is tell one person who’s being watched that there’s an open way to see it, that counts too.
There’s one rule, and it’s the same one the tools follow: treat people the way this project treats its users. No harassment, no gatekeeping, nobody made to feel small for not knowing something yet. Everyone was new to this once. That’s the whole code of conduct.
No résumé, no fee, no gatekeepers. If you found this page, you’re already qualified. Bring an hour, a language, a bug report, or a hard question, and it counts. If you’re not sure where you fit, just ask.
Rather back it than build it? You can support the project.