From 3beaca87c8caffa7adc684332e2cc9f03619e720 Mon Sep 17 00:00:00 2001
From: BlowaterNostr <127284497+BlowaterNostr@users.noreply.github.com>
Date: Tue, 9 May 2023 18:32:26 +0800
Subject: [PATCH 1/4] Create 1078.md

---
 1078.md | 2 ++
 1 file changed, 2 insertions(+)
 create mode 100644 1078.md

diff --git a/1078.md b/1078.md
new file mode 100644
index 00000000..86dc357b
--- /dev/null
+++ b/1078.md
@@ -0,0 +1,2 @@
+# Customized Application Data, but as a regular events
+Everything is the same as NIP78, except it's a regular event kind 1078 so that replays don't remove the old event.

From 399b92153ab19c54dfa59f2b3262b6ab48b23766 Mon Sep 17 00:00:00 2001
From: BlowaterNostr <127284497+BlowaterNostr@users.noreply.github.com>
Date: Sat, 15 Jul 2023 00:14:53 +0800
Subject: [PATCH 2/4] Update 1078.md

---
 1078.md | 21 +++++++++++++++++++--
 1 file changed, 19 insertions(+), 2 deletions(-)

diff --git a/1078.md b/1078.md
index 86dc357b..1c9eb9f9 100644
--- a/1078.md
+++ b/1078.md
@@ -1,2 +1,19 @@
-# Customized Application Data, but as a regular events
-Everything is the same as NIP78, except it's a regular event kind 1078 so that replays don't remove the old event.
+# NIP-1078
+
+## Arbitrary custom app data
+`draft` `optional` `author:BlowaterNostr`
+
+## Nostr event
+
+This NIP specifies the use of event kind `1078` which is almost identical to 30078 except that it's not a replacible event.
+
+## Some use cases
+The reason to not having a 30078 is that some clients want to implement local state changes as CRDTs, meaning support cumulative and associative mutations.
+
+Meaning the order of applying operations doesn't change the final result as long as the same set of operations are applied.
+
+For example, in [Blowater](https://blowater.deno.dev), Pin/Unpin Contacts is implemented as regular events to achieve better consistency.
+
+Event set [`Pin Npub X`, `Unpin NpubX`, `Pin Npub Y`] will result in a pin list of `[Y]` no matter how the order is shifted.
+
+Many other operations are best implemented as CRDTs as well.

From 25d071f69a649230f65805cbcc68833a8a6e2159 Mon Sep 17 00:00:00 2001
From: BlowaterNostr <127284497+BlowaterNostr@users.noreply.github.com>
Date: Sat, 15 Jul 2023 00:25:28 +0800
Subject: [PATCH 3/4] Update 1078.md

---
 1078.md | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/1078.md b/1078.md
index 1c9eb9f9..76de312f 100644
--- a/1078.md
+++ b/1078.md
@@ -5,13 +5,16 @@
 
 ## Nostr event
 
-This NIP specifies the use of event kind `1078` which is almost identical to 30078 except that it's not a replacible event.
+This NIP specifies the use of event kind `1078` which is almost identical to [30078](https://github.com/nostr-protocol/nips/blob/master/78.md) except that it's not a replacible event.
 
 ## Some use cases
-The reason to not having a 30078 is that some clients want to implement local state changes as CRDTs, meaning support cumulative and associative mutations.
+The reason to not having a 30078 is that some clients want to implement local state changes as [CRDTs](https://crdt.tech/), meaning support cumulative and associative mutations
 
-Meaning the order of applying operations doesn't change the final result as long as the same set of operations are applied.
+Cumulative and associative means the order of applying operations doesn't change the final result as long as the same set of operations are applied.
 
+Using regular events can reserve the event/operation history thus the client can recompute the final state easily. [Figma uses CRDT to implement their vector design system.](https://www.figma.com/blog/how-figmas-multiplayer-technology-works/)
+
+## Implementations
 For example, in [Blowater](https://blowater.deno.dev), Pin/Unpin Contacts is implemented as regular events to achieve better consistency.
 
 Event set [`Pin Npub X`, `Unpin NpubX`, `Pin Npub Y`] will result in a pin list of `[Y]` no matter how the order is shifted.

From 7cb0e77d3e87c326c8da42ace99c8f3d1dc01a57 Mon Sep 17 00:00:00 2001
From: BlowaterNostr <127284497+BlowaterNostr@users.noreply.github.com>
Date: Sat, 15 Jul 2023 19:05:05 +0800
Subject: [PATCH 4/4] Update 1078.md

---
 1078.md | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/1078.md b/1078.md
index 76de312f..b9edcdb6 100644
--- a/1078.md
+++ b/1078.md
@@ -7,6 +7,19 @@
 
 This NIP specifies the use of event kind `1078` which is almost identical to [30078](https://github.com/nostr-protocol/nips/blob/master/78.md) except that it's not a replacible event.
 
+### Format
+#### Private Configs
+Private config should be encrypted using Kind-4's algorithm and stored in `content`. Technically the plain text content can be in any format, but it's best to use a JSON format of the following shape
+```
+content: {
+  "client": "the client name, url for web client or NIP-89 identifier"
+  ... the rest can be whatever the client author decides to be.
+}
+```
+
+#### Public Configs
+Similar to [NIP-78](https://github.com/BlowaterNostr/nips/blob/master/78.md#nostr-event), configs should be stored in `tags` and can be anything.
+
 ## Some use cases
 The reason to not having a 30078 is that some clients want to implement local state changes as [CRDTs](https://crdt.tech/), meaning support cumulative and associative mutations