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.
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.
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.
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.
Considered and wanted, not needed yet: sharing the rate limits and metrics between several notefeed processes (#129), until notefeed.me runs more than one.
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).
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.