yosup/web
William Casarin 45b36a9945 Unknown event fetching
Damus will now try really hard to find unknown events. It will use the
event relay hints to connect to new relays and fetch any id that is
missing.
2022-11-20 13:35:44 -08:00
..
css switch to new share spec 2022-11-20 09:28:35 -08:00
icon web: Added new loader graphic. 2022-11-19 11:20:15 -08:00
img web: move webv2 to web 2022-11-11 12:10:39 -08:00
js Unknown event fetching 2022-11-20 13:35:44 -08:00
.gitignore web: move webv2 to web 2022-11-11 12:10:39 -08:00
COPYING add license 2022-11-11 17:41:38 -08:00
index.html web: added alpha sticker 2022-11-19 11:20:15 -08:00
Makefile debug alby again... sigh 2022-11-18 07:39:16 -08:00
README.md Added Known Issues section to README.md 2022-11-14 19:58:55 -08:00

Damus Web

Here lies the code for the Damus web app, a client for the Nostr protocol. The goal of this client is to be a better version of Twitter, but not to reproduce all of it's functionality.

Issue Tracker

Roadmap

Here is what is confirmed for development.

  • Share event
  • Profile view (with ability to follow user)
  • Edit metadata (from profile view)
  • Global timeline view
  • Notifications view
  • Settings view (with ability to configure relays)
  • Multiple reaction picker
  • Direct Messages (subject to discussion)

Contribution Guide

There are rules to contributing to this client. Please ensure you read them before making changes and supplying patch notes.

  • No transpilers. All source code should work out of the box.
  • Keep source code organised. Refer to the folder structure. If you have a question, ask it.
  • Do not include your personal tools in the source code. Use your own scripts outside of the project. This does not include build tools such as Make.
  • Use tabs & write JS with snake_case. End of discussion.
  • Do not include binary files.
  • No NPM (and kin) environments. If you need a file from an external resource mark the location in the "sources" file and add it to the repo.
  • No frameworks. Learn the browser tools and write good code.
  • No experimental browser APIs.
  • Do not write animations in JavaScript, CSS only. Keep them short and snappy. Animations should not be a forefront, but an enjoyable addition.
  • All new & modified code should be properly documented.
  • Source code should be readable in the browser.

These rules are subject to discussion.

Style Guide

TODO Write about the style guide.

Terminology

  • Sign Out - Not "log out", "logout", "log off", etc.
  • Sign In - Not "login", "log in", "signin", "sign-in", etc.
  • Share - Not "boosted", "retweeted", "repost", etc.
  • Send - Not "tweet", "toot", "post", etc.
  • Link - Not "share".

Known Issues

  • You cannot send events when running from an IP address that is not secure. Work arounds are not known at this time.