notefeed 0.33.0: drafts

notefeed 0.33.0 is out.

• A note can now be a draft. Whoever can post to the feed sees it on the feed page, marked as a draft, and edits it like any other note. Readers do not see it on the read link, in RSS or in the read API, and neither do they see its pictures. Publishing keeps its id, links and date, so a draft dated in the past takes its place there and one dated in the future becomes a scheduled note. A published note can be made a draft again. In the web app, tick Draft in the compose box or in a note's edit form. Scripts send X-Note-Draft: true on a post or draft in a PATCH, the client packages take draft, and the CLI has notefeed post --draft and notefeed update --draft / --publish. A draft picture cannot be the feed's title image.
• The post-to-notefeed skill asks where you want your drafts: in the conversation, on the feed itself, or in a second feed whose read link you can send to a reviewer.
• The report form now offers an optional name beside the optional e-mail address, and asks you to confirm that you report in good faith, as the EU's Digital Services Act requires.
• AI assistants can now post notes and files as drafts with post_note and post_file, and publish a draft or hide a note again with edit_note. list_notes and get_note show which notes are drafts. Assistants see the changed tools only after reconnecting. In Claude, start a new chat, or remove and add the notefeed connector if they still do not show. In Claude Code, restart it.
• If you run notefeed yourself on SQLite or PostgreSQL, back up your data before upgrading: the first start adds a column to the notes table and rebuilds its index.
• If you run notefeed yourself with NOTEFEED_REPORT_ENDPOINT set, the report page now also sends the fields name and good_faith. If your inbox refuses fields it does not know, add these two before upgrading.

All the details are in the release notes and on GitHub.