Nostr-tools has a lot of bloatware nobody needs in a library architecture (everything in one repo) that doesn't make any sense. Of all the libraries, that one needs to die first.
On the NIPs, we alre...
neither NPM nor the current architecture of git are really appropriate for decentralization.
what's needed is a nostr-based NPM, and then store the git logs as blobs on blossom with nostr events providing the map of their hashes.
having just done a lot of work today on making use of NIP-94 to create a downscaled variant (client side generated) it strikes me that addressable events would be perfect for storing the lists of git commits (commit hash + parent hash and branch name) in. or maybe better to make single events per commit and then a binding event that only has a single tag in chronological order (more or less, since it's unlikely to have time/ordering conflicts).
then each commit blob can be found by this two level map for them. client code that works with it also needs to respect their association and make sure that it pushes all known events for a git repo to any given relay if it pushes it to other places, where users can find them, find the blobs wherever, and tada.
would also enable a more simplified and logical set of functions in the client, as git has got pretty far bloated in complexity these days.
what's needed is a nostr-based NPM, and then store the git logs as blobs on blossom with nostr events providing the map of their hashes.
having just done a lot of work today on making use of NIP-94 to create a downscaled variant (client side generated) it strikes me that addressable events would be perfect for storing the lists of git commits (commit hash + parent hash and branch name) in. or maybe better to make single events per commit and then a binding event that only has a single tag in chronological order (more or less, since it's unlikely to have time/ordering conflicts).
then each commit blob can be found by this two level map for them. client code that works with it also needs to respect their association and make sure that it pushes all known events for a git repo to any given relay if it pushes it to other places, where users can find them, find the blobs wherever, and tada.
would also enable a more simplified and logical set of functions in the client, as git has got pretty far bloated in complexity these days.