@DanConwayDev
freedom tech developer and creator of ngit, https://gitworkshop.dev and https://metadata.nostr.com
Relays (3)
- wss://relay.damus.io/ – read & write
- wss://nos.lol/ – read & write
- wss://eden.nostr.land/ – read & write
Recent Notes
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 @fiatjaf will hate it and @Justin Moon will love it. Here is a draft spec:
2
Fucking YouTube.
Yeah, I couldn't find it either. @Ayden had the right approach. "Look into nostr solutions to git"
nostr could be a good home for the FOSS developer community
One small complaint. the text in the UI tends to get really small and seems to be all different sizes.
I'm guessing this is from claude bad habit of always setting text-xs classes on everything
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.
1
I'm just repeating whatever my favorite influencer nostr:nprofile1qqsprwdgjszdhucrfelp3p46nhzvd5mk7gu6zxp8r0fwc4n63zv9pnspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszr...
I was that solitary podcast listener that made it to end of the episode; accurately profiled as a nixos user.
1❤️3
How does this compare to git.iris.to ?
In gitworkshop.dev you can browse and comment on issues and PRs for repositories created with git.iris.to. You can't browse the code because git.iris.to uses hashtree.cc which replaces the git client/server protocol with a blossom based approach. Gitworkshop nudges users towards GRASP which builds on the battle-tested and super efficient git client/server protocol to enable distrubuted hosting permissioned with nostr identity. ngit.dev/grasp
21❤️1
Nice, thanks for the info, very helpful! I don't currently know anything about Grasp, but I would expect that it handles authentication simply by allowing anyone to upload any commts anywhere, but che...
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
Can someone write a beginner's guide for people who never used github?
What are you trying to achieve? eg. publish your own code, create a PR, report a bug/request a feature on an existing repository
💜1
