How's the gnostr stuff going?

In my proposal there are multiple packs relating to groups of commits in the history so the hashes don't change. Uding ^2 exponential.

Whilst smaller project often don't require advanced git features such as shallow clones and no-blob, they are essential for my larger open source projects. My goal is to make git nostr so attractive for open source projects that they all want to use it, no matter their size or complex.

Ultimately I prefer the trade-off of using a git server as its fundimantally compatible with all git usages (shallow sync, no-blob, etc) and git tooling. Grasp enable using the battle-tested, flexible and widely used git client-server model but frees it from a single server and moves the trust and authentication onto nostr. My guiding principle has been: let git be git and let nostr be nostr.

@nprofile1q... I considered using blossom, in fact I even wrote some code. @nevent1qqs... I thought the most efficent approach would be to store git packs as blossom blobs. I havent studied your code but from the documentation you are somehow using 2mb chunks? I can see how its naturaly evolved from your 'files' usecase.

O. I thought that meant that it is online now but some sort of source fallback may not be yet. What exactly is online now?

I'm not seeing that comment.

This is because a git repository can't be found at the git.gitter.space address listed in the announcement. @nprofile1q...?

How was the process?

Let every client be a git nostr client
@nevent1qqs...

ask and you shall receive
@nevent1qvz...

Most of the time when paying online, banking app authorisation is part of the payment flow. Never irl. Probably using a VPN and a privacy email address increases the likelihood of this extra step being required.