Community
One person built this. You're invited.
Graphophone is small enough that every report reaches a real human. No customer-success scripts. Pick the right channel below and we'll see it.
Channels
Where to go
- Email
Found a bug
Include the platform, the build version (Settings → Version), and the steps to reproduce. We aim to reply within 48 hours.
- Email
Want a feature
Tell us the use case in your own words, not the solution you have in mind. We read every one.
- /.well-known/security.txt
Report a security issue
Private disclosure first. We respond within 48 hours, publish a fix, then credit the reporter in the changelog (with permission).
- Email + a11y subject
Report an accessibility issue
We treat a11y regressions as P0. Same response window as security; see the /accessibility statement for what the bar is.
How we talk
House norms
- 1 Be specific. A reproducible failure is a fix; a vibe is a thread.
- 2 Be patient. One engineer, real day-job. We answer in days, not hours.
- 3 Be candid. If the docs are wrong, say so — it's the fastest path to better docs.
- 4 Don't share other people's journals. Mock data only in screenshots / repros.
Code of Conduct
The Contributor Covenant v2.1 applies to every Graphophone community space. The private channel for reports is hello@graphophone.app; mark the subject "Conduct" so it gets flagged.
What we read first
On a given day, in order: 1) security reports, 2) privacy-invariant regressions, 3) crash bugs with a reproducer, 4) accessibility issues, 5) everything else. If you think yours falls into one of the first four, say so in the issue body — we'll respond faster.
Start a journal that talks back.
Free to download. No account, no ads, no trackers. Upgrade to Depth when you want more.
