Publish anything, your way
Put files on your own chain, whether a website, a document, a photo or a PDF, and choose who can read them.
You can now publish any file from NAOMS: pages, notes, PDFs, images, audio, video. Publish to yourself, to your group (hive members only), or to anyone who has the address.
There is no hosting company in between. Your files sit on a chain you control, and your own device serves them.
What publishing is
A chain is the signed, append-only record that holds your data. Publishing means adding files to it. Each file is stored with the identity that signed it, so a reader can see who published it.
The web usually puts your content on someone else's server, under someone else's domain and terms. Here you need no hosting provider and no domain name.
It is not only websites
A file can be a web page, a style sheet, a Markdown note (shown as a readable page), plain text, data, an image, a font or a PDF. The command-line tool also sends audio and video.
New on 7 October: a folder called sites/ becomes a small website. A path like sites/garden/index.html is a site named garden, and only the chain's owner can publish it.
A walk-through
Mira keeps a garden journal. She makes a folder on her laptop holding sites/garden/index.html, a style sheet and some photos.
- She runs
naoms pages publish ./my-folder. The files go to her personal chain. - NAOMS asks for her approval, because publishing is an approval-gated action.
- The whole folder goes up in one go, all or nothing. On later runs, unchanged files are skipped.
- A visitor opens her chain's address ending in
/sites/garden/on a device running NAOMS that can reach her data.
She can do the same from the Pages app, which has a file tree, an editor, Preview and Publish buttons, and a picker for where to publish.
Who can read
Only you. Be honest with yourself here: there is no everyday "only me" switch yet. Today, "only you" means not sharing the address.
Your group. On a hive, our shared-group chain, and on chains inside it such as a channel or a repo, published files default to members-only reading. The choice is made per chain, not per page.
Anyone with the address. On other chains, anyone holding the address can open the files, with no account or login. The address is what you share.
Safe by design
Only the chain's owner can publish, replace or remove anything under sites/, and a sites/ file is served only if the owner signed it. Published pages also block scripts, so a page cannot run code in a visitor's browser.
Who it is for
Anyone who wants to share a journal, a portfolio, a PDF or a family photo page without renting a server. It also gives people building on NAOMS a simple way to put content on a chain and serve it by address.
What's next
- Coming next: a public web address for your site, with your approval. Today a visitor needs an address that goes through a NAOMS device.
- Coming next: a simple "only me" choice, per chain or per page.
- Coming next: easier big videos. Today large videos need a connection setting raised.
Written by AI agents from real project logs; owned and edited by Mujo.