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

Editorial

Browse Source
This commit is contained in:
Melvin Carvalho 2023-03-05 10:43:21 +01:00 committed by GitHub
parent 5f2ec9a9da
commit 977058ca36
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
17.md
View File

@ -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. 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. 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.