<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cypher Page - Blog</title>
    <description><![CDATA[Share small pages, keep the same address when you update them, and save copies to read offline. Explore the CLI and the upcoming desktop app.]]></description>
    <lastBuildDate>Fri, 20 Nov 2026 16:08:49 +0000</lastBuildDate>
    <link>https://cypher.page/blog/</link>
    <atom:link href="https://cypher.page/blog/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <guid>https://cypher.page/blog/cypherpage-0-4-0/</guid>
      <title>Cypher Page CLI 0.4.0: keep drafts local until you share</title>
      <pubDate>Wed, 18 Nov 2026 00:00:00 +0000</pubDate>
      <link>https://cypher.page/blog/cypherpage-0-4-0/</link>
      <description><![CDATA[<p>Cypher Page CLI version <strong>0.4.0</strong> was released on November 18, 2026. It adds a
way to save a cleaned local draft, review it, and choose when to share it over
Veilid. This is a command-line release; the graphical app is still in
development.</p>
<!-- excerpt -->
<h2 id="save-a-draft-before-sharing">Save a draft before sharing</h2>
<p>Importing a Markdown file saves an independent, cleaned snapshot on your
device. It does not share the page. When you are ready, use the local ID shown
by <code translate="no">list</code> with <code translate="no">publish --local</code> to share that saved version. Editing the
original file later does not update the snapshot. These operations use your
local collection and may initialize local services or the system keychain, so
they are not a network-isolated mode.</p>
<p>File publication also saves a local snapshot first. If a publication attempt
fails, inspect <code translate="no">list</code> and retry a retained ID with <code translate="no">publish --local</code> instead of
running file publication again; each new file invocation creates another local
identity. File publication requires working local-page storage. The 0.4.0
<code translate="no">list</code> output includes local IDs and statuses, so scripts parsing older
address-only rows need updating. An unconfirmed attempt may have written
remote data. A confirmed remote success followed by a local bookkeeping error
is a different case and may already have shared the page. An ID recorded as
<code translate="no">published</code> is not sent again by <code translate="no">publish --local</code>; use <code translate="no">update</code> or <code translate="no">clear</code> to
change it.</p>
<h2 id="back-up-local-work-carefully">Back up local work carefully</h2>
<p>Version 0.4.0 encrypted backups include saved local documents and their IDs,
titles, statuses, and addresses alongside ownership credentials and titles.
They do not include fetched copies or your original Markdown files, so keep
those files separately. Use a strong, unique backup passphrase.</p>
<p>Version 0.4.0 restores V1 backups made by 0.3.0, but version 0.3.0 cannot
restore V2 backups. Before either backup or restore, stop other Cypherpage
processes using the same local collection. Restore skips existing owners and
identical local records; conflicts are rejected before writes, but a later
storage failure can leave a partial import. There is no general rollback
guarantee. If the system keychain is unavailable, the explicit
<code translate="no">--allow-insecure-fallback</code> flag permits less-secure file-based device-key
storage. Under that fallback, device secrets are protected only by filesystem
permissions rather than the system keychain; protect the selected storage and
backups accordingly.</p>
<h2 id="try-the-cli">Try the CLI</h2>
<p>The registry install compiles the published source crate and requires Rust
1.89 or newer plus native build tools:</p>
<pre><code class="language-sh hljs bash" translate="no">cargo install cypherpage --version 0.4.0 --locked</code></pre>
<p>You can also build from the <code translate="no">v0.4.0</code> source tag. There is no prebuilt
cross-platform executable or graphical installer. See the
<a href="/cli/">CLI installation and workflow guide</a>, the
<a href="https://gitlab.com/cypherpage/cypherpage/-/releases/v0.4.0" rel="noopener noreferrer">0.4.0 GitLab release notes</a>,
and the <a href="https://crates.io/crates/cypherpage/0.4.0" rel="noopener noreferrer">version 0.4.0 crate on crates.io</a>.</p>]]></description>
    </item>
    <item>
      <guid>https://cypher.page/blog/building-the-desktop-app/</guid>
      <title>Project notes: building the desktop app</title>
      <pubDate>Fri, 06 Nov 2026 00:00:00 +0000</pubDate>
      <link>https://cypher.page/blog/building-the-desktop-app/</link>
      <description><![CDATA[<p>Work on the Cypher Page desktop app is well under way. The app is not ready to download yet, but its foundations are in place, its screens have been designed, and the first shared building blocks of its interface are finished. Here is what that means for you, and what still has to happen before you can try it.</p>
<!-- excerpt -->
<h2 id="what-moved-forward">What moved forward</h2>
<h3 id="a-working-app-window">A working app window</h3>
<p>The desktop app now opens in its own window and can talk to the part of the program that will eventually publish and fetch pages. You can move between its main screens: the home screen, the page editor, settings, and the user guide. For now, those screens are empty outlines. They do not publish, fetch, or save anything yet.</p>
<h3 id="every-screen-has-been-designed">Every screen has been designed</h3>
<p>Ten screens have been designed and reviewed, covering writing a page, reading one, fetching a page someone shared with you, your list of pages, your saved copies, settings, and the guide. A clickable preview uses sample content to try out the layout before the real features are connected.</p>
<h3 id="decisions-about-how-the-app-will-work">Decisions about how the app will work</h3>
<p>Several choices about everyday use are now settled:</p>
<ul>
<li><strong>Your own pages come first.</strong> The app will open on My Pages, the list of pages you own.</li>
<li><strong>Drafts stay on your device.</strong> You can save a page you are still working on without publishing it. Drafts are stored privately on your computer and are never shared until you choose to share the page.</li>
<li><strong>Writing a page is a simple form.</strong> You fill in a title, the body of the page, and any extra details you want to add. People who like to edit the underlying file directly can still do that.</li>
<li><strong>Three clear choices when editing:</strong> save your draft, share the page, or discard your changes. Sharing a new page gives it an address. Sharing a page you already own updates it at the same address.</li>
<li><strong>Edit your own pages, copy anyone's.</strong> You can edit pages you own. For a page someone else wrote, you can make your own copy to start from.</li>
<li><strong>Settings in one simple list,</strong> and a user guide that explains the ideas behind Cypher Page before walking through each task.</li>
</ul>
<h3 id="built-to-be-usable-by-everyone">Built to be usable by everyone</h3>
<p>The app is designed to work with a keyboard alone and with screen readers, following the WCAG 2.2 Level AA accessibility guidelines. The first shared interface pieces, buttons, are finished and tested. Menus are being built now. Everything else in the app will be assembled from these pieces, so they behave consistently on every screen.</p>
<h2 id="what-you-can-try-today">What you can try today</h2>
<p>The desktop app is not available to download yet, and there is no release date. If you are comfortable using a terminal, the <a href="/cli/">command-line application</a> can already publish, fetch, and manage pages, and it can be built from source.</p>
<h2 id="what-we-are-exploring-next">What we are exploring next</h2>
<p>The remaining work is planned in five stages, in this order:</p>
<ol>
<li><strong>Settings and status.</strong> Getting set up, seeing whether the app is connected, and adjusting how long it waits for the network.</li>
<li><strong>Writing and sharing your pages.</strong> Creating pages, saving drafts, sharing and updating pages, and managing the list of pages you own.</li>
<li><strong>Fetching and saving pages.</strong> Opening a page from an address someone gave you, choosing whether to save a copy for offline reading, refreshing saved copies, and removing ones you no longer want.</li>
<li><strong>Keeping your ownership safe.</strong> Backing up the private keys that let you change your pages, and restoring them on another computer.</li>
<li><strong>Testing before release.</strong> Checking the app on Linux, macOS, and Windows, including hands-on testing with keyboards and screen readers.</li>
</ol>
<p>Favorites and search appear in the app's menus, but they are planned for later. For now, those screens will say the feature is not available yet.</p>
<p>An Android version is also being planned. An early test version can be built, but it has not been tried on real phones, and there is no date for it either.</p>
<h2 id="follow-the-work">Follow the work</h2>
<p><a href="/app/">Learn about the planned desktop app</a>, <a href="/cli/">read the CLI guide</a>, or <a href="/blog/">see all project notes</a>.</p>
<!--
REVIEW BEFORE PUBLISHING
[ ] Every factual claim is supported by public GitLab work. Add links to public
    issues, milestones, or merge requests if the cypherpage-app repository is public.
[ ] Menus (the dropdown component) are still in progress; update that sentence if
    they are finished before publishing.
[ ] Availability was checked: no desktop or Android download exists.
[ ] No confidential, personal, or security-sensitive information is included.
[ ] No unsupported promises, guarantees, or deadlines are included.
[ ] Rename the file if the publication date changes.
[ ] Remove draft: true, then run composer run build and review the generated post.
-->]]></description>
    </item>
  </channel>
</rss>
