DanConwayDev

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.

2026-07-22 19:50:54 CEST

- reply

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

2026-07-22 18:29:54 CEST

- reply

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.

2026-07-22 18:29:39 CEST

- reply

If you just want to clone and pull with a grasp repository you can use any of the git servers listed in the annonucement event. I did this draft grasp spec to allow someone to push with a standard git client https://gitworkshop.dev/nevent1qvzqqqqx2gpzpgqgmmc409hm4xsdd74sf68a2uyf9pwel4g9mfdg8l5244t6x4jdqy88wumn8ghj7mn0wvhxcmmv9uq3xamnwvaz7tm8d96xummnw3ezucm0d5hsqgrwmpmlfdc8vzjvemlk4z055lccugf3w4tyer4sl4yujt2tva057vlukhdr

2026-07-22 18:04:05 CEST

- reply

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?
#nevent1q…6xlc
https://gitworkshop.dev/nevent1qvzqqqqx25pzqen829vwvvu0az0a5svwg2st72n69vfj2pxax3lszkscjudkg3psqyfhwumn8ghj7emfw3hx7um5wghxxmmd9uq3camnwvaz7tmwva5hgtnyv9hxxmmwwashjer9wchxxmmd9uqzqllj0fhhwrxwmmnh7v9pg8v6vv4djtjtvza7xhzfty5yhrgh02ex25vz20

2026-07-22 17:31:56 CEST

- reply

The impermanence option to really enforce a config driven environment is really what makes it satisfying

2026-07-22 17:31:04 CEST

- reply

nixos is for users who like delayed gratification. AI has made it a lot easier.

2026-07-22 17:29:08 CEST

- reply

I've been daily driving nixos desktop for 1 year+ so I might make an electron build with nix. I moved from QubeOS so I was used to pain.

2026-07-22 17:12:34 CEST

- reply

What if someone wants to collaborate / request a feature?

2026-07-22 17:11:15 CEST

- reply

Thanks. I'd like to add some more Project Management features to gitworkshop but right now I'm not hearing that much demand for these features.

2026-07-22 17:05:55 CEST

- reply

How is it centralised? You can chose any number of grasp servers you want and / or self-host your own with ngit-grasp?

2026-07-22 16:33:20 CEST

- reply

How can I remove the friction / barriers?

2026-07-22 16:26:32 CEST

- reply

There have been 1 or 2 attempts at this. I thought about doing it as an option bundled in ngit-cli, but uiltimately, its never made it to the top of the todo list. If you have created a PR with nostr, and nostr signs each push, you are signing the data anyway with nostr.

2026-07-22 16:21:29 CEST

- reply

Don't the bans and project deletions with no stated or good reason and no recourse appeal worry you?

2026-07-22 16:16:47 CEST

- reply

That's useful feedback. I figured this was one of the main blockers for people but you're the only one to mention it in this thread. solutions to this (self-hosted and paid) are coming pretty soon. I'm using it right now.

2026-07-22 16:11:57 CEST

- reply

I understand you cook food rather than cooking code or do you do both?

2026-07-22 16:06:09 CEST

- reply

There isn't one atm. gitworkshop is a web client. There is an andriod build using capacitor. I could create an electron build if you like? I see you are a nixos user so you might not find that satifying.
The ngit cli is available cross platform and can be installed via the nix flake https://ngit.dev/install

2026-07-22 15:29:53 CEST

- reply

Currently this is not supported but people have raised this as need. Many project that are intended to be open-sourced start out on a private repo until its mature enough to be announced. I do have a plan for this, that involves orivate grasp-endpoints per group using NIP-42 auth, but I want to gauge the demand and how much this is really a blocker for adoption.

2026-07-22 15:25:06 CEST

- reply

There was time when I was running the only 2 grasp serrvers on 2 under-resouced VPSs with bad uptime. As adoption grows I think more professional operators and the redundancy that grasp offers will make it a more solid option than relying on a single centralised entity.

2026-07-22 14:59:08 CEST

- reply

Thanks, There maybe something we could do on the grasp side for this.
You have been using ngit alongside github for a while now for Amber which is great to see! People submit Issues and PRs on both but mainly on Github.
You create 100s of PRs for Amber on Github. Why not ngit?

2026-07-22 14:37:38 CEST

- reply

I have poured the last 3 years of my life into hand-crafting ngit. There are many intergration tests. I have embraced AI in my development flow in the last 8 months so it depends what you mean by vibed. We are still early when it comes to adoption, but the more usage and bug reports I get the more stable it will become.

