a nostr web interface in vanilla JS https://nostr.ch/
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Go to file
OFF0 ad81d892e1
routes: use generic view containers
proof of concept to use generic view containers instead of specifc
functions to show and hide particular views.

a view has an identifier (path) which is used to subscribe to
relevant data. changing a view updates the history so that browser
back displays the last view. each view container has its own
scrollbar so that the scrolling position should be preserved when
changing back and forth between different views.

this change also removes CSS tabs in favor of view or overlays
such settings or write a new text note.

profile and notes deeplink use now native HTML anchors to improve
accessibility (copy/paste, open-in-new-tab, search engines).
2 years ago
src routes: use generic view containers 2 years ago
tools add an about page 2 years ago
.gitignore initial 2 years ago
.woodpecker.yml add an about page 2 years ago
LICENSE initial 2 years ago
README.md docs: update links in the readme file 2 years ago
esbuildconf.js nip-13: mine pow async in worker any only invoke noxy with pow 2 years ago
package-lock.json 0.0.23 2 years ago
package.json 0.0.23 2 years ago

README.md

nostr web client

this is a web interface to nostr. a live instance is hosted at https://nostr.ch/

some useful resources:

dev

nodejs v18.x and npm v8.x are recommended.

after npm install, start by running a dev server with:

npm run serve

and point a browser to http://127.0.0.1:8001/

the serve command injects a live reload snippet. to build a "production" copy, execute

npm run build

the build is done using esbuild, with a config in esbuildconf.js. the result is placed in dist directory.

release

  1. make sure version field in package.json as seen by remote git on master branch matches the tag created in the next step.
  2. tag a commit on master branch with a git tag v<vesion>.
  3. push the tag to the remote: git push --tags.

the CI then receives a git tag event, executes npm run build, creates a tar.gz with all the files found in dist directory and uploads it as a new release artifact. the release is named after the tag name.

the idea is that nostr web instances are then notified about a new release, download the tar.gz archive and update their local copies. this is not yet implemented. at the moment, the CI symply rsync's dist/ with a remote on https://nostr.ch.