nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-11-09 22:09:06 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

syntax cleanup

Browse Source
This commit is contained in:
louhutchinson 2024-05-29 09:39:40 -07:00 committed by GitHub
parent a884973188
commit 816320fef5
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
74.md
View File

@ -67,6 +67,7 @@ unserialized JSON structure:
## Fields ## Fields
```
content: Root object for the sorting algorithm configuration. content: Root object for the sorting algorithm configuration.
algorithmName: Name of the sorting algorithm. algorithmName: Name of the sorting algorithm.
version: Version of the sorting algorithm. version: Version of the sorting algorithm.
@ -87,11 +88,13 @@ includeReplies: Boolean indicating whether to include replies.
includeMedia: Boolean indicating whether to include posts with media. includeMedia: Boolean indicating whether to include posts with media.
contentSafety: Level of content safety (safe, moderate, any). contentSafety: Level of content safety (safe, moderate, any).
promotedContent: Boolean indicating whether to include promoted content. promotedContent: Boolean indicating whether to include promoted content.
Rationale ```
## Rationale
This standardized configuration allows developers and platforms to implement consistent sorting and filtering logic across different social media applications. By using a common format, it becomes easier to integrate and extend sorting algorithms, providing a better user experience. This standardized configuration allows developers and platforms to implement consistent sorting and filtering logic across different social media applications. By using a common format, it becomes easier to integrate and extend sorting algorithms, providing a better user experience.
Compatibility ## Compatibility
This proposal is designed to be backward compatible with existing implementations by providing default values for new configuration fields. Platforms can gradually adopt the new configuration format without disrupting current functionality. This proposal is designed to be backward compatible with existing implementations by providing default values for new configuration fields. Platforms can gradually adopt the new configuration format without disrupting current functionality.