started the process of breaking notedeck into two parts:

- the chrome (tab bar, location bar, back/forward button)

- the apps

so internally our columns app is called notedeck-columns. soon we will be adding notedeck-viz and notedeck-notebook.

These will be different apps that can exist alongside each other. For example, kieran's native zap.stream app can be loaded in a new "tab" when you click on a stream link in a column.

The browser will be responsible for the local relay, accounts, signing, possibly even subscription and connection management.

This means every app you use will be multi-account by default, and you don't have to worry about key security.

The everything app is coming.

nostr:note1atthw2u9cwgv26zzutspnwnu2zvtzskrgg3cxr8he6dtkw4pzlzqfert3l

Reply to this note

Please Login to reply.

Discussion

will it be possible to interact with the local relay from the host system? i.e. a basic api for some simple stdin and stout?

you can do this with the nostrdb commandline tools:

you had me at “nostrdb commandline tools”.

tremendously excited about this entire paradigm.

does the embedded relay have a listen address that exposes the ws api?

no but it wouldn’t be that hard to do

Native zap.stream can be loaded in a separate tab?

yup

On which OS? I know about Android intents, is that something similar?

it would load within notedeck, the native nostr browser I'm working on.

works on all OS's

Looking forward to it

Can’t wait to see what comes out of all this 👏

for inspiration what to build , man can go to https://nostrapps.com