Kind 30023: Long-form Content

Overview

Long-form Content events (kind 30023) provide a way for users to publish longer articles, blog posts, essays, or any text content that exceeds the practical limits of regular notes. These events are designed to be editable and use Markdown formatting to maintain consistent rendering across different clients.

Specification

Property	Value
Kind Number	30023
Event Range	Addressable
Defined in	NIP-23

Content Format

The content field contains Markdown-formatted text. The Markdown should be "clean" without hard line breaks in paragraphs and without HTML embedded within the Markdown.

Schema

# Title

This is a paragraph in Markdown format.

## Subheading

This is another paragraph with **bold text** and *italics*.

[This is a link](https://example.com)

- List item 1
- List item 2
- List item 3

Tags

Tag Name	Description	Format	Required
d	Unique identifier for the article	["d", "<identifier>"]	Yes
title	Article title	["title", "My Article Title"]	Recommended
summary	Brief summary of the article	["summary", "This is a summary..."]	Recommended
published_at	Original publication timestamp	["published_at", "1671217411"]	Recommended
image	URL for header/preview image	["image", "https://example.com/image.jpg"]	No
t	Topic hashtags	["t", "nostr"]	Recommended
e	Referenced events	["e", "<event-id>", "<relay-url>"]	No
a	Referenced addressable events	["a", "30023:<pubkey>:<d-identifier>", "<relay-url>"]	No
p	Referenced profiles	["p", "<pubkey>", "<relay-url>"]	No

Client Behavior

Clients should:

1. Render the Markdown content properly, maintaining the author's formatting.
2. Support updating articles via new events with the same d identifier.
3. Display only the most recent version of an article when multiple versions exist.
4. Render links to other notes, profiles, or long-form content appropriately.
5. Parse and display metadata like title, summary, and publication date.
6. Support NIP-19 naddr references for linking to articles.

Relay Behavior

Relays should:

1. Store long-form content events.
2. Support queries for these events by d tag, author, or other parameters.
3. Implement proper handling of replaceable events if the relay supports that feature.

Use Cases

• Publishing blog posts
• Writing tutorials or documentation
• Sharing in-depth analysis
• Creating newspaper or magazine-style articles
• Academic writing or research summaries
• Newsletters
• Comprehensive reviews

Example

{
  "id": "b3e392b11f5d4f28321cedd09303a748acfd0487aea5a7450b3481c60b6e4f87",
  "pubkey": "a695f6b60119d9521934a691347d9f78e8770b56da16bb255ee286ddf9fda919",
  "created_at": 1675642635,
  "kind": 30023,
  "tags": [
    ["d", "lorem-ipsum"],
    ["title", "Lorem Ipsum"],
    ["published_at", "1296962229"],
    ["t", "placeholder"],
    ["t", "example"],
    ["e", "b3e392b11f5d4f28321cedd09303a748acfd0487aea5a7450b3481c60b6e4f87", "wss://relay.example.com"],
    ["a", "30023:a695f6b60119d9521934a691347d9f78e8770b56da16bb255ee286ddf9fda919:ipsum", "wss://relay.nostr.org"]
  ],
  "content": "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.\n\nDuis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.",
  "sig": "908a15e46fb4d8675bab026fc230a0e3542bfade63da02d542fb78b2a8513fcd0092619a2c8c1221e581946e0191f2af505dfdf8657a414dbca329186f009262"
}

References

• NIP-23: Long-form Content
• NIP-19: bech32-encoded entities
• NIP-21: nostr: URI scheme
• NIP-27: Text Note References

Related Kinds

• Kind 30024: Draft Long-form Content - For unpublished drafts
• Kind 1111: Comment - For commenting on articles
• Kind 1: Short Text Note - For shorter content

Notes

• Long-form content is meant to be editable over time, unlike regular notes (kind 1) which are immutable.
• .created_at represents the last update time, not necessarily the original publication time.
• Proper Markdown formatting without HTML or arbitrary line breaks ensures consistent rendering across different clients and device sizes.
• Clients that primarily deal with kind 1 notes are not expected to implement support for this kind.
• Comments on long-form content should use kind 1111 as defined in NIP-22.