Kind 30024: Draft Long-form Content

Overview

Draft Long-form Content events (kind 30024) serve as unpublished or work-in-progress versions of long-form articles. They have the same structure and format as published long-form content (kind 30023) but are intended to be private or not yet ready for public consumption. This kind allows authors to save and synchronize drafts across devices before finalizing and publishing them.

Specification

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

Content Format

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

Schema

# Draft Title

This is a paragraph in a draft article.

## 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 draft	["d", "<identifier>"]	Yes
title	Draft title	["title", "My Draft Article Title"]	Recommended
summary	Brief summary of the draft	["summary", "This is a draft summary..."]	No
image	URL for header/preview image	["image", "https://example.com/image.jpg"]	No
t	Topic hashtags	["t", "nostr"]	No
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. Provide an interface for creating, editing, and managing draft articles.
2. Keep drafts separate from published articles in the user interface.
3. Support converting a draft (kind 30024) to a published article (kind 30023).
4. Allow users to continue editing drafts before publication.
5. Include options for previewing how the draft will appear when published.
6. Consider privacy implications, potentially limiting where drafts are published.
7. Only show a user their own drafts, not drafts from other users.

Relay Behavior

Relays should:

1. Store draft events like any other events.
2. Implement proper handling of addressable events if the relay supports that feature.
3. Respect privacy concerns regarding draft content.

Use Cases

• Saving work-in-progress articles
• Synchronizing drafts between different devices
• Backing up unfinished writing
• Collaborative editing workflows
• Keeping notes or outlines for future articles

Example

{
  "id": "f7dfa4952fe8e10591546c1c454f3c3d291fd641074d8125f39ef3ce0161a6b6",
  "pubkey": "a695f6b60119d9521934a691347d9f78e8770b56da16bb255ee286ddf9fda919",
  "created_at": 1675642635,
  "kind": 30024,
  "tags": [
    ["d", "my-draft-article"],
    ["title", "Working Title: Thoughts on Nostr"],
    ["summary", "Draft thoughts on the Nostr protocol (incomplete)"],
    ["t", "nostr"],
    ["t", "draft"]
  ],
  "content": "# Thoughts on Nostr\n\n*Note: This is a draft, still working on the main arguments*\n\nNostr presents an interesting approach to decentralized social media. Unlike federated systems like...\n\n## Key Points to Develop\n\n- Simplicity of the protocol\n- Relay model advantages\n- Comparison with other approaches\n\n*Need to expand this section with more research*",
  "sig": "908a15e46fb4d8675bab026fc230a0e3542bfade63da02d542fb78b2a8513fcd0092619a2c8c1221e581946e0191f2af505dfdf8657a414dbca329186f009262"
}

References

• NIP-23: Long-form Content
• NIP-19: bech32-encoded entities

Related Kinds

• Kind 30023: Long-form Content - Published version of long-form articles
• Kind 1111: Comment - For commenting on published articles
• Kind 31234: Draft Event - General draft event mechanism defined in NIP-37

Notes

• Draft content shares the same technical structure as published long-form content but is meant to remain unpublished or private.
• Clients may implement different privacy controls for drafts, such as only publishing them to private relays.
• The distinction between kinds 30023 and 30024 allows clients to clearly separate published and unpublished content.
• Authors can use the same identifier in the d tag when converting a draft to a published article, maintaining continuity.