
MyEditor: from first draft to publication
How MyEditor joins local writing, Nostr, EINUNDZWANZIG and STANDUP into one path. Requested: 1,500,000 sats.
The idea for MyEditor grew out of my own everyday life.
I wanted a text editor on my laptop that suits the way I write. A place for short thoughts, notes and drafts, and just as much for longer articles. At the same time, I did not want to tie my texts to one particular device or to a single provider’s cloud service.
That is how MyEditor came about.
MyEditor combines classic local writing with Nostr. A text can simply stay a file on your own computer. If you like, you can also keep drafts private and encrypted on your own Nostr relays. Connect MyEditor on a second device with the same Nostr identity, and those drafts open there again, ready to work on.
Once a text is finished, it can be published straight from MyEditor: as a short Nostr note or as a full NIP-23 article with title, summary, cover, tags and embedded media.
The private key stays in your own NIP-46 signer and is never stored in MyEditor. Pictures and other media can be managed through Blossom and embedded directly in articles.
MyEditor already runs on Windows, macOS and Linux.
This way, censorship-resistant publishing does not arrive as a complicated protocol or a specialist tool, but as an ordinary desktop program that is easy to install. Download, install, write and publish.
MyEditor is open source and aims to make Nostr accessible exactly where many people already work: on their own computer.
MyEditor and STANDUP
EINUNDZWANZIG STANDUP was an important point of reference for me from the start.
STANDUP creates a place where content on Nostr can be discovered, curated and published. MyEditor starts one step earlier: with the writing itself.
So the long-term idea is not to build two separate editors.
MyEditor is to be the writer’s personal desk. STANDUP the editorial office and publishing platform.
A text starts locally as an idea or a private draft. It grows in MyEditor into a finished article and can then be handed straight to STANDUP, to be curated, published and shared further there.
The result is one continuous publishing workflow:
- Write
- Save the draft
- Manage media
- Publish or submit
- Curate on STANDUP
- Reach readers
Nostr is the open infrastructure in the background.
What I want to build with the funding
With the requested support of 1,500,000 sats, I want to develop MyEditor exactly where a working Nostr editor becomes a complete, easy to use workflow for writers.
The focus is on five concrete areas.
-
Movement I
Simple Nostr onboarding
MyEditor should not assume that a new user already knows Nostr or has an identity.
Anyone without a Nostr account should be guided through getting started in plain words, and then be able to start writing right away.
Nostr should stay out of the way as much as possible.
The goal is not to explain a protocol to people first, but to give them a good writing tool in which open identity, their own data and independent infrastructure simply work in the background.
-
Movement II
Bring existing blogs to Nostr
Many potential writers do not start from zero.
They have published years of work on their own blog or on platforms such as WordPress, Ghost or other publishing systems.
So MyEditor is to get a high-quality import of existing content.
Articles, titles, publication dates, descriptions, pictures and further metadata should come across as cleanly as possible and then be editable in MyEditor.
Moving to Nostr should not mean leaving your past work behind.
Do not start over. Bring your blog with you.
-
Movement III
Build in the EINUNDZWANZIG infrastructure
For members of the EINUNDZWANZIG association, MyEditor is to become a simple way into the association’s existing Nostr infrastructure.
The relevant services of the association should be connected as automatically as possible, in particular:
- the EINUNDZWANZIG relay
- the Blossom media server
- the existing Nostr identity and related services
- the connection to STANDUP
Instead of configuring server addresses and technical settings by hand, MyEditor should recognize which infrastructure a member has available and work it sensibly into the workflow.
The way to an EINUNDZWANZIG membership should also be reachable from this process for anyone interested.
This way MyEditor can also help make the association’s existing infrastructure actually usable for more people.
-
Movement IV
Direct handoff between MyEditor and STANDUP
The most important next step is the direct connection between the two applications.
A finished article should be prepared for STANDUP and handed over from MyEditor in a few clicks.
Title, summary, cover, tags, author details, media and the relevant NIP-23 information all come along.
A private draft then becomes not only a published Nostr article but, if you like, a concrete submission to STANDUP.
In the long run, this can grow into a real editorial workflow:
- MyEditor
- Submission
- STANDUP
- Curation
- Publication
Writers and editors would work together over an open protocol, without handing their texts, identity or publishing rights to a central platform.
-
Movement V
A publication check before publishing
Before an article is published or handed to STANDUP, MyEditor should be able to check that everything important is in place.
For example:
- a title
- a summary
- a cover
- fitting tags
- media that can be reached
- complete required metadata
- an article correctly prepared for NIP-23
In the end the writer gets one simple answer:
- Ready to Publish
- Ready for STANDUP
Especially for new users, this keeps technical details of Nostr or missing metadata from surfacing only after publishing.
-
Coda
Also planned: scheduled posts
As an extra, I want to make scheduled publishing possible.
Writers should be able to prepare a finished post in MyEditor and set the time it goes out.
Since MyEditor is a desktop application that does not have to stay open, scheduled publishing is to run through a centrally operated EINUNDZWANZIG service.
The post can be prepared and left for a later time. The publishing itself then happens automatically at the set time.
For blogs, series, regular posts or content prepared by an editorial team, this is a real gain in comfort.
The core idea of MyEditor stays the same: the writer keeps control of their identity and their content, while the central service only carries out the timing.
The goal
MyEditor is not meant to become just another Nostr client.
I want to create a workspace where people can write without first having to understand how relays, event kinds, Blossom or NIPs work.
The writer focuses on the text.
Nostr takes care of identity, sync and publishing in the background.
EINUNDZWANZIG provides infrastructure and community.
STANDUP then takes on editing, curation and distribution.
Several existing building blocks become one connected workflow:
- MyEditor: writing
- Nostr: identity and data
- EINUNDZWANZIG: infrastructure and community
- STANDUP: curation and publication
And it all begins with a program that anyone can install on Windows, macOS or Linux and use right away.
Censorship-resistant publishing as a desktop app, not a technical hurdle.
With funding of 1,500,000 sats, I want to build exactly this connection.




