Skip to content

Where notefeed is going

notefeed started as one feed of markdown notes posted over HTTP and read back as RSS. It is becoming a place where anyone, a person, a script or an AI assistant, keeps feeds of notes and pictures without an account, on notefeed.me or on their own server. This page says what is planned and why, inside what notefeed stands for, and what has shipped.

Every step makes publishing easier without making anyone known: it works without an account, through the API and MCP as well as the web UI, and it keeps a note in the one feed it belongs to. Planned steps have no dates, only now, next or later; shipped steps carry the day they shipped. A step that is dropped leaves the timeline, with the reason in its issue.

Now
Accounts that are a number, not a person#292#297#347V2

An optional account holds your feeds and your license on every device, for scripts and MCP too. It is a generated number with passkeys, no e-mail and no name.

Details

In four steps:

  • Sign-in on Better Auth, and one sender any post can set (done).
  • Accounts: sign-ins that renew while used (no weekly sign-in, the allow-list checked on every request); account number, recovery key and passkeys; a feed's owner and its several named feed passwords; account tokens; either an instance password or accounts.
  • Licenses on the account: one checkout for several feeds, the number raised or lowered later.
  • Values and legal pages for accounts.

Readers get nothing new, and nothing about who holds an account is stored.

Later
Webhooks on new notes#252V11

A feed calls out when a note is posted, so a site built from it can rebuild, or a phone can be notified, without polling.

Later
Taken-down images stay down, even changed#331V9

A perceptual hash beside the exact one, so a re-encoded or cropped copy of an image taken down is refused too.

Later
Replies from your own feed#318V8

Answer another feed's note with a note in your own feed, shown under the one it answers; no accounts, nothing stored on someone else's feed.

Later
Notes the operator can't read#213V4

A feed's content encrypted before it leaves the writer, so the running server only ever holds ciphertext.

12 Nov 2026
A ready-made iPhone Shortcut#364V11

Share pictures, text and links to a feed from an iPhone with a signed Shortcut, generated from source; load it, answer four questions, share.

12 Nov 2026
Rename a feed#363V8

A feed can get another name and keeps everything, its read link included; the old name is freed.

12 Nov 2026
Atom beside RSS#362V5

Every read link offers its notes as an Atom feed too, with an entry's last change, so readers pick up an edited note.

10 Nov 2026
Creem's official packages for licenses#346V7

The webhook and the calls to Creem go through Creem's own packages; notefeed keeps only what a payment means for a feed, and the checkout opens over the license page.

29 Oct 2026
Take down one post, not the whole feed#330V9

The operator removes a single note that breaks the law and leaves a mark in its place; the rest of the feed stays.

28 Oct 2026
Drafts#325V11

Notes only the feed's writers see until they are published.

28 Oct 2026
Share to notefeed from a phone, images shrunk on the server#313#315V2

Installed from the browser, notefeed is in the phone's share sheet; every image is shrunk, converted and stripped of its metadata on the server, for every client.

26 Oct 2026
Scheduled notes and a note's date#246V5

Post a note for later, or change the date a note shows.

21 Oct 2026
A lost feed password, recovered with the license key#225V13

Whoever holds a feed's license key can set a new password, without an account or an e-mail address.

18 Oct 2026
Encrypted at rest#216V4

Notes, images and feed details encrypted with a key per feed before they reach the database, the main key kept apart in OpenBao.

16 Oct 2026
Licenses on notefeed.me#194V7

A free tier for every feed, and a monthly or yearly license that lifts its limits; readers never pay.

10 Oct 2026
A report link on every notev0.10.0V9

Anyone can report a note; the operator can take a feed down for good, leaving a tombstone and blocking its images.

3 Oct 2026
Pictures and files are notes toov0.8.0V8

One API for every type of note; pictures are listed in the feed and sent to RSS readers as enclosures.

1 Oct 2026
AI assistants post and read notesv0.6.0V11

An MCP server at /mcp, so Claude and other assistants can post to a feed and read it back.

1 Oct 2026
Many feeds, no accountsv0.5.0V1

One instance holds many feeds, each reached by its name and read by others through a read link that never shows the name.

30 Sep 2026
The first releasev0.2.0V5

Post markdown notes over HTTP, read them back as RSS; every note a plain file; clients for Python and Node.

Parked

Considered and wanted, not needed yet: sharing the rate limits and metrics between several notefeed processes (#129), until notefeed.me runs more than one.

Decided against

Accounts, sign-up or a login that reaches a feed (V1); reader counts, view statistics, a directory or search of feeds (V3); comments stored under someone else's note, where a reply from one's own feed does the job (V8); ads, or a free tier paid for with data (V7); features only notefeed.me has (V6).

Keep it true

The timeline is rendered from docs/roadmap.yml; on GitHub, read that file. Every step has an issue and names the value point it serves. Finish a step in the pull request that finishes it: set status: done, replace when with a date, add the link to its pull request, and move it to the top of the shipped entries. Change the file in the pull request that changes the plan.