From 7367fe2fcd2b63a62ec9015047f182e1545017cc Mon Sep 17 00:00:00 2001
From: Beemo <120607606+b35363@users.noreply.github.com>
Date: Sat, 19 Aug 2023 14:07:44 +0200
Subject: [PATCH] Update 101.md

---
 101.md | 15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/101.md b/101.md
index e770d35e..e900f796 100644
--- a/101.md
+++ b/101.md
@@ -1,20 +1,18 @@
-NIP-79
+NIP-101
 ======
 
-`window.nostr` offline message signature & verificiation
+Enhancing Event Compression and Encoding Support
 --------------------------------------------------------
 
 `draft` `optional` `author:b35363`
 
 ### Abstract
 
-This NIP proposes a modification to the WebSocket 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 futureencoding schemes.
+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.
 
 ### Motivation
 **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. 
 This NIP suggests leveraging encoding and compression techniques within the message payload to provide enhanced flexibility
 and compatibility.
@@ -39,7 +37,6 @@ example:
 - **EncodingInfo**: An **optional** field indicating the encoding used for the payload.
 - **Payload**: The actual payload data of the message.
 
-
 > Note that when not provided, the default encoding is set to default, for backward compatibility.
 
 #### 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. 
 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
 
 #### LZ77