Nostr Web Client

To build an effective, scalable, nostr, we need to go back to first principles. Brain dump:

- The web is based on the URI, HTTP and HTML

- It is the URI that ties the whole web together aka The Hyperlink

- Adding hyperlinks to a document or data allows it to be web scale

- The web enabled a syntax to allow hyperlinks to be added to docs

- The web enabled a syntax to allow hyperlinks to be added to data

- Data and documents are different things

- Data is real data, meta data and headers are for documents

- Hyperlinks are global variables aka super keys

- Typed links are also part of the web

- The order of hyperlinks is generally not recorded in a document

- All hyperlinks in a document form a Set

- Nostr is a subset of HTTP, using the websockets protocol

- Nostr transmits notes from one user to another, using relays

- Adding hyperlinks to nostr allows it to be web scale

- Data should be separate from transport

- Nostr has unique users which are also a pubkey

- A user can have a list of things as an array

- An array of things can have a user

From these simple principles a web scale flavour of nostr can be delivered

Please Login to reply.

How would you tie a note to a URL? 🤔

web became popular for the same reason it broke:

anyone can publish a website, consisting rendered layout and executable script.

now how do you build a popular web alternative:

anyone should be able to publish content, consisting of a rendered layout and executable script.

and how it will break:

everyone will use same centralized apps consisting of advertisers and censors.

how not to build a web alternative:

- keep it simple plain text

- limit functionality by the popular applications

- define functionality in single github repo