Hello Robert, Welcome, we are always happy to get contributions. Look at the projects we have in the team and see what motivates you to contribute to: https://gitlab.torproject.org/tpo/anti-censorship/ We have a list of "First contributor" issues, that are usually a good starting point to contribute in a project. See if any of them sounds interesting to you: https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues?sort=creat... Before getting deep into any complex task do discuss it with us and to see if is something we'll want to include. You can join our meetings in matrix/irc on thursdays at 1600UTC in #tor-meeting:matrix.org or #tor-meeting @ irc.oftc.net. I see in your profile that you do work with agentic systems. We don't have a policy against code generated by AIs (yet), but to have better success sending us merge requests I recommend you to manually review any automatic generated code and clean it up before submitting it. We'll expect you to be able to defend the code you are sending. Have fun. Quoting Gustavo Fring via anti-censorship-team (2026-04-02 17:16:17)
Hi anti-censorship team,
I was referred here by the Tor Project Community Team regarding potential engineering collaboration.
I am an infrastructure engineer based in Russia, working under active network restrictions including DPI, protocol blocking and traffic analysis. My focus is Go microservices, WireGuard forks, transport layer automation and observability under censorship constraints.
Recent work includes a probe service that detects seven types of blocking and enables dynamic config updates for Xray based proxy networks. The architecture follows a Client → Relay → Uplink pattern with node specific health checks: Relay performs nine checks including DNS, SNI and TLS fingerprinting, while Uplink focuses on transport with four basic checks. This design delegates detection logic upstream to keep the edge lean. Architecture reference: https://github.com/roberttkach
If there is room for collaboration on tooling, testing or infrastructure hardening, I am happy to discuss a small scoped task. Happy to continue privately if preferred.
Format: remote, flexible, results driven.
Robert Telegram: @roberttkach GitHub: https://github.com/roberttkach
-- meskio | https://meskio.net/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- My contact info: https://meskio.net/crypto.txt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Nos vamos a Croatan.