Add nip136 code packages kind 1036 #1347
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
See also: #1112 |
|
This is the same as #1112 right? Guessing it's out of scope here as well? |
No this is not the same, it doesn't suggest relays to host anything. All it does is describe a new event kind, it can't be out of scope. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposing this as part of Nostr Sites effort. A code package event is basically npm package on nostr, where files are stored on Blossom or other sha256-addressed servers, and the package event lists those files along with their relative paths within the package. Being able to fetch individual files using http (instead of downloading the whole package as zip archive) is useful for Nostr sites where specific assets are included selectively into the web pages. NIP136 text here.