2026-07-22 14:22:25 CEST

- reply

Thanks. Maybe an awesome-ngit repo would help with understanding the projects in the space.

2026-07-22 14:19:05 CEST

- reply

Well thanks for being honest at least. How would you know if it's buggy if you don't try it again? How can I fix the bugs if no one reports any?
Thanks for your feedback

2026-07-22 14:14:20 CEST

- reply

Agents work flawlessly with ngit as a drop in replacement for github if you install the skill at https://relay.ngit.dev/npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr/ngit.git
If you moved everything to ngit, they would still be in one place. its just a one-time effort.
Thanks for your feedback.

2026-07-22 14:07:26 CEST

- reply

I'm not sure when you tried it but there have been a lot of improvements. I'd recommedn either use the default grasp servers or running https://gitworkshop.dev/danconwaydev.com/ngit-grasp let me know how you get on.

2026-07-22 13:28:28 CEST

I need your help in prioritising what I work on. Why aren't you using ngit/grasp as your primary git forge?

2026-07-22 09:55:16 CEST

- reply

Do you have opinons on git related nips? I'd love to hear them.

2026-07-15 21:56:25 CEST

- reply

I think they have done a good job so far

2026-07-08 19:16:01 CEST

- reply

Absolutely!

2026-07-08 19:10:52 CEST

- reply

And / or use grasp servers offered as a service.

2026-07-07 21:09:42 CEST

- reply

Just released v2.6.2 should fix this and provide some defense in depth to prevent this from happening.

2026-07-06 09:51:16 CEST

- reply

can you link to some specific PR it is happening with?

2026-07-06 09:08:06 CEST

- reply

Thanks for the report. Are you on the latest version?

2026-07-02 21:04:30 CEST

- reply

What is the purpose of a lawn?

2026-06-30 15:07:07 CEST

I love how https://nostrhub.io 2.0 glues everything together. Good work @npub1scv…68d8, @npub1q3s…d26p.

2026-06-26 22:16:37 CEST

ngit-cli v2.6.0 is out: new ngit merge, issue auto-close from commit messages, better clone discovery via git index relays, improved bunker login, safer push/state publishing, tag push cleanup, fixes for PR merges/force-pushes and more. https://ngit.dev/install

2026-06-22 15:23:11 CEST

- reply

I'm really open to feedback. In addtion to NIP-34 and GRASP, I'm using these more experimental kinds: https://gitworkshop.dev/danconwaydev.com/gitworkshop/tree/main/NIP.md
I'm starting to doubt whether the CoverNote idea is really better than some for of 'edit' of PR / Issue Patch kinds.

2026-06-22 12:23:17 CEST

- reply

https://haven.danconwaydev.com/001e8f6ac78b307e1b8e788ecc9461624bf949bef2d5eb027f0a642925e02448.png

2026-06-19 21:09:32 CEST

This could be the foundation of something transformational
#nevent1q…se30

2026-06-19 21:07:06 CEST

- reply

This has a lot of promise.

2026-06-19 17:27:02 CEST

- reply

Do you mean @nprofile…d9y2 and https://walletscrutiny.com ?

2026-06-18 15:36:52 CEST

- reply

Thanks!

2026-06-12 13:28:31 CEST

- reply

On top of the NIP-34 issue spec, ngit and gitworkshop currently support these three extra features: 1) post issue creation labels/tags, 2) editable issue subjects and 3) CoverNotes - editable pinned note with version history designed similar to an editable issue description. Here is the spec I am using: https://gitworkshop.dev/danconwaydev.com/gitnostr.com/gitworkshop/tree/main/NIP.md#shared-issue-patch-pr-metadata

2026-06-11 14:21:23 CEST

- reply

Can you expand on 'any form of free communication may require compute power in the future'?

2026-06-08 20:14:32 CEST

- reply

I like this approach. Significant effort goes into curating NIPs, I'd like to be able to delegate my 'view' of the NIPs to a committee and publish variations for specific NIPs. This way my overall view doesnt go stale. I'd also like to inspect other people's view, particilar their explicit variations.

2026-06-01 23:08:32 CEST

- reply

They were empty. Isn't it a nicer user flow to use a default set (that amethyst automatically updates based on the relay landscape) when the user hasn't signed the corresponding events? I don't really want to sign an event to just enshrine defaults.

