We can have the entire Git repo as Nostr Events. The hard part is to keep a single head for all files given that Nostr doesnt have a timechain. But we will figure it out.
Discussion
Btc timestamp right ?
yep
git in itself is a state chain. every commit id is a hash of all previous changes. that way you can be certain you aren't missing any data.
I thought the hard part was identifying who the authoriative maintainers are fpr a repository if they change overtime, such as bitcoin-core. I proposed https://github.com/DanConwayDev/ngit-cli/tree/v0.0.2 which uses OpenTimestamps.
Someone then pointed out that you can embed this information right into the commit history and contributors will 'build on top of' whichever history they don't object to. Overtime the longest chain (of quality commits, by contributors we trust), will determine the authorative maintainers.
This is what ngit optionally does when you run `ngit init`.
Timestamp based Single use seals is what i was thinking. Linked to ones npub. Can be revoked, updated, passed on, as maintainers come and go.
Oops. Missed the "show more" and did not read the full note.
From the link: "Forks are replaced by permissioned branches."
Replaces the whole "key holder" issue. If i understand correctly. Neat.
So as a project moves through its life cycle, a baton of sorts is passed on to the next endorsed npub or the most popular branch. This eliminates a bunch of friction. Organic. Neat.
User expectations/behavior will have to change. Particularly around malicious fake accounts and noobs.
"Large patches and binaries would need to be transported separately and referenced in a stub patch event."
Which is where the convenience of Github comes in. Potential security issues too.
Forward looking though its also an oportunity for V4V storage.
I created a POC for an entire git repo as nostr events in May 2023. you can try it out:
https://github.com/DanConwayDev/ngit-cli/tree/v0.0.2
My conclusion was that it isn't the right approach. git is very efficient at storing and accessing the data, working out the differences between repositories and bandwidth efficiently sending the right data.
I agree. But using Nostr with Git is not supposed to be efficient. Just decentralized. Nostr itself is not efficient to begin with.
nostr:nprofile1qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshszrnhwden5te0dehhxtnvdakz7qpqahaz04ya9tehace3uy39hdhdryfvdkve9qdndkqp3tvehs6h8s5sl8p9ks is innovating on and around this and I'm really looking forward to seeing what he comes up with gnostr.
I’ve already created a “timechain” of #nostr events…
https://x.com/randymcmillan/status/1764056522965831753?s=46
#gnostr
Getting ready to create “blob signatures” - this way even thru a rebase or whatever - the origin of the blob can be verified… 
also nostr:nprofile1qyv8wumn8ghj7un9d3shjtnrw4e8yetwwshxv7tf9uq36amnwvaz7tmwdaehgu3wvf5hgcm0d9hx2u3wwdhkx6tpdshsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qqs9njktmqadt322myw6eag6f8qxuzl0wv9vpe7zxkn0d73fhy3s7qsaq9shr and nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpr9mhxue69uhhyetvv9ujuumwdae8gtnnda3kjctv9uq3gamnwvaz7tmjv4kxz7tpvfkx2tn0wfnj7qpqu9e887ad8pl49cxgzqkuljxcxy89dtac7jkyuajnukxg6hu2hufqmxzy8a are innovating with an approach using mercke DAGs in GitNestr. I'm excited to see that as well.
It’s become so much more. 🤟 Merkle DAGs were just one piece of the puzzle. 🧩
Never say never :-)
I’ve already created a “timechain” of #gnostr git commits…
#nostr