DanConwayDev

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

Public Key

npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr

NIP-05 Address

danconwaydev.com

Profile Code

nprofile1qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5use7d3

Publishing to

nostr-pub.wellorder.net

Author Public Key

npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr

Show more details

Last Notes

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-13 19:24:08 CEST

- reply

Merged. Zap to your hearts content.

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

See also gitui

2026-02-27 23:48:15 CET

- reply

Nixos works great with agents because all the config is declative and version controlled. I run it on all my machines, laptops, home servers, vpses dedicated cloud servers, even my router.

2026-02-27 22:54:09 CET

- reply

Yubikey?

2026-02-27 22:53:04 CET

- reply

Use doas with limited rights so it can diagnose but not do damage without consent. A yubikey is real helpful so it can run commands using a swperate sshkey with more permission, but only if I physical touch the yubikey to approve it.

2026-02-27 19:02:27 CET

- reply

I'd like to catpure the git server responses (what git normally prints) and only show a summary of that. it currently shows what git normally show for but for each git server the maintainer lists.

2026-02-27 19:00:18 CET

- reply

If you haven't upgraded recently do that (ngit v2.2.3 is current latest) as a lot of the verbose cli output has now been hidden by default.

2026-02-27 18:54:12 CET

- reply

I've been testing all day and I'm getting a lot of inconsistencies. I think it is a combination of things. relays being flaky with remote signing events, a lack of full compliance with nip46 in rust-nostr and a resulting lack of resilience with Amber. i found more consistency with `nak bunker` running on the same machine. Also with opther nip46 client implementations eg nostrify one used in https://mew.ditto.pub

2026-02-27 18:50:16 CET

- reply

ngit v2.2.3 now makes it easier to customise the signer relays via `ngit account login`. also it now has hopefully better defaults.

2026-02-21 01:00:23 CET

- reply

I should also tease a grasp implementation ive been working on that live at relay.ngit.dev.

2026-02-21 00:57:49 CET

- reply

https://gitworkshop.dev/danconwaydev.com/ngit/tree/main/CHANGELOG.md

2026-02-21 00:57:13 CET

ngit v2.2.0 released today including AI-friendly commands, simplifed cli output and other goodies.
`curl -Ls https://ngit.dev/install.sh | bash`

2026-02-16 16:28:18 CET

- reply

https://nips.nostr.com/34#repository-state-announcements

2026-02-16 09:21:31 CET

- reply

The repository state is stored in the repository state event. The maintainer publishes a new /updated state event and pushes the associated new git data to the grasp servers. The ngit git plugin is convenient for this all behind a `nostr://` remote. Nak also has support (run `nak git --help` and some other tools handle this themselves though eg Shakespeare.

2026-02-15 11:27:51 CET

- reply

What do you mean by 'where the clones are'? The clone URLs are listed in the announcement event. The actual protocol is the best place to look: https://gitworkshop.dev/npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr/grasp

2026-02-14 22:51:16 CET

- reply

Yes, the https://gitworkshop.dev/fiatjaf.com/git-natural-api approach is best way for a lot of scenarios where you want to display repo data.

2026-02-12 13:07:41 CET

GLM5 is my new favourite model

2026-02-11 21:13:50 CET

- reply

Another good roundup. I liked how you built on themes and tried to keep things moving and below the 15min mark.

2026-02-11 15:53:13 CET

- reply

This is interesting. Does the comment still appear for you @nprofile…lej9 when you are logged in?

2026-02-10 22:25:08 CET

- reply

Try pipepipe

2026-02-10 21:46:16 CET

- reply

Nice round up. I like the format. It's nice to see what's peaking your interest.

2026-02-10 13:17:43 CET

- reply

Where has git started using rust?

2026-02-09 18:01:04 CET

- reply

Why lock your source control and collaboration flow to a single provider when you can use an open network with built in redundancy?

2026-02-08 00:01:08 CET

- reply

FYI I plan to create a optional extension of the GRASP protocol that supporting relay based moderation that respects the wishes of maintainers. Examples include: 1) deletion - they can delete PRs, issues, comments etc. 2) apply WoT rules for creating issues, PRs or even comments. 3) optional pre-approval proeccess for PRs or Issues.

