Since posting this last week I vibe-coded my own personal github replacement that runs on my homeserver. For my personal projects I have no use for github anymore. Going to slowly evolve it into something other people can use - with nip34 support.
The more i vibecode and the better i get at it, the less i find github useful. I already have self-hosted runner so don't need their ci. it's move convenient to store issues and roadmap in text files so i don't need issues. Starting to do a local merge pipeline so don't need PRs.
Just saw this neat video which makes me want to stop using the GitHub git server https://blossom.primal.net/734b358761ae40b5f2bb02b379d0b4119ef6dc787a1c4113661715cb2ac73981.mp4
Might work well with gitworkshop, too (cc nostr:nprofile1qy2hwumn8ghj7etyv4hzumn0wd68ytnvv9hxgqguwaehxw309a5xzan9dchxgctwvdhkuamp09jx2a3wvdhk6qpq5qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exsweceyk)
Discussion
Looks like a good start. When dark mode? đ
Excellent news. What do you think of ngit.dev/grasp ?
I'm not sure yet. I played with them a little.
I don't agree with this thesis screenshotted below. So far it seems shockingly easy to host my own git server. The only thing I'm missing in my setup is really good backups and ability to have other people collaborate with me. I'm building up a little https://restic.net/ based system for the backups, and nip 34 seems to largely solve the collaboration. So I'm not really sure that grasp or ngit solve any problems for me? Switching to a new tool needs to have a very clear benefit and I don't see one here yet. But I might be misunderstanding something!
How should someone send you a PR (a change to big for a patch in a nostr event)? Must they run their own server and host their own fork?grasp makes it easy for contributors to send you PRs without you having to rely on infrastructure they provide.
Why can't they just push a branch to my git server?
Is it compeletly unauthenticated?
I don't see why it couldn't allow unauthenticated http for branch creation. Github allows it by default, right? From security pov, fetching the patches over nostr would be nice. I can see the benefit of that.
You have to be logged into github to push to their servers which helps with spam prevention and malicious activity. And you can only push to repositories you have explicitly been given access to (you can fork repos that you have read access to). For me, contributions as patches over nostr would be the ideal flow but the event size limit makes that not always possible. Grasp enables the PR flow without relying on the git data being on only one server.
Yea I can see that. I'm glad you are exploring that avenue. I will play with it more here soon!
Youâre relying on non-attributed, copyright-violating AI to rebuild you a clone of gitea or similar. You didnât create anything.
You may think youâre contributing to âself-hostingâ, self-sovereignty, etc. but I think youâre another example of how this little movement of open source code over the past ~30yrs finally shoots itself in the foot.
lol