DanConwayDev

If you are interested, here are my thoughts about the best way to use blossom for git:
It's inefficient to create one blob of the whole git repo each time a branch tip changes eg. using `git bundle`. This forces users who have already cloned the repo to download the whole thing again to pull just the latest commit. Imo the optimum way of doing it would be to group commits based on powers of 2 and create blobs of each group using `git packs`. I made a start here #nevent1q…qr9d but didn't take it any futher because grasp is a much better idea.

2025-07-07 13:46:48 GMT

- reply

I thought about using blossom for git. I ended up creating grasp, which has many more advantages https://ngit.dev/grasp .

2025-07-07 13:00:32 GMT

- reply

O nice. I didn't think of this and it esthetically works well. Its simple and it looks like a claw grabbing and git nodes. The problem is that its a claw from a crane game, which is designed to fail 70-90% of the time. We can't really have a logo associated with failure.
My first thought with grasp was reaching to grab a baton in a relay race but I'm not sure its possible to represent that in a logo.

2025-07-07 12:41:37 GMT

- reply

@nprofile…pt5w Can Amethyst use NIP-22 for git issue / patch replies rather than the deprecated git reply kind`1622`?

2025-07-07 12:36:34 GMT

- reply

Do you want to link it to a patch set (tracked in patches or nostr PR event) or to a branch (tracked in git state)?

2025-07-04 19:21:56 GMT

- reply

Raw milk?

2025-07-04 18:31:47 GMT

- reply

Thanks very much..I'm struggling to articulate it in a way that isn't confusing. https://ngit.dev/grasp

2025-07-04 14:28:04 GMT

- reply

Do you have any ideas for a grasp logo? https://gitworkshop.dev/danconwaydev.com/grasp

2025-07-04 14:08:52 GMT

- reply

Anything is a sphere if you make it massive enough

2025-07-04 10:13:01 GMT

- reply

Love it. It would be nice to have some more interactive desktop signer tools. I guess there is no so much demand because of the browser extension model and a smaller set of native desktop nostr apps.

2025-07-03 20:16:39 GMT

- reply

Here is a new one for you: grasps https://gitworkshop.dev/danconwaydev.com/grasp

2025-07-03 13:03:12 GMT

- reply

The git republic ui is looking great BTW

2025-07-03 13:02:50 GMT

- reply

Patches are part of the git protocol

2025-07-02 10:31:43 GMT

- reply

https://github.com/nostr-protocol/nips/pull/1336

2025-06-27 07:57:53 GMT

- reply

@nprofile…fcsk is building something with blossom #nevent1q…33hx

2025-06-26 13:01:38 GMT

- reply

Certainly

2025-06-25 08:53:20 GMT

- reply

AI wants to crawl everything

2025-06-25 08:37:46 GMT

- reply

I'm working on it. See gitworkshop.dev

2025-06-25 07:49:14 GMT

Heavy rate limiting of unauth github requests incoming. KYC every request or face inconvenience. https://github.blog/changelog/2025-05-08-updated-rate-limits-for-unauthenticated-requests/

2025-06-24 11:26:33 GMT

- reply

The intent of `git repository announcement` kind `30617` events was to claim ownership of a repository and indicate that you are accepting Issues and PRs via nostr. nip34 reads:
> \[git repositories\] existence can be announced using Nostr events, as well as their willingness to receive patches, bug reports and comments in general
I expected that announcement would either reflect this or be intentional affinity scams by bad actors which could be weeded out as spam.
I now think the intent is not very intuitive as most repositories on github are private forks for creating PRs or hosted a patch just for that user. Some users created an `announcement` event as they tried to figure out how to do a PR.
Some users wanted to send Patches or Issues to a respository not using #GitViaNostr as a way to encourage them to use it and created an `announcement` event for this.
Trying to enforce a non-intuitive original intention on a permissionless protocol like nostr is like pissing in the wind.
Maybe we should add some flags to the announcement event to enable announcing someone else's repository? Github has the concept of pinned repositories which seems relivant here.

2025-06-23 13:44:56 GMT

- reply

What good is storing my reply if the rest of the thread is lost?

2025-06-23 13:44:10 GMT

- reply

What good is storing a reaction ifIthe original event is lost?

2025-06-23 13:43:28 GMT

Wouldn't it be great if Haven synced the context around our notes from other relays? @nprofile…6u4e

2025-06-22 20:16:19 GMT

- reply

WW2 is an examppe where these questions are answerable?

2025-06-22 20:02:23 GMT

- reply

What about when Hitler invaded Poland?

2025-06-22 11:05:51 GMT

- reply

Its a pleasure

2025-06-20 23:28:21 GMT

