Nostr Web Client

I like to offroad a lot... so much that I am specifically designing #notedeck and #damus #android so we can spin up new ideas quickly without having to build an entire cross-platform app for every nostr experiment.

notedeck will be the best interactive development environment for building nostr apps.

built in:

- nwc/zapping wallet

- signing

- multi account

- relay/fast database for local storage.

- local p2p sync

- relay sub/outbox toolkit

- ui toolkit of rendering notes, profiles, etc

you get all these for free so you can focus on building your app instead of protocol details.

no signing browser plugin needed. no bunker needed. you don't need to be a gigabrain coder to build something. vibe coders rejoice.

nostr:note1l5tuxrluulcy5gy6zflnpqy83x6stw2czm6rh2e25p4w9a0lfd5qjqk5m7

vinney...axkl 8mo ago

this all sounds completely awesome.

but! (sorry, I have a but...) do you find it at all worrying that all nostr development will actually turn into "notedeck development"? the browser and http are amazingly open systems. if more and more nostr applications and features "only work in notedeck", I would count that as a mild setback in internet openness progress.

will the "notedeck approach" be like an open protocol that other people can implement in their own software such that "Notedeck apps just work" in those other softwares, the way websites mostly "just work" in any browser? (see Chrome as the negative case there)

Reply to this note

Please Login to reply.

Discussion

jb55 8mo ago

not sure I understand your point. nostr is already a spec'd out protocol and has nothing to do with http or the browser ecosystem. damus currently doesn't build on the web at all, and provide native apps.

all I'm suggesting is building a rapid development platform for building nostr apps. these apps will be compatible with native nostr apps and web based nostr apps, since the thing that makes them interoperable is the underlying data model, relays, and nip01, not how they are implemented.

vinney...axkl 8mo ago

agreed that the way they are implemented doesn't impact interoperability, but it does impact access and proliferation. and I'm not even necessarily saying this is a negative thing, but imagine a world where 95% of nostr features and apps ONLY have an implementation in notedeck (because it is just that good. and I do believe it could be). is that a success mode or a failure mode?

vinney...axkl 8mo ago

"this thing will be too good!" is obviously not an argument against doing something! but it's an important context to be aware of ahead of time