The most reliable way to reach me is email. Write to [email protected] for project questions, collaboration, a correction to something on this site, or a private report about a security or privacy issue. A useful first message says what you are trying to do, which page or repository is involved, and what kind of response would help.
You can also reach me on Telegram. For a bug in a public repository, an issue or pull request on the relevant GitHub project is usually the clearest place because the report, code, and follow-up stay together.
What to include
For a site correction, include the URL and the sentence or behavior that looks wrong. For a software problem, include the repository, version or commit, the smallest input that reproduces it, what you expected, and what happened instead. Please remove access tokens, passwords, private customer data, and other secrets before sending logs or screenshots.
Response and scope
This is a personal site rather than a staffed support desk. I read messages myself and respond when the subject is something I can act on. I do not offer an automated support API, a public webhook endpoint, or a public MCP server from this domain. The developer resources page describes the machine-readable resources that do exist.