- reply

This is so awesome

2025-06-13 12:10:08 GMT

- reply

I added some functionality related to repository deletion:
- show red banner and notices when on a repository page that has been deleted
- add delete button if there are less than 5 issues or PRs
- hide deleted repositories form search results and profile page

2025-06-12 20:24:45 GMT

- reply

Its been on my list to look into @nprofile…xfvf's nostr package management project.

2025-06-10 17:57:43 GMT

- reply

Ngit-relay has an optional 'proactive sync' that checks every 45m whether the git repo matches the state event and if not, tries to catch up by syncing with the other git servers.
The intention is that it would also sync nostr events from other listed relays too but that isn't built yet.
So if you always pushed to the nostr remote, which creates and sends the nostr state event first, and so long as at least 1 git server got your update, the others should catch up.

2025-06-10 13:15:01 GMT

- reply

If you set up your repo on nostr with `ngit init` and selected 'relay.ngit.dev' then the repo would get pushed there. I'd expect people to clone using the nostr url and they could still clone and raise a PR after you deleted on github.

2025-06-10 10:45:34 GMT

- reply

If you push using the nostr remote, it will publish your state to nostr. In the future there might be git nostr tools that find the data related to that state from other sources when the git server link(s) listed in the announcement go down or are deleted. On a relate front, check out https://ngit.dev/relay soon to be renamed 'grasp'. Think blossom but for git. The same 'finding lost assets when the link breaks' ideas apply.

2025-06-10 09:52:06 GMT

- reply

There isn't a cammnd for this. You can use delete.nostr.com . gitworkshop can delete other things such as patches, issues, replies, etc but I wasn't happy I quite had the right flow for repository announcements, which wouldn't recreate the opportunity for a repeat of the 'left-pad' incident.

2025-06-10 04:40:00 GMT

- reply

Thanks. What gave you the 'works on my machine' vibes or do you mean specifically getting it to work with jj?

2025-06-05 12:12:47 GMT

https://gitnostr.com/072675635c6156fd1ad84e5a1808fdbefdb188b768e185f97133bd800ff2cce2.png
https://ngit.dev/relay introducing ngit-relay, a Nostr-permissioned Git / Relay / Blossom Service Protocol. A complete, self-hostable data solution for Nostr Git repositories.

2025-05-14 15:17:37 GMT

error handling in javascript sucks

2025-05-14 15:06:42 GMT

- reply

Keen to try this out. I'm not sure what git backend you are using but could you get it to set git config `uploadpack.allowTipSHA1InWant` and `uploadpack.allowUnreachable` to true on the repo to enable cloning with ngit via the nostr url?
Also add .git to the end of the git sever in the nip34 announcement, as the git server doesnt forward it?

2025-05-04 21:21:31 GMT

- reply

Its also a lot more convienent to sign and verify messages as every interaction has to be signed.

2025-05-04 21:20:10 GMT

- reply

Say a vulnerability was merged 1 year ago and it was ACK'd by someone who has since had their PGP compromised. How would you know the ACK was signed ahead of the merge rather than after the key compromise?

2025-05-04 21:08:00 GMT

- reply

I like radicle and I had some discussions with them about this. Unfortunately they use a different cryptographic curve which means you can't have a key which is provably a radicle key and a nostr key.
Ultimately, I think nostr is the better solution because it has its own ecosystem and doesn't try to create one from scratch.
#nevent1q…rrpd

2025-05-04 20:53:56 GMT

- reply

"I have to trust that the interface telling me that he has approved the PR is being truthful when I merge it. " https://github.com/QubesOS/qubes-issues/issues/3958#issue-329274197
They'd love signed OTS'd ACKs:
#nevent1q…p2lk

2025-05-04 20:36:00 GMT

- reply

TLDR; We can bring back git's decentralised roots with nostr. Nip34, ngit and gitworkshop.dev takes what's great about the email and GitHub models and applies it to nostr. Friction remains for on boarding new repositories. To solve this we need to strip back and decentralise the git server function and enable CI /CD via a DVM style marketplace.
#naddr1qq…s8x4

2025-05-01 13:13:01 GMT

- reply

For me the concept is more useful than the spec. See #naddr1qq…sr3t

2025-05-01 10:23:36 GMT

- reply

The bearer token nature of ecash simplifies things. Users can push a payment at the size of their choosing to a specific DVM with non interactivity with that provider. The provider can send change back to the user again with no interactivity.

2025-05-01 09:49:00 GMT

- reply

Thanks. I'd love your feedback - good and bad.

2025-05-01 09:30:15 GMT

- reply

Thanks

2025-05-01 08:42:47 GMT

- reply

