He did and its merged!

Take a look at

Not with

Here is a draft spec. https://gitworkshop.dev/

Have you tried on gitworkshop?

I did think about adding optional 402 to grasp git endpoints to enable operators / self-hoster to make dealing with inefficent use by AI crawlers profitable.

Reach out if you need anything or have any questions. I'd recommend gitworkshop.dev/danconwaydev.com/ngit-grasp if you are self hosting.

I saw your bounties implementation, but I felt it was too tightly-bound to LNURL and gives too much credence to the code creator vs the reviewer, when the biggest costs are in the review. What do you think about ideas in this thread? ie. leaving the payment out of band? https://gitworkshop.dev/

I think they have done a good job so far

Those requirements were from earlier days of ngit. You dont have to self-host anything as there are public grasp servers you can use or self-host your own. With ngit you have the freedom to switch from self-hosted to hosted and back again with no user disruption. If you have a repo on your self hosted gitlab, a collaborator needs to create an account on your instance - that's friction whereas with ngit, their nostr account can be used.

Do you have any repositories on github or a git server?

as it stands you can use any git server and not use the nip34 'state' event, but it sort of feels like ngit supports too many different ways of doing things which prevents it from being simple.