2026-02-07 23:52:15 CET

- reply

Interesting! It feels like there is such an opportunity for #GitViaNostr with Microsoft neglecting github so much. If they were on the ball, they would have introduced a feature like this months ago.

2026-01-27 11:45:15 CET

- reply

Yes your right. The output of those different phases should be consolidated so you just see the status per relay / git / grasp server.

2026-01-22 15:27:51 CET

I totally agree. Unless you need dowload every file in a repository for some reason this is much better. It uses a fraction of the bandwidth and is really quick.
#nevent1q…asgg

2026-01-20 20:36:39 CET

- reply

I thought about doing this to make @nprofile…cd2e's favourite and @nprofile…xuyp 's least favourite client at the same time

2026-01-20 12:35:49 CET

Fantastic to see this coming together
#nevent1q…lgfa

2026-01-17 09:51:56 CET

- reply

So your needs are: 1) basic Issue / PR flow with good review tooling 2) moderation tools 3) CI tooling? Have I missed anything?

2026-01-17 09:23:50 CET

- reply

With ngit, nostr events are synced to a db within the .git directory. Also GRASP-05 enables archive servers that mirror repositories the operstor cares about. This enables repository data to always be publically available even if the services the maintainers choose go down.

2026-01-16 22:37:12 CET

- reply

As @nprofile…3zgd said you can use any git server you want or host it yourself. Grasp is designed to enable users and projects to either self host, use grasp services offered by individuals or teams in their network or use public free or paid servers. The idea is thst projects use multiple grasp services at the same time whic sync up to provides reduncancy. Its also really simple for maintainers to switch service providers by updating a single event.

2026-01-16 22:23:15 CET

- reply

quote from https://radicle.xyz/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-01-16 22:22:06 CET

- reply

last time i checked in on the project it mainly worked through 'seed' nodes which are analogus to relays because p2p was proving so unreliable. I'm not sure how much more decentralised it is in reality.

2026-01-16 22:18:29 CET

- reply

Hi @npub185h…wrdp, I'm the creator of gitworkshop, gnit and grasp. A combination of relay an client tools can provide the provide this sort of moderation and control for projects that desire it, but the maturity of git nostr isn't really there yet. Whilst the majority of a project community would likely use these tools that support this moderation, the conversation can spill over into the wider nostr ecosystem and clients built / used that don't enforce this moderation. This is the trade-off using an open protocol thats easy to build on.

2026-01-06 22:23:42 CET

- reply

How's the gnostr stuff going?

2025-12-27 13:51:37 CET

- reply

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

2025-12-27 13:05:10 CET

- reply

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.

2025-12-27 12:57:53 CET

- reply

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.

2025-12-27 12:54:59 CET

- reply

@nprofile…ptz7 I considered using blossom, in fact I even wrote some code. #nevent1q…x4r0 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.

2025-12-23 16:07:57 CET

- reply

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?

2025-12-23 14:53:53 CET

- reply

I'm not seeing that comment.

2025-12-23 11:50:46 CET

- reply

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

2025-12-22 22:49:46 CET

- reply

How was the process?

2025-12-22 22:49:06 CET

Let every client be a git nostr client
#nevent1q…s9j2

2025-12-22 22:01:15 CET

- reply

ask and you shall receive
#nevent1q…ryvq

2025-12-21 10:16:39 CET

- reply

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.

2025-12-19 17:51:32 CET

- reply

Some features, such as card payment authorisation, aren't available through the web.

2025-12-19 15:49:11 CET

- reply

Gitworksho.dev is good for managing the issues but you can also create the issues straight from your app. Many clients support notifications for the discussion thread.

2025-12-18 22:08:33 CET

- reply

I needed to hear that. Thanks.

2025-12-18 20:30:02 CET

- reply