2026-06-01 22:18:42 CEST

- reply

I also get this to the extent that I've learnt to recognise about 10 users by their npubs.

2026-05-22 17:21:27 CEST

Thanks @npub1qny…95gx for the ngit shoutout on @npub10ut…xdlq. Is this the nicest thing you have ever said about a nostr client name?
https://haven.danconwaydev.com/5c6cec8384862d93723803afe869886d22f3bf5ca83f8ed6fe1f286122bc97c1.mp4
#nevent1q…7fzc

2026-05-22 09:31:51 CEST

- reply

No. What sort or issues? What sort of timeframe?

2026-05-21 23:56:07 CEST

I think @npub19yw…322j might invent fire. There is a new paradigm out there that frees us from the feed. Who is going to discover it?

2026-05-19 10:52:53 CEST

- reply

Heresy! Are you just trying to stir up controversy because nostr is devoid of it this week? In terms of theatre, its second only to the syphon https://www.youtube.com/watch?v=mvmRtPGR4C4

2026-05-15 10:20:01 CEST

- reply

More issues / PRs are showing up in the counts now. That's a cool design decision to show issue / PRs from other sources. Are you using https://nips.nostr.com/34#status for issue / PR status? The statuses aren't showing on any PRs/Issues on that gitworkshop repo.
I'm also getting inconsistent grasp / relay lists for the same repo.
https://blossom.primal.net/fd42131396324e3503d62544b9bc3173e1af136e107fee9728a1204b1076fce8.png
https://haven.danconwaydev.com/0fa3c0a0895c089a71dbf42d2b13ecf2c8ef695427978f306568914978afad76.png
the repo announcement event uses (3 of which are grasp servers):
```
[
"relays",
"wss://gitnostr.com",
"wss://relay.ngit.dev",
"wss://ngit.danconwaydev.com",
"wss://relay.damus.io"
],
```
are you showing the relays / grasp servers you are actually fetching from?
Thanks for fixing the announcement event shape to match nip34 and cleaning out alot of the clone urls that wouldn't work. This is much better. You are still listing 5 grasp servers as relays only. Most of these won't accept your event because you dont list them in the clone or push a valid state event and git data within 20mins. ```
[
"clone",
"https://git.gittr.space/npub1ruxskh0xm6gags4mpc5x50gnag4m9zkyysmprm9f9y63p0rz2t5q0ffu7z/tmptestgittr.git",
"[email protected]:npub1ruxskh0xm6gags4mpc5x50gnag4m9zkyysmprm9f9y63p0rz2t5q0ffu7z/tmptestgittr.git"
],
[
"relays",
"wss://git.shakespeare.diy",
"wss://ngit-relay.nostrver.se",
"wss://git-01.uid.ovh",
"wss://git-02.uid.ovh",
"wss://gitnostr.com",
"wss://relay.ngit.dev",
"wss://ngit.danconwaydev.com",
"wss://relay.damus.io"
],
```
When creating an repo from scratch you try and sign a state event but ommit a commit id under `refs/head/main` which is in an invalid state.
```
"tags": [
[
"d",
"tmptestgittr"
],
[
"refs/heads/main",
""
],
[
"HEAD",
"ref: refs/heads/main"
]
],
```

2026-05-14 08:22:32 CEST

- reply

this is how the gitworkshop repo looks on gittr:
https://blossom.primal.net/216fcd3e168a13fc0a15f744407b498ab7b3b6402f7513a221bcfa17a40c4107.png
and on gitworshop client:
https://haven.danconwaydev.com/31adc239f45b85ba25687d7f530dbb36f5069493dcc827b0e0c7c883660290ba.png
See how the Issue and PR counts are wrong and its showing git data (tip of main) 8 months out of date?
Gittr lists 16 repository relays 7 grasp servers whereas the nip34 announcement event only lists 4 relays, 3 grasp servers and 2 additional git servers:
https://haven.danconwaydev.com/4ce409d478685fc07ac000d7d4a797a486ec6574ae4f96ef3031143bb3de51e0.png
vs
https://haven.danconwaydev.com/e731642a00b4d7abb6673156472ac01e2ba876f1ff29fb858ed29f97ba718668.png
when i click on issues it shows 76 open and 0 closed:
https://haven.danconwaydev.com/ea38c04a36d35b50dfe25956a560f7a521ab42cdfa927115c0f461ca8ec5de52.png
compared to 12 open, 78 resolved and 24 closed on the gitworkshop client:
https://blossom.primal.net/31a7d4961f64f8826b1a326bb32085acdf2a8048624d186c207c54b9b14d2765.png
Gittr still mades malformed nip34 repo announcement events. ie.multiple `clone` / `relays` tags rather than 1 tag with multiple values. it also includes 16 clone urls including non existing ones such as `[email protected]:<npub>/<id>.git`

