One channel, and it is a real one. Bugs, questions, and feature requests all go to the same place, where the reply is public and the next person with the same problem can read it.
Open an issue on GitHub. It does not need a template or a title in any particular shape — a sentence about what happened is enough to start.
Nook is made by one developer, so a reply may take a few days. An issue that has gone quiet has not been closed in someone's head; a nudge on the thread is welcome.
Nothing here is required, but each one removes a round trip:
Please leave out anything you would not want in public: an issue is a public page. Nothing in a report needs an account, a password, or an invitation code, and a support request will never ask you for one.
Nook reads feeds on your device and keeps working without a network or an account. If subscriptions are missing after moving to a new device, they were never on a server to restore from — export an OPML file from the old device and import it on the new one. Privacy explains what is stored and where.
Publishing is optional, and during the beta it is available to invited accounts only. Publishing describes how it works and where your writing lives; Email lists every message the service sends, so an unexpected one can be checked against the list.
Both are in the app, and neither depends on us answering an issue first. You can export your records in full and delete them at any time, including while publishing is suspended — losing access to a service should not mean losing access to your own writing.
For anything that should not be public — a vulnerability, or a way to reach someone else's data — open a private security advisory instead of a normal issue. It goes to the same person and stays closed until there is a fix.