notefeed

Oct 29

  1. notefeed 0.34.0: the operator can remove a single post

    notefeed 0.34.0 is out.

    • The operator can now remove one post that breaks the content rules instead of taking down the whole feed. The note goes, along with the text it was posted with and every picture posted with that text. In its place the feed shows a mark: "Removed by the operator: this broke the content rules of this instance.", linked to the terms page. Whoever can post to the feed can delete the mark, but the post does not come back. Links to a removed note answer 410 (removed), also after the mark is deleted. In the API and client packages the mark is a note with removed: true and no content.
    • Every note now counts against a feed's limits: texts, pictures and marks alike. On a free feed, a feed that kept pictures after its license ran out drops its oldest notes sooner.
    • AI assistants now see which notes are the operator's marks: list_notes and get_note show them with removed: true, get_note and edit_note refuse a removed note, and delete_note deletes a mark. 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.
    • Breaking: if you run notefeed yourself with NOTEFEED_MAX_NOTES_PER_FEED set, it now counts pictures as well as text notes, so a feed with many pictures reaches the limit sooner and further posts answer 507 (note_limit). Raise the value if that matters to you. NOTEFEED_MAX_IMAGES_PER_FEED still limits pictures on their own.
    • If you run notefeed yourself on SQLite or PostgreSQL, back up your data before upgrading: the first start adds a table.

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

Oct 28

  1. notefeed 0.33.1: no report link on drafts

    notefeed 0.33.1 is out.

    • Drafts and scheduled notes no longer show a Report link. No reader can see them, so there is nothing to report, and whoever does see one can remove it. A note gets its Report link once readers see it. On notefeed.me the terms, privacy page and imprint now say the link is on every published note.

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

  2. 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.

  3. notefeed 0.32.0: a license key no longer opens your purchase details

    notefeed 0.32.0 is out.

    • A license key no longer opens the payment provider's page with your purchases. That page shows the buyer's e-mail address, payment method, invoices and every license they bought with its key, so a key given to a co-author or put into a script could reach all of that. To cancel, change the payment method or get invoices, sign in at https://creem.io/my-orders/login with the e-mail address you bought with, or use the link in your receipt. The license page links there under "Manage your purchases" and no longer asks for a key.
    • Scripts can ask what licenses cost, where to buy one and where buyers manage them, with GET /api/v1/licenses or licenses() in both client packages.
    • AI assistants can now look up the license plans, where to buy a license and where to manage a purchase with the new tool get_licenses. Assistants see the new tool only after reconnecting. In Claude, start a new chat, or remove and add the notefeed connector if it still does not show. In Claude Code, restart it.

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

  4. notefeed 0.31.1: the values page has its own address

    notefeed 0.31.1 is out.

    • The page that says what notefeed stands for is now at https://docs.notefeed.me/values/. For a few hours it was at /vision/, which no longer works, so update any link you saved. The footer's "Values" link and the start page point to the new address.

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

  5. notefeed 0.31.0: share pictures from the phone, images cleaned on the server

    notefeed 0.31.0 is out.

    • You can share pictures to notefeed from your phone. On Android, notefeed installed from Chrome now shows up in the share sheet for pictures, text and links. Pick a feed and they wait in its compose box until you post. Samsung Internet's installed app does not do this yet. On the iPhone, a Shortcut does the same, and the new docs page "Sharing from a phone" shows how to set it up. Pictures in one post may now share a file name, unless the text refers to that name.
    • Every image is now shrunk to at most 2560 px, turned upright and stripped of its location and camera data on the server, whatever posted it. Animations stay. An upload may now be up to 10 MiB instead of 5, so a phone photo can go as it is.
    • A title image uploaded in a feed's settings belongs to the feed and no longer shows up as a post. Scripts can set it with PUT / DELETE /api/v1/feeds/{feed}/image, setFeedImage / removeFeedImage (JS) or set_feed_image / remove_feed_image (Python). Title images uploaded before stay posts until you set them again. The footer and the ⓘ menu show the version an instance runs. On a wide screen, a note's page has a large "All notes" link beside it, and large pictures in notes are kept to a sensible size. A new page linked from the footer, "Values", says what notefeed stands for.
    • AI assistants can now set a feed's title image with set_feed_image, and pictures posted with post_note may share a name unless the markdown refers to it. Assistants see the new tool only after reconnecting. In Claude, start a new chat, or remove and add the notefeed connector if it still does not show. In Claude Code, restart it.
    • Breaking: a file that only starts like an image but is not one is now refused with 415, and an image over 100 megapixels with 413. When the server is busy with images it answers 503 with Retry-After, which both clients raise as RateLimitedError. Wait the given time and try again.
    • If you run notefeed yourself, remove NOTEFEED_SHRINK_IMAGE_BYTES: it is no longer used and logs a warning at startup. NOTEFEED_MAX_IMAGE_BYTES now defaults to 10 MiB, which is also the most it can be set to.

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