2026-05-13 22:33:40 CEST

- reply

I can understand how it could feel this way. I think the lack of compatibility with the NIP-34 ecosystem is is holding back users of other git nostr tools from using gittr.

2026-05-13 19:24:08 CEST

- reply

Merged. Zap to your hearts content.

2026-05-06 16:26:52 CEST

- reply

# 6 - I've released a fixed. Can you confirm its fixed?
# 7 I think it would have worked in you used `git clone --mirror`. I suspect it's failing becaue the tag git data wasn't downloaded locally and therefore can't be pushed. There is probably a better flow for migrating a remote repo for a url. I've thought about adding a feature to gitworkshop where it will migrate the Issues/PRs/Comments as well.

2026-05-06 16:21:41 CEST

- reply

Thanks! I've now archived ngit-relay in favor of https://gitworkshop.dev/danconwaydev.com/ngit-grasp which is the most complete and stable implemenation.
I should have updated ngit.dev/grasp and the readme sooner - sorry about that. Issues # 6 and # 7 are really useful reports.
Would you like to try ngit-grasp?

2026-05-05 10:21:50 CEST

- reply

Its probably because the client you are using doesnt support showing the git PR kind.
https://gitworkshop.dev/nevent1qy28wumn8ghj7un9d3shjtnwva5hgtnyv4mqqgrwmpmlfdc8vzjvemlk4z055lccugf3w4tyer4sl4yujt2tva057v49nc6t
The nostr link has relay hints: #nevent1q…nc6t

2026-05-05 10:17:06 CEST

- reply

I decided to interpret this as "until you fix the client that produced the note without the reference" for maxium PoW. So here is the GRASP ssh proxy idea: #nevent1q…s6xr
and here is the client fix PR: #nevent1q…mm3d

2026-05-02 19:41:43 CEST

- reply

I'm not sure if my nostr DMs are getting through, but I'm getting yours. Let's have a call on signal.

2026-05-01 13:31:19 CEST

Idea: Grasp ssh proxy. benefits: simple onboarding, no plugin required, retain most grasp beneifts, trusted-third party but can upgrade to remove this at anytime. I predict @npub180c…h6w6 will hate it and @npub1zxu…cx2y will love it. Here is a draft spec: nevent1qvzqqqqx2gpzpgqgmmc409hm4xsdd74sf68a2uyf9pwel4g9mfdg8l5244t6x4jdqy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwdenkjapwv3jhvtcqyphdsal5kurkpfxvalm238620uvwyych24jv36c06jwf949kwh60xgxuxyz

2026-04-30 22:56:24 CEST

- reply

Yeah, I couldn't find it either. @nprofile…8mc2 had the right approach. "Look into nostr solutions to git"

2026-04-30 22:50:24 CEST

- reply

Thanks for commenting @nprofile…8mc2

2026-04-30 22:02:52 CEST

- reply

Thanks @nprofile…2szn

2026-04-27 12:41:00 CEST

- reply

I think I'm guilty as charged for having a preference for really small text and low contrast. I should do a review to comply with accessability standards relating to size and contrast.

2026-04-27 12:31:26 CEST

- reply

I was that solitary podcast listener that made it to end of the episode; accurately profiled as a nixos user.

2026-04-27 12:02:31 CEST

- reply

Rather than authenticating users, GRASP servers reject pushes that don't match the repository state published to nostr. This state is just a list of the git refs ie. a list of branches, tags, etc and the commit id of their tip. The backend is actually really simple, a standard git server with custom authentication. The core of the protocol fits on one page: https://gitworkshop.dev/danconwaydev.com/relay.ngit.dev/grasp/tree/master/01.md

2026-04-27 11:47:47 CEST

- reply

What are you trying to achieve? eg. publish your own code, create a PR, report a bug/request a feature on an existing repository

2026-04-25 15:55:00 CEST

- reply

I heard you like⭐🌟⭐ so i finally added them:
https://haven.danconwaydev.com/cce7560c4646132d6e2e28f14807271d56d1f8a1d7bce9fa3666692b18cb9b0c.png

