nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-26 18:25:51 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update 101.md

Browse Source
This commit is contained in:
Beemo 2023-08-19 14:07:44 +02:00 committed by GitHub
parent b20cf672cc
commit 7367fe2fcd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
101.md
View File

@ -1,20 +1,18 @@
NIP-79 NIP-101
====== ======
`window.nostr` offline message signature & verificiation Enhancing Event Compression and Encoding Support
-------------------------------------------------------- --------------------------------------------------------
`draft` `optional` `author:b35363` `draft` `optional` `author:b35363`
### Abstract ### Abstract
This NIP proposes a modification to the WebSocket protocol to introduce a more flexible and modular approach for message compression and encoding. This NIP proposes a modification to the **Nostr** protocol to introduce a more flexible and modular approach for message compression and encoding. It suggests extending the current WebSocket message structure to include optional encoding information, such as _base64_, _base58_, _gzip64_, _gzip58_, and _plaintext_. This enhancement aims to improve modularity, retro-compatibility, and the potential for future encoding schemes.
It suggests extending the current WebSocket message structure to include optional encoding information, such as _base64_, _base58_,
_gzip64_, _gzip58_, and _plaintext_. This enhancement aims to improve modularity, retro-compatibility, and the potential for futureencoding schemes.
### Motivation ### Motivation
**WebSocket** is a widely used protocol for real-time communication between clients and servers. **WebSocket** is a widely used protocol for real-time communication between clients and servers.
While the WebSocket protocol itself ([ref. LZ77](#markdown-header-lz77)) supports message compression, While the WebSocket protocol itself (ref. [LZ77](#lz77)) supports message compression,
there are scenarios where direct WebSocket compression might not be sufficient or optimal. there are scenarios where direct WebSocket compression might not be sufficient or optimal.
This NIP suggests leveraging encoding and compression techniques within the message payload to provide enhanced flexibility This NIP suggests leveraging encoding and compression techniques within the message payload to provide enhanced flexibility
and compatibility. and compatibility.
@ -39,7 +37,6 @@ example:
- **EncodingInfo**: An **optional** field indicating the encoding used for the payload. - **EncodingInfo**: An **optional** field indicating the encoding used for the payload.
- **Payload**: The actual payload data of the message. - **Payload**: The actual payload data of the message.
> Note that when not provided, the default encoding is set to default, for backward compatibility. > Note that when not provided, the default encoding is set to default, for backward compatibility.
#### Supported Encodings #### Supported Encodings
@ -100,6 +97,10 @@ This NIP suggests a valuable enhancement to the WebSocket protocol by introducin
This approach offers improved modularity, retro-compatibility, and the potential for accommodating future encoding schemes. This approach offers improved modularity, retro-compatibility, and the potential for accommodating future encoding schemes.
By allowing clients and servers to selectively choose their preferred encoding, the proposed changes empower developers to optimize communication based on their specific requirements. By allowing clients and servers to selectively choose their preferred encoding, the proposed changes empower developers to optimize communication based on their specific requirements.
### Implementations
...
### References ### References
#### LZ77 #### LZ77