Nostr Web Client

I think it is an abandoned POC. As I understand it, here are the active git on nostr projects: ngit, gitworkshop.dev, gitstr, patch34, gnostr and GitNestr.

If you hear about any more, let about them.

Replying to

Yonle

in case if you wonder why the heck ngit did not do well with bostr,

well. it asks for profile, but newer than the specified timestamp.

I don't understand. Are you having an issue with ngit?

Replying to

thanks, I drew heavily from your left border and 'show all' approach to threading. its what makes amethyst my go-to android client.

Interesting that primal changed the root to your first reply. This currently wont appear in gitworkshop.dev as it only queries for messages that tag the issue as root. I'll have to update that.

Replying to

I really like your up arrow to fold replies.

thanks, I drew heavily from your left border and 'show all' approach to threading. its what makes amethyst my go-to android client.

Replying to

Reply test from Amethyst.

Looks good

Replying to

It's awesome! I am about to release the Git integration in Amethyst. Now I can see a notification when a new patch is submitted. :)

nostr:nevent1qqszt4w38p6nzqmdcesqejxztfp6njhkrqzu0uqnhjlkalpfafku69sppemhxue69uhkummn9ekx7mp0qgs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngrqsqqqqqp6ca36p

Do you have a view on this?

I'm using kind 1 events for replies in defiance of the draft nip34 some users will get reply notifications on clients that havnt added support.

Replying to

It's awesome! I am about to release the Git integration in Amethyst. Now I can see a notification when a new patch is submitted. :)

nostr:nevent1qqswq56myvvhusyudfy2wr2xhhsdxmrjpny577pc4a23kf3g5p8tf3qszxy6c

Fantastic! Would you consider supporting the display of the 'issues' kind: 1621

Example:

Replying to

Julia Evans

i just understood today that the reason I feel stressed out about merge commits is that you can't figure out the contents of a merge commit by looking at it with `git show`

for example in this screenshot I have two merge commits (`merge1` and `merge2`). They both have the same parents. They display the exact same way with `git show`. But they have different contents.

Do you think merge commits are an important or even required feature for a git code collaboration solution?

I'm working on nostr based git tools, which draw heavily from the patches-over-email model which doesn't involve merge commits.

I'm unsure how much to lean into suporting the branch based PR-like model.

Replying to

ANOUNCEMENT: first release of ngit and gitworkshop.dev

i'd love your feedback, its really easy for repository maintainers to try out.

https://gitworkshop.dev treat it as alpha

nostr:nevent1qqsqm4qhhlkfn9jf8ceux4kgldhdkn5fz5ss7r7yeuxltawjky95u2gppemhxue69uhkummn9ekx7mp0qgs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngrqsqqqqqppy88fm

I completely agree. That's why I started ngit and https://gitworkshop.dev

Replying to

kuiperbelt

is there a github clone for nostr? would that be a good idea? maybe all it needs is to link to existing git repos #nostr #git

Serendipitous that you asked the question today

Replying to

ANOUNCEMENT: first release of ngit and gitworkshop.dev

i'd love your feedback, its really easy for repository maintainers to try out.

https://gitworkshop.dev treat it as alpha

nostr:nevent1qqsqm4qhhlkfn9jf8ceux4kgldhdkn5fz5ss7r7yeuxltawjky95u2gppemhxue69uhkummn9ekx7mp0qgs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngrqsqqqqqppy88fm

Replying to

Seraf

Hope it work with Obtainium...

We definitely should look at how to achieve this. I'd love to have obtainium verify that APKs are signed by the developers and nostr would be ideal for this purpose. Obtainium would have to add nostr features like websockets and event signature verification support. I wonder if they'd consider a PR.

I'd imagine we'd have to get a userbase of freedom projects first.

Replying to

New Nostr Git Client: https://gitworkshop.dev/repo/amethyst/

Thanks for sharing

Replying to

Laeserin

I try not to even look at it. It's like the scene of an accident.

Just focus ahead and drive past.

How many NIPs are you using?

Replying to

Great feedback. If it is not on a feature branch it expects a reference. Ill change it to defaulting to the most recent commit instead of throwing an error.

nostr:nevent1qqsqm4qhhlkfn9jf8ceux4kgldhdkn5fz5ss7r7yeuxltawjky95u2gpr3mhxue69uhkummnw3ez6vp39eukz6mfdphkumn99e3k7mgzyzsq3hh327t0h2dq6matqn5064cgj2zanl2stkj6s0lg4t2h5dty6qcyqqqqqqg9dxat3

I have implemented this and it will be in the next minor release.

commit:31c085a584cbd30f71a44a70eaf828c2c8c5f6e3efb7942547edb37cf4a632cf

Replying to

CXPLAY

另一个更完善的 #Git over #Nostr 软件.

Thanks for sharing

Replying to

Santos

Overall quite intuitive, I really like the interactive commands. The only thing that I didn't get at first is that "ngit send" didn't let me send the last commit on main. Are you supposed to make a new branch, add the commits and then send? What I ended up doing is "ngit send HEAD^" and that seemed to work.

Great feedback. If it is not on a feature branch it expects a reference. Ill change it to defaulting to the most recent commit instead of throwing an error.

Replying to

Santos

Nice! Primal doesn't handle the reply very well since it does not display the patch and therefore shows that you are replying to @UNKNOWN. noStrudel seems displays it properly however. Btw great job on the UX on both the cli and the web app, pretty sleek!

thank you. was it ngit intuitive or did it take some brain power to work out what the commands would do?

Replying to

Santos

Nice! Primal doesn't handle the reply very well since it does not display the patch and therefore shows that you are replying to @UNKNOWN. noStrudel seems displays it properly however. Btw great job on the UX on both the cli and the web app, pretty sleek!