DanConwayDev

freedom tech developer and creator of ngit, https://gitworkshop.dev and https://metadata.nostr.com

Public Key

npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr

NIP-05 Address

Profile Code

nprofile1qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngpp4mhxue69uhkummn9ekx7mqpz4mhxue69uhhyetvv9ujumn0wd68ytnwv46qz9nhwden5te0wfjkccte9ehx7um5wghxyctwvsq3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7vqsxts

Publishing to

Author Public Key

npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr

Show more details

Last Notes

2026-09-09 03:42:08 CEST

- reply

Thanks. It feels like a real milestone. A lot of hardwork and late nights.

2026-09-09 03:41:30 CEST

- reply

Thanks. Let me know what you think of it

2026-09-09 02:34:43 CEST

https://blossom.ditto.pub/a1db480cb5ca201cf5c3b7d22dee9d7cfbfde3d284fd39e70289a4b4c28a89b1.png
🎓 ngit v3 and GitWorkshop v4 launch! The biggest release yet brings CI, private repositories, forge-free software releases and much more. Grasp is the powerhouse behind ngit. The launch also includes ngit-grasp v3, the new ngit-ci 0.1 and an entirely new docs site. https://ngit.dev/v3

2026-09-05 22:47:28 CEST

- reply

Can you use your network to get their contact details?

2026-09-01 17:29:39 CEST

- reply

Did you sync it with nostr git sync? Did you make it with your main npub? I only see flotilla and a nostrlib fork as nostr git repositories for @nprofile…psy5

2026-09-01 11:13:17 CEST

- reply

When grasp?

2026-08-28 10:41:17 CEST

- reply

Yes

2026-08-14 13:13:51 CEST

- reply

This looks great. I'm interested to see where this goes.

2026-08-05 12:03:52 CEST

- reply

Morning!

2026-08-04 18:14:56 CEST

- reply

Amazing! We plan to introduce support for subpath as part of private grasp repos.

2026-08-04 18:11:52 CEST

- reply

Not right now but soon. But we have a draft and some work towards implementing it.

2026-08-02 22:01:06 CEST

- reply

Welcome back!

2026-07-30 16:31:16 CEST

- reply

Its the right quest!

2026-07-30 15:25:26 CEST

- reply

I listened to this last night and it was fantastic! @npub19w6…syzj, I'm excited about nix-nostr. FYI I just got buzz-desktop working on nixos: https://github.com/block/buzz/pull/3734

2026-07-29 09:06:31 CEST

- reply

I love nix. I think we could use it for git nostr CI. http://gitworkshop.dev/npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr/ngit-ci/tree/nix-idea/docs/nix-workflow-path-proposal.md

2026-07-28 16:00:41 CEST

- reply

He did and its merged!

2026-07-26 15:22:56 CEST

- reply

Take a look at #naddr1qq…w05r

2026-07-25 12:00:16 CEST

- reply

Not with #nevent1q…pcvv

2026-07-25 11:59:44 CEST

- reply

Here is a draft spec. #nevent1q…pcvv https://gitworkshop.dev/nevent1qvzqqqqx2gpzpgqgmmc409hm4xsdd74sf68a2uyf9pwel4g9mfdg8l5244t6x4jdqy88wumn8ghj7mn0wvhxcmmv9uq3vamnwvaz7tmjv4kxz7fwv35hgar09ec82c30qqsr79zwkfckr85cgyec0hz5u3ch20mqfc3l9ahkwe2df9drjkat8tqvdq9wh

2026-07-23 05:31:29 CEST

- reply

Have you tried on gitworkshop?

2026-07-22 21:25:02 CEST

- reply

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.

2026-07-22 20:30:28 CEST

- reply

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

2026-07-22 20:23:57 CEST

- reply

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:47:53 CEST

- reply

You may actually find that a git repository can help you manage and version control materials and content but atm I'm focusing on on-boarding software projects.

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:18:16 CEST

- reply

I'm enjoying the irony that you are complaining that nostr isn't decentralised enough via the primal caching service

2026-07-22 17:15:24 CEST

- reply

Here is a quote from https://radicle.dev/guides/seeder
"While a peer-to-peer network without seed nodes is feasible, it is impractical. This is because regular “user” nodes go online and offline all the time, so finding a user from which to download a certain piece of content can be challenging, or even impossible if all users with that content are offline.
Therefore, a healthy peer-to-peer network necessitates at least some highly available nodes that participate in the network like regular peers, but seldom go offline. These are called seed nodes."

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:40:06 CEST

- reply

#nevent1q…fxxa

2026-07-22 16:38:22 CEST

- reply

Thanks, I'll tell me wife someone of no small renound on the internet called me cool. Then I'll tell my kind someone called my skibadi rizz no caps.

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:20:35 CEST

- reply

thanks to @npub1ye5…knpr @npub1gvv…xchs @npub1ven…ddfh for contributions

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:45:50 CEST

- reply

I've thought about supporting private repos on git nostr. Basically a GRASP endpoint per org where the relay requires NIP-42 auth to read based on a org wide whitelist. Then the grasp git endpoints get accessed via ssh, with ssh pubkey published by the whitelisted user in a nostr event. This way the entire repo can easily transition to being public. Have you thought about how to publish more widely than just local or a private network?

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 15:16:32 CEST

- reply

Imo we wouldn't deserve it. Most nostr projects aren't even using it yet. I think with GRASP we now have the right approach but we have a way to go: CI, stability, moderation tools, etc.

2026-06-22 14:51:42 CEST

Brits think American service culture is ungreatful and low trust
https://blossom.primal.net/0ea91f1d23b0fde1a211e7812112df5d83df218494fe5f526c8c7f855b895f1c.mp4
https://www.youtube.com/watch?v=ytv3467E4JY&t=6206s

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-06 18:09:52 CEST

- reply

How did you lose it?

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 14:10:04 CEST

- reply

i *think* nostrhub.io only uses the first listed server so it makes sense that it doesn't work for your repo when git.shakespeare.diy is down.

2026-05-22 14:08:38 CEST

- reply

hrm🤔 I've been getting CORS and 502 errors git.shakespeare.diy but I've had no problems with relay.ngit.dev and gitnostr.com (the two that i run). Your screenshot showed relay.ngit.dev reachable but maybe just slow? I wonder if its geolocation related? I need some better montoring. @npub1zaf…26k5 and I have discussed this. I'm thinking about using a NIP-66 variant that probes grasp functionality too.

2026-05-22 09:31:51 CEST

- reply

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

2026-05-22 00:12:26 CEST

- reply

There are the two people I see pressing into these ideas the most

2026-05-22 00:10:58 CEST

- reply

I also think @npub1q3s…d26p might invent fire

2026-05-22 00:05:41 CEST

- reply

Its not Shakespeare or Ditto or Nostr Station or NostrOS. But its users expressing there creativity with other. creating their own experiences. UI and UX totally curated by the user.

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-07 17:40:57 CEST

- reply

Point it at @nprofile…uavg and ask it to put a positive spin on it.

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"