Oct 27

  1. notefeed 0.30.0: create a feed before its first note, reset a lost password anywhere

    notefeed 0.30.0 is out.

    • You can create a feed without posting a note, to reserve its name with a password, a license and a read id from the start: with POST /api/v1/feeds/{feed}, createFeed / create_feed in the clients, or "Create feed without a note" in a new feed's card. On notefeed.me this needs a license key, which goes on the new feed. Free feeds still start with their first note.
    • A lost feed password can now be reset with the feed's license key from scripts too, with POST /api/v1/feeds/{feed}/password/recover or recoverFeedPassword / recover_feed_password in the clients. A browser that is still unlocked finds it under "Forgot the current password?" in the feed's settings. A changed password is now confirmed next to the password row. Feeds with an active license are no longer rate limited on posts, edits and deletes. Wrong passwords and keys still are.
    • The page uses the whole width of the window. Mermaid diagrams are drawn in the timeline too, and a click opens one enlarged. The newest agent skills are always at https://notefeed.me/r/skills/post-to-notefeed.md.
    • AI assistants can now create a feed with create_feed and reset a lost password with the license key through recover_feed_password. Assistants see the new 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.

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

  2. notefeed 0.29.0: editable tags, claiming open feeds and better long notes

    notefeed 0.29.0 is out.

    • You can change a note's tags after posting: in the edit form, with PATCH and tags, or with notefeed update --tags in both clients. An empty list removes them. Tags that are numbers now sort as numbers, so v0.9.1 comes before v0.10.0.
    • An open feed can now get a password later. Whoever has the feed's name can set the first one, on the settings page, with PUT /api/v1/feeds/{feed}/password or with the clients. The read link and RSS stay open. Where licenses are sold, a license can now go on a feed without a password, when it is created or later from its settings.
    • Long notes read better: headings get anchors, three or more headings get a table of contents, pictures can be sized with ![](shot.png#width=480), code is highlighted on the page and in RSS, and Mermaid diagrams are drawn. A note posted with a name (X-Note-Name) can be fetched by that name at /r/<read id>/<name>, which always serves the newest note with that name.
    • AI assistants can now set a note's tags with edit_note, give a note a name with post_note, and set a feed's password or license with update_feed, which also no longer needs a title and description every time. 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.
    • Breaking: where licenses are sold, a lapsed license key is now refused with 402 instead of being accepted and doing nothing. An unknown key counts as a failed attempt, like a wrong password. Renew the license or send a valid key.
    • If you run notefeed yourself, upgrade soon: this release includes Next.js security fixes. The footer now links only the feeds listed in NOTEFEED_FOOTER_FEEDS, in that order, and none if it is unset, so set it before upgrading if you want footer links. Reserved feeds no longer hit the free tier's limits, and euro prices show as 1.99 €.

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

Oct 26

  1. notefeed 0.28.0: scheduled notes and changeable dates

    notefeed 0.28.0 is out.

    • A note posted with a date in the future is scheduled. Readers see it on the read page, in RSS and in the read API only from that time on. You see it marked as scheduled.
    • You can change a note's date at any time: in the edit form on the note's page, with PATCH and date, with notefeed update --date in both clients, or by asking an AI assistant through edit_note. Pictures posted with a note move with it.
    • Breaking: the header for a note's time is now X-Note-Date, and a post that still sends X-Note-Created is refused with an error. Everywhere else it is date instead of created_at, createdAt or --created. The old names no longer work.
    • Note ids are now random. Every existing note gets a new id and keeps its date, so links to single notes and their pictures stop working, and links from one feed to another are not updated. If you run notefeed yourself, back up your data and images before upgrading.

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

  2. notefeed 0.27.0: post a note with an earlier date

    notefeed 0.27.0 is out.

    • You can now post a note with a time in the past instead of now, from a date and time with its offset or just a date, back to 1970. The note then sits at that time in the feed, its read link and RSS.
    • The compose box has a date-and-time field next to Tags for this. From scripts, send the X-Note-Created header. The JS client takes createdAt and notefeed post --created, the Python client takes created_at and --created, and AI assistants can pass created_at to post_note.
    • If something polls a feed for notes newer than the last one it saw, it will miss notes posted with an earlier date.
    • The footer and the ⓘ menu now link to notefeed's own release notes and this blog.

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

  3. notefeed 0.26.0: notes as you wrote them

    notefeed 0.26.0 is out.

    • A note now shows its text exactly as you wrote it. notefeed used to take the first line as the title and leave it out of the text; now only a title you set yourself shows as a heading above the note.
    • Click anywhere on a note to open it.
    • RSS readers now show a note as formatted text with its pictures instead of raw markdown, and its first picture is the item's image.

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