There is a signal and a simplex chat. I'll DM you the links.

2025-04-30 18:31:58 GMT

- reply

Thanks for your encouragement

2025-04-29 09:57:29 GMT

- reply

OpenTimestamped ACKs are native and easy when using #GitViaNostr
#nevent1q…4jdf
#nevent1q…qz6x

2025-04-25 08:47:52 GMT

- reply

If you use someone else's relay you don't need to expose your IP address to your users.

2025-04-23 14:31:01 GMT

- reply

In git there is a command for everything!

2025-04-23 07:35:53 GMT

- reply

Thanks. Let me know your experience of ngit the CLI #gitvianostr

2025-04-23 07:01:16 GMT

- reply

Thanks. I've reintroduced it.

2025-04-23 06:36:32 GMT

- reply

The quick search should be in the top right. Didn't this meet your needs?https://m.primal.net/QaIC.png

2025-04-18 21:49:09 GMT

- reply

Interesting pan choice

2025-04-17 08:10:39 GMT

- reply

I've thought some more about this. I think its better for project management style features like kanban to be done in other clients. [gitworkshop.dev](http://gitworkshop.dev) should be able to detect that an issue / PR is referenced by other things (eg tags, boards, epics, etc) and link out to other clients for that.

2025-04-16 13:15:41 GMT

- reply

Is that because you are vibe coding?

2025-04-13 08:31:14 GMT

- reply

Small commits with decent descriptions FTW!

2025-04-10 11:40:59 GMT

- reply

Checkout gitworkshop.dev

2025-04-05 18:30:39 GMT

- reply

https://image.nostr.build/8ca4093ce2446b0dd18caa39db4214d8ef097b92d1638730f4ad2c4da4b14548.gif

2025-04-05 09:05:37 GMT

- reply

We do get reminders like this from time to time just his important a decentralised alternative is.

2025-04-03 11:36:45 GMT

- reply

I've added ngit builds for all OSes versions available from github runners:
ubuntu latest, 24.04, 22.04, 20.02, 24.04-arm, 22.04-arm
MacOS latest, 15, 14, 13
Windows latest, 2022, 2019
see http://gitworkshop.dev/ngit under 'download compiled binaries'

2025-04-01 17:53:29 GMT

- reply

Throttle it so it doesn't dominate my feed. I had to stop following it.

2025-03-31 14:24:22 GMT

- reply

No solutions. Only trade offs.

2025-03-28 21:20:06 GMT

- reply

Let us proceed together apace

2025-03-27 10:09:08 GMT

- reply

1) because it was never standardsised in the protocol so apps did their own thing.
2) in an attempt to make creating a simple client easier so it doesn't need so much custom rendering.

2025-03-27 09:33:23 GMT

- reply

@npub1jlr…ynqn's attempted at defining this in this nip27 PR: https://github.com/nostr-protocol/nips/pull/1800

2025-03-25 16:12:20 GMT

- reply

@npub1c03…yrnw was also asking for a delete button so I have one in the menu EventWrapper menu (next to the share and reply buttons under more).
Closing as resolved.

2025-03-25 14:34:17 GMT

Why don't deletion requests include nip22 thread root tags? It would them eaiser to find. #asknostr #dev #nips

2025-03-23 12:39:12 GMT

- reply

Wouldn't it make more sense to zap a commit? That's an individuals contribution to the repo. How would the zap get split if you zapped a file? Number of line changes to the file would be problematic. Eg. 80% to the person who applied the new linting rules

2025-03-23 12:30:26 GMT

- reply

Who is your rust dev?

2025-03-20 15:39:24 GMT

- reply

I'm super keen for a nostr native git server solution which I can just push to from ngit without any other auth or setup. That I'd definitely pay for.

2025-03-19 09:46:21 GMT

- reply

Isn't it better to calculate it using the token events rather than the history events? There will be less data to fetch and it is less likely to be effected by a client used in the past that created bad data.

2025-03-18 19:12:40 GMT

- reply

Have you looked at git.fiatjaf.com/song ? It seems an ideal fit for your usecase.
I briefly started a simpler project to put https://git-scm.com/docs/git-http-backend behind a reverse proxy and only let through push requests when the match the state in a nostr event but I've been distracted by other stuff.

2025-03-12 07:52:19 GMT

- reply

Nice!

2025-02-26 21:56:44 GMT

- reply

I find paid relay service offerings unclear. I really want a fast and reliable outbox relay that will store my notes and the non-spammy context. Also with private DM support. Any advice?

2025-02-26 18:05:50 GMT

- reply

This looks excellent. How can I try it out? I don't think it's in v0.2.11

2025-02-26 18:04:36 GMT

- reply

