The hosted service¶
You do not have to run notefeed yourself. A public instance runs at notefeed.me: open it, pick a feed name and post.
It is the same software as in these docs, on the current release. Wherever an example says https://notes.example.com, use https://notefeed.me:
export NOTEFEED_URL=https://notefeed.me NOTEFEED_FEED=homelab-7f3k2q9x4m8wz
What to know before you use it¶
- There are no accounts. Nothing to register, and no instance password. The feed name is what lets someone read and post, so on an instance the whole internet can reach, pick a long name nobody can guess. A feed password protects posting and the feed page on top of that.
- Sign-in is off. Notes carry no sender.
- Every feed starts on the free tier. It keeps its newest 1000 notes and has no pictures and no feed password; a license for the feed lifts that. The rate limits apply at their defaults.
- Some feed names are taken by the operator, as reserved feeds.
- It comes with no promise of availability. It is run with care, with backups and monitoring, but by one person. For something you depend on, run your own.
Who runs it and where your data is¶
notefeed.me is run by the author of notefeed, in Germany, on a server in a German data centre.
- Data privacy: what is stored, what the logs hold, how long backups keep a deleted feed, and your rights.
- Imprint: who is responsible and how to reach them.
Those two pages and the terms are the binding statement. These docs describe the software and do not repeat them.
Reporting content¶
Every note on notefeed.me carries a Report link, on the feed page, the note page and the read-only view. It opens the form at notefeed.me/report with the note already named; a mail to abuse@notefeed.me works as well.
- What a report holds: the feed's read id and the note's id, the reason you choose, what you write, and your e-mail address if you give one. When the report has been dealt with, your text and address are deleted the day after; an anonymised record of the decision is kept. The privacy page has the binding wording.
- Nothing is hidden automatically. The operator reads each report and decides.
- A feed that must go is removed for good, with all its notes and images: its name and its read link answer removed by the operator and cannot be used again, and the same images are refused in every feed afterwards.
- There is no appeal path yet beyond writing to the address above.
- Nobody is identified. There are no accounts and notes carry no sender, so a removal is not attributed to anyone and nobody can be barred from posting.
How the link, the form and the removal work is in the self-hosting pages: A report link on every note and Removing a feed as the operator.
How it is run¶
The whole setup is public as a worked example: notefeed/stacks holds the compose files of the server, with PostgreSQL, an S3-compatible image store and Caddy in front. If you plan a public instance of your own, it is a place to start from.
Hosted or your own¶
| notefeed.me | Your own instance | |
|---|---|---|
| Set-up | None | Docker Compose, a few minutes |
| Who can reach it | Anyone who knows a feed's name or read link | Whoever you let: your LAN, or behind an instance password |
| Where the notes are | On the service's server in Germany | On your disk, as plain .md files or in your database |
| Limits and settings | Fixed: the free tier per feed, a license to lift it | Yours to set; no free tier, no licenses |
| Sender on notes | No | With sign-in, if you switch it on |
Moving later is possible in both directions: a feed is its notes, and the API reads and posts them.