Definitely. We could iterate really quickly with a combination of reports (1984), WoT based metrics, relay based filtering and client side mantainer and user tools.

2025-12-18 17:59:30 CET

- reply

This is a good thought. Right now I feel we are too experimental and it would be counter productive to have a large influx of users with viral marketing.

2025-12-17 17:27:20 CET

- reply

@nprofile…cy97 we should have a call sometime to discuss compatible. Would you be up for that? I reached out the other day on telegram.

2025-12-17 17:16:53 CET

- reply

Are you sending a nostr DM from a system account for every one of these notifications?This feels a like an anti-pattern. Wouldn't it be better to show them as notifications in the gittr UI. Many clients show git related content in there notifications normally and as we grow #GitViaNostr maybe more will.

2025-12-17 17:09:19 CET

- reply

No not yet. https://gitworkshop.dev/notifications is a good place to see notifications for #gitvianostr

2025-12-15 21:13:06 CET

- reply

Yes, I'll add it with a left-pad protection scheme.

2025-12-09 15:25:18 CET

- reply

I cannot replicate this on 145.0. vnext.gitworkshop.dev is now at the exact same state as gitworkshop.dev. does it now have the same behaviour? does a fresh profile fix it?

2025-12-09 10:57:49 CET

- reply

I think your missing the insight into fucundious nature of ground of our being. These life-like properties are emergent in 146 bytes of C: `#include<stdio.h>
#include<stdlib.h>
int main(int c,char**v){int i,j;for(i=1;i<c;i++)for(j=1;j<c-i;j++)if(atoi(v[j])>atoi(v[j+1])){char*t=v[j];v[j]=v[j+1];v[j+1]=t;}for(i=1;i<c;i++)printf("%s%c",v[i],i==c-1?'\n':' ');}`

2025-12-09 10:18:51 CET

Michael Levin's team applied 'theory of life' analysis to a sorting algorithm and found emergent life‑like behaviors not explicit in the code — including delayed gratification, clustering, robustness, and repair. Fascinating.
https://www.youtube.com/watch?v=Qp0rCU49lMs

2025-12-09 00:13:46 CET

- reply

I made it a PWA a month or so ago, clearly not as successfully as I thought.

2025-12-09 00:12:23 CET

- reply

So you're getting this too?

2025-12-09 00:11:52 CET

- reply

Does this happen I'm a fresh profile? I'll try it on this version but I suspect there is something else being cached somehow that's causing this issue.

2025-12-08 22:06:19 CET

- reply

I can't replicate this. I also tried rolling back and forwards with various with a dev preview and couldn't replicate any issues. What Firefox build are you using? I've tried librewolf and 145.0.2. Can you replicate it on gitworkshop.dev now even after you unregister the old service worker? Does it also happen on vnext.gitworkshop.dev?

2025-12-08 19:17:01 CET

- reply

Thanks. I've actually justed picked this message up now (i somehow misted your note from 3 days ago) and I'm afk. I reproduced it in chrome based on the troublesome build I mentioned. I'll try and reproduce when I can get back to the keyboard.

2025-12-08 19:00:56 CET

- reply

#nevent1q…xcdk

2025-12-08 18:49:45 CET

- reply

@nprofile…6akr thanks for the report. I thought this white page issue was related to a tempory PWA corruption I introduced for users who visited the page during a windows of a few hours when I initially introduced it. I can see now this is happened on persistently on Firefox. I'll look I to this in a few hours.

2025-12-05 23:43:16 CET

- reply

For now you can just ask in the chat box to commit your changes and the AI will do it for you. Then you can use the 'Push to Nostr' button.

2025-11-29 18:24:47 CET

- reply

For now if you want you check the network tab of developer tools and filter for websockets to see the request and events that come back. State event is kind 30618

2025-11-29 18:23:11 CET

- reply

This means it can't find the state event on the relays specified in the announcement event. Clearly this warning should specify that and yrll you which relays it checked and either it failed to connect, got rate limited or didn't have the event. I'll make this better