#gitvianostr is getting integrated into all sorts of clients. Well done @nprofile…dswr!
#nevent1q…cfje

2025-02-25 16:01:37 GMT

- reply

This is implemented in vnext. So much for a quick win! Issues and PRs and events responding to them (status, replies, etch) can be deleted with a tool like delete.nostr.com and gitworkshop will honor the deletion.
If the event is a PR or an Issue and a user has already cached it, it will move into a 'marked as deleted' status. replies, etc will be removed.
If a reply is deleted which has other replies to it, these replies will be shown under the top level thread with a 'missing parent note' heading.
a separate job queue processes each deletion event which trawls through local db entries to remove cached counts of replies and update status accordingly.
cc @npub1elt…cume

2025-02-23 13:50:01 GMT

- reply

You and me both

2025-02-21 14:13:41 GMT

- reply

Embrace the chaos!

2025-02-19 23:21:22 GMT

- reply

In gitworkshop we store a range of relay hurisrics for pubkeys, repos, issues and PRs. We use these for filter specific relay selection.

2025-02-19 09:56:55 GMT

- reply

Looking forward to checking this out when I'm at my desk

2025-02-19 09:55:49 GMT

- reply

GM. Another #gitvianostr client just dropped. Congrats @nprofile…atmf
#nevent1q…8l40

2025-02-17 22:28:29 GMT

- reply

#nevent1q…aalf

2025-02-17 22:26:33 GMT

- reply

#nevent1q…aalf

2025-02-17 22:25:23 GMT

- reply

Thanks for expressing interest. Here is a link to a GitViaNostr simplex group. I'll try and arrange a Signal call later this week to outline the categories of GitViaNostr projects and explore opportunities for collaboration. Dont worry if you can't make the call, we can follow up afterwards.
https://simplex.chat/contact#/?v=2-5&smp=smp%3A%2F%2F1OwYGt-yqOfe2IyVHhxz3ohqo3aCCMjtB-8wn4X_aoY%3D%40smp11.simplex.im%2Fh4qUr9Yj8C9y59CoalGVQDQWpEPzESmW%23%2F%3Fv%3D1-2%26dh%3DMCowBQYDK2VuAyEAltJo8QZNzjq_6Sz_zjMqY3Sqb9Jg2mSiDIAvSIUg9kA%253D%26srv%3D6ioorbm6i3yxmuoezrhjk6f6qgkc4syabh7m3so74xunb5nzr4pwgfqd.onion&data=%7B%22type%22%3A%22group%22%2C%22groupLinkId%22%3A%223WlWt7YVg49I_AcPMLgQFQ%3D%3D%22%7D

2025-02-17 22:25:13 GMT

- reply

2025-02-17 13:03:28 GMT

- reply

I tested multi-account nip07 functionality. Right now this works in the same way NoStrudel does. Its intuitive if you switch accounts in the signing extension and the app at the same time, but it otherwise gets confusing as account switching with the app and within the extension happen independently. cc @npub1ye5…knpr.
To improve this, the app could ask for the pubkey on page load (or refresh) when a nip07 extension user is logged in. Then it could switch the user to the active pubkey.
This would be slightly annoying for unusual users like me who likes to manually approve each signing request but its probably worth the trade off.
This wouldn't pick up on changes if the nip07 signer account changed whist the app is already loaded. Periodic polling of the signer pubkey could address this but this would be even more annoying for users who want to manually approve.

2025-02-16 20:02:59 GMT

- reply

Could you top up for more than 1 month at a time? The selection box is grayed out. Maybe they have channel liquidy issues and are limiting payment sizes.

2025-02-16 13:22:44 GMT

- reply

Yes, sorry I was being pedantic. It's cool isn't it?

2025-02-15 19:27:05 GMT

- reply

So maybe a few third parties involved.

2025-02-15 11:07:57 GMT

- reply

Did you setup a lightning channel with them?

2025-02-15 08:41:05 GMT

- reply

Will do!

2025-02-15 08:30:41 GMT

- reply

When a PR is merged in ngit, it could also send an resolved status for issues referenced like this in comments. It would need to download all comments that tag the PR to detect this.

2025-02-15 00:58:24 GMT

- reply

Thanks again Ben. I indeed added apple-sauce signing but havn't gotten to the nip46 or Amber clipboard signing just yet. There is an issue open for it. Your welcome to have a go? I can provide some guidance as needed.
#note1vpd…s2p6

2025-02-15 00:55:45 GMT

- reply

I've rewritten gitworkshop and the pre-release is viewable at https://vnext.gitworkshop.dev
I'm really keen on working with you to add kanban support to gitworkshop and more broadly ensure good integration with nip34.