From 977058ca36c10cff398fbefdb15e3ce41fc528ca Mon Sep 17 00:00:00 2001 From: Melvin Carvalho Date: Sun, 5 Mar 2023 10:43:21 +0100 Subject: [PATCH] Editorial --- 17.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/17.md b/17.md index a3c48079..b9f14df1 100644 --- a/17.md +++ b/17.md @@ -26,7 +26,7 @@ Tracking Git Commits with Nostr enables **use cases** similar to: but without central points of failure. The aim is to create continuous distributed software development processes, without having to rely on complex or centralized services. The first implementations will be designed to illustrate these use cases in more detail. -You need only know the **nostr ID or bech32 form of a repo** and you will be able to discover all versions, its origins and its history. +You need only know the **nostr ID or bech32 form of a repo** and you will be able to discover all versions, its origins and its history. The repo itself will be able to communicate with nostr. Git object data is not designed to be stored in nostr, instead, nostr will store the signaling, update, version or commit data. Git object data will live in existing git repositories, github, gitlab, gitea, gogs, ssh, file system etc.