[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6},"actionData","errors","routes/hashtag",{"_7":8,"_9":10,"_11":12},"articles",[13],"authors",{},"tag","#draft",{"_14":15,"_16":17,"_18":19,"_20":21,"_22":23,"_24":25,"_26":27},"content","\n**Status:** Draft \n**Type:** Community convention (not a NIP) \n**Last updated:** 20 Dec 2025\n\nA lightweight, Nostr-native convention for mirroring RSS or Atom feeds with provenance, deduplication, and update handling.\n\n---\n\n## Abstract\n\nRSS-to-Nostr bridges exist today, but they are fragmented, lossy, and inconsistent. Most simply dump feed entries into kind 1 notes, losing provenance, update semantics, and any hope of cross-mirror deduplication.\n\nNSF-01 defines a minimal, composable convention for representing syndicated feeds and feed items on Nostr using existing NIPs. It focuses on identity, stability, and clarity rather than crawling behaviour or trust guarantees.\n\n---\n\n## Goals\n\n- Represent RSS/Atom feeds as first-class Nostr identities \n- Enable deterministic item identifiers across mirrors \n- Support updates and revisions without duplication \n- Preserve provenance and source attribution \n- Remain fully compatible with existing clients and relays \n\n---\n\n## Non-goals\n\n- Replacing RSS or Atom \n- Defining polling schedules or crawler behaviour \n- Solving copyright, licensing, or authenticity \n- Defining “official” publisher verification \n\n---\n\n## Terminology\n\n| Term | Meaning |\n|-----|--------|\n| Feed URL | RSS or Atom feed URL |\n| Item URL | Canonical webpage for an entry |\n| GUID | RSS `` or Atom `` |\n| Mirror | Service that republishes a feed onto Nostr |\n| Feed identity key | Pubkey used to publish the feed and its items |\n\n---\n\n## Dependencies\n\nThis convention reuses existing NIPs and does not invent new primitives.\n\n- **NIP-23**: Long-form content (kind 30023) \n- **NIP-48**: Proxy tags for mirrored content \n- **NIP-73**: External content identifiers (`i` / `k`) \n- **NIP-09**: Event deletion (optional)\n\n---\n\n## Design overview\n\n### 1. Feed representation\n\nEach feed is represented by a dedicated Nostr identity.\n\n- **Event kind:** `0` (metadata)\n- **Publisher:** Feed identity key\n\n#### Required metadata fields\n- `name` – Feed title \n- `about` – Feed description \n- `website` – Feed homepage, if available \n- `picture` – Feed image, if available \n\n#### Required tags\n\n[\"i\", \"\"] [\"k\", \"web\"]\n\n#### Recommended tags\n\n[\"proxy\", \"#feed\", \"rss\"]\n\nThis allows the feed itself to be queried, followed, muted, or listed like any other profile, while clearly marking it as syndicated content.\n\n---\n\n### 2. Item representation\n\nEach feed item is published as an **addressable long-form event**.\n\n- **Event kind:** `30023`\n- **One logical item = one stable `d` tag**\n\nThis enables clean updates. The latest event with the same `d` value wins.\n\n#### Required tags\n\n[\"d\", \"\"] [\"proxy\", \"\", \"rss\"]\n\n##### Stable item key\nUse the most stable identifier available:\n\n- Preferred: `guid:`\n- Fallback: `url:`\n\n##### Proxy id format\n\n#\n\n---\n\n### 3. External identity (strongly recommended)\n\nIf the feed item has a canonical webpage URL:\n\n[\"i\", \"\"] [\"k\", \"web\"]\n\nThis enables cross-mirror deduplication even when GUIDs differ.\n\n---\n\n### 4. Recommended item tags\n\n| Tag | Purpose |\n|----|--------|\n| `title` | Item title |\n| `published_at` | Original publish time (unix seconds) |\n| `updated_at` | Last update time |\n| `summary` | Short plain-text summary |\n| `r` | Item URL (for simple clients) |\n| `license` | SPDX identifier or URL, if known |\n\n---\n\n### 5. Item content\n\n- Markdown preferred \n- Mirrors may include:\n - Title\n - Summary\n - Link to original\n - Full content if provided by the feed, otherwise excerpt\n\nMirrors should avoid heavy rewriting or commentary.\n\n---\n\n## Normalisation rules\n\nMirrors SHOULD normalise URLs used in `i` and `proxy` tags:\n\n- Lowercase scheme and host \n- Remove URL fragments (`#...`) for `i/k` web identifiers \n- Preserve query strings unless site-specific rules are known \n\n---\n\n## Deduplication guidance (clients)\n\nClients MAY treat items as the same logical entry if any match:\n\n1. Same `proxy` id \n2. Same `i` + `k:web` external identifier \n\nPreference should be given to trusted pubkeys or user-followed mirrors.\n\n---\n\n## Updates and deletions\n\n### Updates\n- Republish kind `30023` with the same `d` tag \n- Update content and metadata as needed \n\n### Deletions\n- Mirrors MAY publish NIP-09 deletions \n- Mirrors SHOULD avoid deleting items simply because they age out of feeds \n\nDeletion policy is mirror-specific.\n\n---\n\n## Multiple mirrors and trust\n\nMultiple mirrors may publish the same feed.\n\nThis convention intentionally does not define:\n- Which mirror is “official”\n- How trust is established\n\nClients are expected to rely on:\n- Follow lists\n- Mute lists\n- Relay trust\n- User preference\n\nPublisher verification can be layered later using website proofs or identity bindings.\n\n---\n\n## Optional compatibility note\n\nMirrors MAY also publish a short-form kind `1` note linking to the canonical `30023` item for timeline visibility. The `30023` event remains authoritative.\n\n---\n\n## Minimal compliance checklist\n\nA mirror implementing NSF-01 MUST:\n\n- Publish a kind `0` feed profile\n- Use `proxy` tags to mark mirrored content\n- Publish items as kind `30023`\n- Use stable `d` tags per logical item\n\nA mirror SHOULD:\n\n- Include `i/k:web` tags when item URLs exist\n- Preserve original publish times\n- Avoid destructive deletions\n\n---\n\n## Open questions\n\n- Standard tag for per-item author attribution \n- Optional feed manifest event for mirror policy and cadence \n- Client-side UX treatment for syndicated content \n\n---\n\n## Status\n\nNSF-01 is an experimental convention. Feedback, forks, and alternative implementations are encouraged.\n\nIf adoption stabilises, this document could be proposed as a formal NIP or remain as a lightweight community standard.","created_at",1766191756,"id","cacf4d9ee55183deee13f7654f1a738642f3033ef62eac0cb1d8d3e3597e1dc0","kind",30023,"pubkey","b5d34eedc7d8f81ceaa5ed377b5a2d534ee949fae0c5ab3bae0a576aa7475cbf","sig","a992297278dd448f69b99a10b95a01bc14614fcef3f1ccb7f444dd9d2e2ba90160e4b34cafc352ab5a211ce2df82f98891c0acaa3e4924507381b3a3645a078e","tags",[28,29,30,31,32,33,34,35,36,37,38,39],[56,57,58],[54,55],[52,53],[50,51],[48,49],[46,47],[40,45],[40,44],[40,43],[40,42],[40,12],[40,41],"t","#proposal","#convention","#rss","#nostr","feed","published_at","1766191756","summary","A lightweight, Nostr-native convention for mirroring RSS or Atom feeds with provenance, deduplication, and update handling.","title","Nostr Syndicated Feeds Convention (NSF-01)\n","image","","d","670adf2b3371230a","client","YakiHonne","31990:20986fb83e775d96d188ca5c9df10ce6d613e0eb7e5768a0f0b12b37cdac21b3:1700732875747"]