NAOMS Devlog

Building a sovereign, local-first memory & identity system — in the open, honestly.

Bring your data in

NAOMS now has one place, Import data, where you can pick a source such as a contacts file or a LinkedIn export and bring what you already have onto your own device. Here is what works and what is still held back.

Product Teacher free October 28, 2026·3 min read·craft
TL;DR What the Import data hub is, how to bring in contacts from a file or a LinkedIn export, and an honest list of which importers are real, unconfirmed, held back or not built.

You probably already have years of your life sitting in other places: contacts in a phone, connections on LinkedIn, mail, photos, files. Starting a new system usually means starting empty. NAOMS now has a front door for the opposite: a screen called Import data.

What it is

Import data is a grid of big logo tiles, one per source, opened from the owner menu. The whole tile is the button. You tap a source, do only that source's step, and land back on the grid. Progress shows in a small tray.

Everything lands on your own device. NAOMS has no central server holding your data. An import is a read, from the source into your own records.

Each tile is drawn from a description the importer ships, called a card. The hub holds no list of its own. If an importer is not built, its card says so and the tile says "Coming".

A walk-through: bringing in your contacts

  1. Open Import data and tap Contacts file (.vcf). This is the file you get when you export from your phone, Google or iCloud.
  2. Pick the file. It is read once, on this device.
  3. People arrive as contacts: name, email, phone numbers with country code, company.

LinkedIn works the same way. Request your data from LinkedIn, then pick the .zip it sends you (or its Connections.csv). A second tile, "LinkedIn (browser)", opens a separate browser window where you sign in yourself and NAOMS reads your connections slowly. It is marked unofficial and carries a warning, because LinkedIn's rules do not allow automated tools and your account could be limited. It never asks for your password and stops at the first challenge from LinkedIn.

Imported contacts are labelled with where they came from, and they are not made discoverable and not connected to anyone. They are your notes about people, not an invitation to them.

Who asks, and who approves

The address-book import first does a dry run: it shows how many people would be added, updated or left alone, and writes nothing. Your own tap in the hub is not asked for a second approval. The same operation started by your AI assistant raises an approval for you instead.

What works, and what does not yet

  • Unconfirmed, everywhere. A tile reads "Confirmed" only when a real-account test has recently passed. That record is empty today, so every tile honestly says "Unconfirmed". The contact importers have been exercised against local test files, not real accounts.
  • Held back: "Soon". Email, WhatsApp, Telegram, Discord and the GDPR export hold other people's words. Their tiles cannot be queued until a safeguard for that is verified, and none is verified yet.
  • Needs your own key. Google Drive, Dropbox and Google Contacts expect you to bring a Google or Dropbox app key. NAOMS ships no shared one.
  • Not built. Slack, Matrix and Microsoft sign-in are "Coming". Reading contacts directly from a phone has the plumbing on the receiving side, but no phone reader yet.

What's next

The next steps are real-account proof for the file-based importers, verifying the safeguard for the message sources, and finishing the phone-contacts reader. Until then, the file importers are the ones to reach for.

Written by AI agents from real project logs; owned and edited by Mujo.

← more in Product   home ✦   all →