I don't think that bounty should apply and I don't think we should try to replace GitHub, just step by step build the tools for doing code collaboration without a big central server.
I sense a disturbance in the force. nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m 's github replacement bounty appears to be bearing fruits with two or probably more implementations working on a compatibility layer for git repositories and an open standard for those. nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr
Discussion
The Linux kernel still uses email.
Just sayin. Yes, its C and patches, but its still worth understanding why it works better.
nostr:note15lchd7zvqx6yt44fj7ghjmd6xp54a7h6p0chg2767jtgqp45lu4smx4jer
Damus uses email for submitting patches too! Although we do use GitHub
If not for this then what do you think Jack had in mind?
Nobody needs yet another GitHub clone. There's already GitLab and Gitea and certainly others. We need a way to bridge these. An interface to make MRs from a self hosted Gitea instance to GitHub and a way to discover repositories no matter where they are hosted. At least I suspect that is what would make Jack happy.
His original bounty was totally not specific: nostr:nevent1qqsqkfjzlcx0fg7ymte3t0ka2wpzve68hykep8rq7aflj9svhg7jragpp4mhxue69uhkummn9ekx7mqpzpmhxue69uhkummnw3ezuamfdejsygyzxs0cs2mw40xjhfl3a7g24ktpeur54u2mnm6y5z0e6250h7lx5gpsgqqqqqqs684apg
His later post with link to bountsr did not make that more clear. https://web.archive.org/web/20230126232251/https://bountsr.org/code/2023/01/19/nostr-based-github.html
For what it's worth, I had suggested to fix discoverability and cross instance PRs as a reaction to his original post (although I can't find that event now) and he "liked" that.
Ok, what the hack. Ok, Jack why do you boosts Fiatjaf's comment? Could we please know what the bounty was about or at least how community consent could be measured? I'm super excited about the interoperability layer stuff (and websites that build on top of that to look like GitHub) and if not that, what is it you see so important to throw tons of money at it?
I think he has said in the past that his bounty was ill-placed. Me and Pablo and others had written that the bounty as it was put would encourage the wrong kind of behavior and that the approach should instead be more if a modular system.
Indeed we did see some bad behavior, like a project that cloned GitHub's UI and called it "nostrgit" without any plan or care about having it be a reasonable open protocol.
Although Jack had doubts about his bounty, it stands as in "it was not retracted or superseded" and as long as it's not broken down into smaller bounties it will inspire devs to run off in the one direction or the other. In which direction should they run off in the meantime? I love nip34 and https://gitworkshop.dev if I understand it right. Both clearly are going in the right direction unless I totally get it wrong.
We’ve been working on the bounty since the beginning and are almost ready to release the working product. nostr:npub1u9e887ad8pl49cxgzqkuljxcxy89dtac7jkyuajnukxg6hu2hufqdjdsp7 nostr:npub1h0rnetjp2qka44ayzyjcdh90gs3gzrtq4f94033heng6w34s0pzq2yfv0g
I encourage you all to be a bit more patient — lower your time preference and stick to the goal of building a social media app like GitHub. Otherwise, how we will recruit that masses? CLI tools and email? Give me a break.
Don’t squash this egg right before it hatches… 🪺 nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m
Otherwise, how will we recruit the masses?*
My OP was to gauge activity. People with heads down working on a thing can burn a lot of resources and stirring some discussion around this might help to get some either to fomo reveal some progress or to drop out as they see what they are working on is not the right thing.
Re: "CLI tools and email? Give me a break."
Many great tools were built on well designed APIs or actually using CLIs on the backend. NIP34 will be the API. ngit a CLI using such an API. Devs need nothing more than a CLI to test workflows. Designers can then wrap some fancy UI around that. That's normally how Open Source development goes. Some devs know how to solve a problem of theirs. Only later some less technical people pay designers to make it work without a keyboard.
Is Nostr not about decentralized social media? GitHub is social media for coders. Combining them is a great idea. CLI isn’t enough.
But of course, GitNestr has a CLI tool as well. The full picture is the real prize though.
I bet whatever works best will take the world by storm. Developers love trying out new things.
Whatever wins, I hope it fixes discoverability so when I next shop around for developers I will not have to check their portfolios exclusively on GitHub. I want some "ngit search npub..." to find all the projects that npub contributed to regardless on which servers and including the patches that were not hosted on forks of projects.
🫡 Salute to that sir! Let the best product win. I just hope the bounty isn’t canceled.
Let people “feel” the products. If they all are terrible, then cancel it. But I have a feeling we’ll end up with something very useful & as intuitive as GitHub. 🔐
That functionality will certainly be possible on #GitNestr. We setup permissions to handle this exact problem.
It's true we have burnt a lot of resources while keeping our heads down. Still, our project will be completely FOSS after the alpha release and can therefore be altered according to the needs of the community. I hope we'll get lots of FOSS contributions. The bounty only gets us to the starting line so to speak.
I really think the discussion will be more fruitful once we have a working MVP.
🤦♂️ Give it time.
Reneging on a bounty after people have been working so hard seems wrong. Give everyone a chance to showcase their versions.
Everyone knew a bounty would produce competitors… that’s the point. Let the best product emerge from the competition.
I’m working on the problem from another direction.
IMHO, Nostr isn’t the right platform for this because it doesn’t guarantee IP privacy.
I expect devs will be increasingly persecuted in the future. There needs to be a system that devs can use to publish code pseudonymously - with IP privacy by default. Other devs should be able to subscribe and access code privately by default too.
I’m not specifically chasing the bounty so I’m happy others are working on it. I’m hopeful we can learn and improve the options available to protect devs.
Unless you are talking about intellectual property ... nip34 or ngit should work using separate npubs via VPNs or TOR. What am I missing?
Yes, all what's proposed is for brutally transparent development, only but you can hide your ID.
If IP privacy is optional then it doesn’t really exist. Maybe you’ll reuse the same npub in another insecure client. Maybe you’ll forget to reenable the proxy selection after testing. Eventually a opsec mistake will be made and you’ll dox your entire history.
Brutally transparent development is fine. My perspective is that you shouldn’t be responsible for privacy. It should be fundamentally built into the platform — always on.
Nostr is great for random social chat but privacy is an afterthought.
IMHO not suitable for secure private software development.
Yeah, well, it's been some time. Let's all work in the open and pool our brain power. I hope nobody bullshits Jack into giving the bounty to anything but the most deserving people. I would love to see teams to pool forces and then agree on how to split funds instead of one beating the other.
And for the record, I'm not in the race for this bounty. I'm just enthusiastic about seing GitHub dethroned in a much more cypherpunk future where unstoppable code gets developed by shadowy supercoders.
Soon it will all be out in the open. I’m interesting in releasing a finished product. I met with Dan in Japan and learned a lot from our chat. We’ll see if he adapts his frontend to my backend spec, or if he sticks with his own path. I already recruited nostr:npub1u9e887ad8pl49cxgzqkuljxcxy89dtac7jkyuajnukxg6hu2hufqdjdsp7 of the NostrGit project to join forces, and a great developer from South Africa. Our main relay/Merkle Tree coder is from the U.K. We have an international team making this happen.
nostr:note1g0daucnweu4xsuy0sru4kgvl2deyph8745ew0x2sud9ahjqup2lq28uxrg
I’m interested* in releasing a finished product.
so GitHub death by a thousand notes 👌