NIP-800: Define BDD Payload Execution Protocol (because 800 and BDD are a match made in alphanumeric heaven) #1717
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
added 2 commits
January 28, 2025 14:21
…re a match made in alphanumeric heaven) While breaking convention by jumping to NIP-800, the alphanumeric and visual similarity between "800" and "BDD" is too perfect to ignore. This synchronicity aligns with the purpose of the protocol, making it instantly memorable and symbolically representative of the structured nature of BDD itself. Some conventions are worth bending for elegance.
|
Please get rid of the stringified json object inside the .content and move those properties to the tag array as usual. |
|
I don't get the value prop, a regular server is much better for arbitrary computation than relays, which are specifically scoped down for interoperability. |
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.
While breaking convention by jumping to NIP-800, the alphanumeric and visual similarity between "800" and "BDD" is too perfect to ignore. This synchronicity aligns with the purpose of the protocol, making it instantly memorable and symbolically representative of the structured nature of BDD itself. Some conventions are worth bending for elegance.