2026-04-25 11:14:27 CEST

https://gitworkshop.dev rewrite shipped. Is there a better time to try git nostr? protocols > platforms

2026-04-21 12:57:55 CEST

- reply

Someone need to teach his parents about doas.

2026-04-21 12:41:47 CEST

- reply

GM. I'm working on gitworlshop.dev rewrite currently at https://alpha--gitworkshop.netlify.app

2026-04-16 23:53:53 CEST

- reply

NIP-34. I'm also using a couple of extra primatives. I've been meaning to formalise them into a proposed update to NIP-34.
1. Nip32 labels for apply hashtags after the fact.
2. A nip32 style 'subject' to enable updating the title.
3. CoverNote - a versioned controlled pinned note that appears at the top of the related issue/PR/patch to enable the author or repo maintainer to provide a summary / update for long threads. This sort of plugs the gap of editable issues.

2026-04-16 23:07:48 CEST

Kinga Glyk is incredible. I've not been blown away by music in nearly a decade. https://haven.danconwaydev.com/69d66d86213c4a70a002a7ec7d54d28606c8bb56eaf79aad6494093cbb866a71.mp4
https://www.youtube.com/watch?v=hAcMDUvAcAo

2026-04-16 23:03:30 CEST

- reply

Let's go!!!

2026-04-05 16:28:17 CEST

- reply

Wow. Sorry to hear that. Did you have any backup of the issues / replies?

2026-04-01 12:50:33 CEST

- reply

Netgear nighthawk's are broadcom based so OpenWRT is not an option. FreshTomato is the the best alternative IMO.

2026-03-30 18:53:00 CEST

- reply

Thanks for the report. I'm immanently going to release a complete rewrite with hopefully better remote signer / amber support

2026-03-22 19:43:46 CET

- reply

Good luck. AI has made using NixOS as a daily driver so much easier.

2026-03-18 21:15:10 CET

- reply

It was down intermittently for me earlier today.

2026-03-15 20:05:39 CET

- reply

What's your review process?

2026-03-09 22:41:55 CET

- reply

thanks for the feedback. 1. didnt `ngit init` end by showing your the nostr://<npub>/<relay-hint>/<identifier> clone url and a link to browse it on gitworkshop.dev>? 2. have you installed ngit locally? ngit init has a --repo-relay-only flag for non-public repos. see `ngit --customize` for how to turn it on in your local repo. the ngit skill is really useful. AI is fantatic at using ngit. nevent1qgs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngqyp7mna9m2pev3u9hjakldpsxhsswea5dex9gurh6sdc4dh0exhttgwz2l36
I'd love to get on a call with you to discuss I am can improve it and make it less confusing.

2026-03-09 16:11:28 CET

- reply

I've not seen gitgrasp.com before. is that your work or perhaps @npub180c…h6w6

2026-03-09 15:57:05 CET

- reply

Grasp!

2026-03-08 20:49:14 CET

- reply

Sure, happy to chat. You missed the nostr state event in nips.nostr.com/34 which is the primary way maintainers push. See the grasp spec https://gitworkshop.dev/danconwaydev.com/grasp/tree/master/01.md
This is the most mature implementation: https://gitworkshop.dev/danconwaydev.com/ngit-grasp
Here is the authorization code: https://gitworkshop.dev/[email protected]/ngit-grasp/tree/master/src/git/authorization.rs note that it implements the purgatory PR to the grasp spec

2026-03-08 19:42:36 CET

- reply

Half right. Both clients and servers treat the git state on nostr as the authority.
One grasp implementation (ngit-relay) uses git hooks to prevent pushes of incorrect state. 3 others implement there own http git server rather than git-http-backend.
An ngit client won't download an incorrect state from a listed git server. This makes the trust relationship with git servers identical to that of nostr relays.
grasp servers authorising a new state. Clients like ngit fetch the only the related data from listed servers. If a server has a d if repository git servers have a different state. Grasp servers prevent other use

2026-03-06 23:43:44 CET

- reply

That's not cringe. You acknowledged their humanity.

2026-03-06 21:01:46 CET

- reply

Simple and elegant

2026-03-06 15:50:19 CET

Released ngit v2.3.0 which now supports issues, comments. Add the skill and ask ai to create a git nostr repo and explore the features.
npx -y skills add https://relay.ngit.dev/npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr/ngit.git

2026-03-03 14:23:13 CET

- reply