The current way to reach Ptichi is the public issue tracker on GitHub. Use it for website problems, factual corrections and general product questions. Posting requires a GitHub account; reading the site does not.
Product
A question, a correction, a useful failure
How to contact Ptichi without publishing your voice recordings or private work.
Tell us where the useful part breaks
A good report can be short:
- Link to the page and name its language.
- Say what you expected and what happened instead.
- For a display problem, include browser and approximate window size.
- For a factual correction, quote the relevant sentence and share a source or explanation.
For example: “On the German exercise page at a narrow window size, the playback label covers the next button.” That gives us something to reproduce. “It feels broken” is understandable, but harder to investigate.
Public means public
Do not attach voice recordings, transcripts, client material, passwords or personal medical details. A screenshot can contain private browser tabs and account names; crop or redact those before posting.
We do not currently provide a private support upload channel. If a problem needs sensitive material to explain, start with a general description and do not send the material. No response-time guarantee is offered.
What belongs here
Missing sources, misleading wording, inaccessible controls, translation mistakes and broken links all count. You do not need to propose a fix before reporting the problem.
Ptichi is under development. A request is useful input, not a promise that the next release will contain it. The public roadmap explains what would justify the next steps.
Reviewed: