Running Continuum — Common Questions

原始 JSON

{
  "kind": 30023,
  "id": "4fbd504b8d578a251532532a38e43594ce92f170b1c9551da142720f2045eb55",
  "pubkey": "2b998b04e2a1fe6855b2e0ab10bb92b774b5dfa0f78926c7a65ae08086727e47",
  "created_at": 1773431998,
  "tags": [
    [
      "d",
      "running-continuum--common-questions"
    ],
    [
      "title",
      "Running Continuum — Common Questions"
    ],
    [
      "published_at",
      "1773431998"
    ],
    [
      "client",
      "Continuum-Pro-localhost"
    ],
    [
      "display_date",
      "2026-03-13"
    ],
    [
      "image",
      "https://2026.mycontinuum.xyz/archive/pro/nostr/npub19wvckp8z58lxs4djuz43pwujka6tthaq77yjd3axttsgppnj0ersgdguvd/images/6_friday.jpg"
    ],
    [
      "e",
      "4cf1ad3f02b7796697eba2036a2e713f1012402f7a4f47b201950820fb07aec0",
      "edit"
    ]
  ],
  "content": "Andrew G. Stanton - Friday, March 13, 2026\n\n---\n\nContinuum is designed to give users **sovereign custody of identity, writing, and archives** while still publishing to the Nostr network.  \nThe questions below address common concerns people have when first installing or running the system.\n\n---\n\n## What exactly is Continuum?\n\nContinuum is a **local-first publishing node** for authors.\n\nIt manages:\n\n- sovereign identity (`npub`s)\n- signed content (articles and notes)\n- relay publishing on the Nostr network\n- durable local archives of your work\n\nContinuum runs **entirely on your machine**.\n\nThere are **no cloud dependencies** and no external platform required to operate it.\n\nYou control your keys, your writing, and your archive.\n\n---\n\n## Is Continuum a notary or proof-of-authorship service?\n\nNo.\n\nContinuum is **not a notarization or timestamping service**.\n\nSome systems focus on taking content, hashing it, and anchoring a proof to a blockchain to demonstrate authorship.\n\nContinuum operates at a different layer.\n\nInstead of proving authorship through a service, Continuum enables **sovereign publishing** by allowing authors to:\n\n- maintain custody of their identities\n- sign their content directly\n- publish to distributed relays\n- maintain a durable local archive\n\nIn other words:\n\n```\nContinuum = author node\n```\n\nrather than\n\n```\nnotary service\n```\n\n\nBecause all content is **signed**, Continuum could be extended to support notarization workflows if desired, but that is **not its primary purpose**.\n\nThe primary goal is **local custody and durable publishing**, not proof services.\n\n---\n\n## Local-first? What if I lose my data?\n\nLocal-first does **not** mean fragile. It means **you control the primary copy**.\n\nContinuum protects your work through multiple durability layers:\n\n- **Local database** – fast access to your notes and articles\n- **Nostr relays** – published content is distributed across the network\n- **Archive export** – your signed history can be reconstructed\n- **Backups** – you can copy the archive directory anywhere\n\nEven if your machine fails, your content can usually be **recovered from relays or archives**.\n\nLocal-first gives you **control**, not risk.\n\n---\n\n## Multiple keys? What if I get hacked?\n\nContinuum reduces risk compared to centralized platforms.\n\nYou can:\n\n- use **separate identities (`npub`s)** for different roles\n- rotate identities if necessary\n- isolate publishing identities\n\nIf a key is compromised, you can **stop using it and create a new one**.\n\nThere is no centralized account that can be taken over.\n\n---\n\n## What if I lose my keys?\n\nPrivate keys should be backed up, but you have options:\n\n- Continuum stores keys **locally in identity files**\n- those files can be **copied or encrypted for backup**\n- multiple identities can be created and used\n\nEven if a key is lost, **published content remains verifiable** on the Nostr network.\n\nFor experimentation you can also create **throwaway keys**.\n\n---\n\n## Docker? Isn’t that complicated?\n\nDocker simply runs Continuum in a **self-contained environment**.\n\nBenefits include:\n\n- no dependency conflicts\n- predictable environment\n- easier upgrades\n- isolation from the rest of your system\n\nTypical setup:\n\n1. Install Docker (one time)\n2. Run the provided script\n3. Open the local dashboard\n\nAfter that Continuum behaves like a **normal local application**.\n\n---\n\n## ZIP download — what about viruses or tampering?\n\nEach Continuum release includes a **SHA-256 checksum** so you can verify the download.\n\nAfter downloading the archive run:\n\n```\nshasum -a 256 continuum.zip\n```\n\nThis produces a hash value.\n\nCompare it with the **official hash provided in the release `.txt` file**.\n\nIf the values match:\n\n- the file downloaded correctly\n- the contents have not been modified or corrupted\n\nIf the values do not match, discard the file and download again.\n\nYou can also:\n\n- inspect the ZIP contents\n- scan with antivirus tools\n- run the software inside Docker isolation\n\n---\n\n## Local custody — what about discovery?\n\nLocal custody **does not isolate your content.**\n\nContinuum publishes to the **Nostr network**, which provides:\n\n- distributed relays\n- global discovery\n- multiple compatible clients (Primal, Coracle, etc.)\n\nYour archive stays under your control while your content can still be discovered **across the ecosystem.**\n\n---\n\n## Can I test Continuum without commitment?\n\nYes.\n\nYou can experiment safely by:\n\n- creating a **new test identity**\n- publishing a few notes\n- exploring the dashboard\n\nIf you decide not to continue, simply delete the folder.\n\nNothing persists outside your machine unless you **choose to publish to relays**.\n\n---\n\n## The Principle Behind Continuum\n\nContinuum follows a simple idea:\n\n**Your identity, your keys, your content.**\n\nInstead of trusting a platform to preserve your work, you maintain **sovereign custody** while still benefiting from a distributed network.\n\nContinuum prioritizes:\n\n- durability\n- portability\n- independence\n- verifiable authorship\n\nRunning Continuum is closer to operating a **personal publishing node** than signing up for another cloud account.\n\n---\n\n## Why not just use a folder of Markdown files and Git?\n\nUsing Markdown files with Git is a good practice and many developers already work this way.\n\nContinuum does not replace that idea — it builds on it and extends it into a **sovereign publishing system**.\n\nA simple Markdown + Git workflow gives you:\n\n- local files\n- version history\n- backups if you push to a remote repository\n\nContinuum adds several capabilities that Markdown + Git alone does not provide:\n\n### Sovereign identity\n\nContinuum is built around **cryptographic identity (`npub`)**.\n\nEvery piece of content is **signed by the author's key**, creating verifiable authorship across the Nostr network.\n\nGit commits can be signed, but those signatures usually remain within the repository context.\n\nContinuum signatures travel **with the content itself**.\n\n---\n\n### Distributed publishing\n\nGit manages repositories.\n\nContinuum publishes directly to **Nostr relays**, allowing content to be discovered across the network without relying on a central hosting platform.\n\nYour work becomes part of a **distributed publishing ecosystem** rather than a single repository.\n\n---\n\n### Durable archives\n\nContinuum maintains **structured archives of signed content** that can be rebuilt if needed.\n\nThis creates a durable record of authorship and publication history that can be recovered independently of any single platform.\n\nGit preserves file history, but it is not designed as a **long-term publishing and authorship archive**.\n\n\n---\n\n### Multi-identity workflows\n\nContinuum allows you to manage **multiple identities (`npub`s)** in a single environment.\n\nThis makes it possible to publish under different identities while keeping each identity's keys and content organized.\n\nGit repositories typically assume a **single identity per repository**.\n\n---\n\n### Local-first publishing\n\nContinuum acts more like a **personal author node** than a repository.\n\nIt manages:\n\n- identity\n- signing\n- publishing\n- relay distribution\n- archives\n\nwhile still keeping everything **locally under your control**.\n\n---\n\n### The difference in perspective\n\nA Markdown + Git workflow looks like this:\n\n```\nMarkdown files\n↓\nGit repository\n↓\nHosting platform\n```\n\n\nContinuum looks more like this:\n\n\n```\nIdentity (npub)\n↓\nSigned content\n↓\nLocal archive\n↓\nDistributed publishing (Nostr relays)\n```\n\n\nBoth approaches value **local files**, but Continuum integrates identity, publishing, and durability into one coherent system.\n\nIf Markdown + Git already meets all of your needs, you may not need Continuum.\n\nBut many writers and builders want something that provides **sovereign identity and distributed publishing**, not just version control.\n\n---\n\n## Why not just use a Nostr client like Primal, Damus, or Coracle?\n\nNostr clients are excellent tools for **reading and interacting with the network**.\n\nThey focus on:\n\n- browsing content\n- social interactions\n- short-form posting\n- following other users\n\nContinuum serves a different purpose.\n\nIt is designed to function as a **local-first author node** that manages identity, publishing, and archives.\n\n### Nostr clients\n\nTypical Nostr clients provide:\n\n- timeline browsing\n- replies and social interaction\n- reposts and likes\n- ephemeral posting\n\nMost clients treat content primarily as **social feed activity**.\n\n---\n\n### Continuum\n\nContinuum focuses on **durable authorship and publishing**.\n\nIt manages:\n\n- sovereign identity (`npub`s)\n- signed articles and notes\n- local archives of all published content\n- structured publishing workflows\n- relay distribution\n- recoverable publishing history\n\nInstead of treating posts as ephemeral feed items, Continuum treats them as **signed artifacts of authorship**.\n\n---\n\n### The architectural difference\n\nA typical client workflow looks like this:\n\n```\nUser\n↓\nClient app\n↓\nRelays\n↓\nTimeline feeds\n```\n\nContinuum operates more like this:\n\n```\nIdentity (npub)\n↓\nSigned content\n↓\nLocal archive\n↓\nDistributed relays\n↓\nNostr ecosystem\n```\n\n\nIn this model the **author node is primary**, and the network is a distribution layer.\n\n---\n\n### Complementary tools\n\nContinuum does not replace Nostr clients.\n\nIn fact, many users will:\n\n- **publish using Continuum**\n- **read and interact using their favorite Nostr client**\n\nContinuum focuses on **creating durable, signed work**, while clients focus on **consuming and interacting with content**.\n\n---\n\n### Why this distinction matters\n\nMost social platforms prioritize **engagement and feeds**.\n\nContinuum prioritizes:\n\n- authorship\n- custody\n- durability\n- verifiable history\n\nIt treats writing more like **published work** than social activity.\n\n---\n\n## Why should I care about owning my publishing infrastructure?\n\nMost people today publish their work using tools or platforms they do not control.\n\nExamples include:\n\n- social networks\n- blogging platforms\n- cloud-based writing tools\n- newsletter services\n- most Nostr clients\n\nThese tools are convenient, but they come with tradeoffs.\n\nYour work becomes dependent on:\n\n- the platform’s policies\n- the platform’s availability\n- the platform’s business model\n- the platform’s long-term survival\n\nEven in decentralized systems like Nostr, most users still rely on **third-party clients**.\n\nThose clients typically require your **private key or delegated signing authority**, meaning you still trust a third-party tool to perform signing operations.\n\nContinuum takes a different approach.\n\nInstead of publishing **through a platform or client**, Continuum allows authors to run their own **local publishing node**.\n\nThis means:\n\n- your identity belongs to you\n- your private keys remain under your control\n- signing happens locally\n- your content is stored locally\n- your archive is portable\n- publishing happens through a distributed network\n\nIn this model, clients and platforms become **interfaces**, not gatekeepers.\n\nYour work remains yours regardless of which clients or services exist in the future.\n\n---\n\n### The traditional model\n\nMost online publishing looks like this:\n\n\n```\nAuthor\n↓\nPlatform account\n↓\nPlatform database\n↓\nReaders\n```\n\n\nIf the platform disappears, the connection between author and reader disappears as well.\n\n---\n\n### The Continuum model\n\nContinuum treats authorship differently:\n\n```\nAuthor identity\n↓\nSigned content\n↓\nLocal archive\n↓\nDistributed relays\n↓\nMultiple clients and readers\n```\n\nYour writing is **not tied to a single platform**.\n\nIt exists as a set of **signed artifacts** that can be distributed and verified across the network.\n\n---\n\n### A shift in perspective\n\nContinuum is based on a simple idea:\n\n**Writers should own their publishing infrastructure.**\n\nInstead of relying on centralized services, authors can maintain custody of their identity and work while still participating in a global network.\n\nThis approach emphasizes:\n\n- independence\n- durability\n- portability\n- verifiable authorship\n- long-term preservation\n\nIt may look different from typical cloud platforms, but it restores something that existed in earlier eras of computing:\n\n**the author runs the node.**",
  "sig": "fbe9c4a1f7b6fd31b82ad87fa2394495431ee2c1d905011a117369b230029bd0e8374070f09c3178050047ec02a2bef818aad6e5570b397d8f32a07d2cb2f44f"
}