Something not working?
Kagaz has no analytics, so if something breaks I have no way of knowing unless you tell me. Pick whichever of these is least annoying — two of them need no account at all.
reading…
This is filled in from the browser you are using right now, so you do not have to look it up. It is the single most useful thing in a bug report — most problems turn out to be specific to one browser. Nothing here identifies you, and none of it is sent anywhere until you choose one of the buttons below.
Opens your mail app with everything above already written out. The simplest option, and the one to use if you would rather not be public.
Write the emailOpens a reply on the launch thread with the details filled in, so everything stays in one place. Good for quick things, and I see it fastest.
Reply on the threadOpens a new issue with the title and body prefilled. Best for anything you want tracked to a fix.
Open an issueYou do not need to write a good bug report — anything at all is better than silence. But if you have thirty seconds spare, these are the things that turn "it didn't work" into a fix:
Please do not send me the document itself — especially not the kind of document you'd be using Kagaz for. If a file is needed to reproduce a problem, I will ask, and only ever for something you have made up for the purpose.
The roadmap lists what's being built and what will never exist here, with the reason for each. If what you want isn't on either list, say so — the reason behind a request is usually more useful than the request itself.
This page reads your browser's own details and writes them into a link. It sends nothing by itself, sets no cookies, and stores nothing. If you close the tab without pressing a button, no trace of you exists anywhere — same as every other page here.