Define 56xx range #22
Draft
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
|
This is really cool. Reserving a block of 100 makes sense, and when we need more we can go beyond the current ranges of 5000-5999. One thing to keep in mind is that a popular kind id right now is 6666, although I don't know much about them. They seem to mostly contain data regarding relays, apnTokens, and addresses. So maybe we should make a note that people should avoid 5666? |
|
Recommend adding a checksum for the binary to ensure the correct binary is downloaded that is requested. |
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.
Still playing around if this is the correct input parameters but have one running here: npub1e222rh2n4eh4tf5900399mnpa06phl7zazvyng2cm95f57ja0alqg055t4