NIP-24: Add optional 'languages' field to kind 0 extra metadata #2159
+1
−0
Conversation
This file contains hidden or 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 enables new use cases, such as clients suggesting language-specific relays or building dedicated language-limited relays to improve content discovery and user experience in multilingual communities.
Member
Author
|
I'd like to change |
This commit updates the proposed `language` field to `languages` (plural) and changes it from a single string to an array of strings. Reasons for the change: - Many users are fluent in multiple languages and may want to indicate secondary languages they are comfortable with. - An array allows expressing language preferences with priority (first element = primary language). - Clients can use this to match users with relays supporting any of their preferred languages, not just one. - It better supports multilingual communities, content filtering, translation features, and discovery of language-specific relays. The field remains optional, and clients can continue to read only the first element for basic compatibility. Example values: - `["en"]` (English only) - `["ja", "en"]` (Japanese primary, English secondary)
mattn
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This pull request proposes adding a new optional extra field called
languages(plural, as an array) to kind 0 (user metadata) events in NIP-24.The field is an array of strings following the IETF BCP 47 language tag format (e.g.,
["en"],["ja", "en-US"],["es-AR", "fr", "en"]), indicating the author's preferred languages in order of preference (first element = primary).Motivation
Nostr is a global protocol with diverse multilingual users. Many people are fluent in multiple languages and want to indicate support for more than one.
A single-language field is limiting for such users. Changing to an array: