GitHub and GitLab are mature yes but what happens when they don't work for you anymore? It's all one company. That's what we're trying to solve. The beauty of it is that existing projects don't need to migrate, they can just cover their backs by pushing to GitHub and Nestr. Much like the current X influencers could (and probably should) cover their backs by establishing a Nostr presence for when they get deplatformed.

Reply to this note

Please Login to reply.

Discussion

You can self host GitLab. But that is a minor point.

I'm only speculating on why people may not just start using it right away. I certainly do see the benefit of it existing. But it seems that it isn't even released yet, so anything I said is moot until it can actually be widely used and feedback comes in. It is cool that you can push to both, but is that the same thing as fully using both in tandum without choosing one or the other as the primary? That sounds like a backup, but not really an ability to actually utilize both simultaneously. I just don't think it's going to catch on broadly for years and don't really see that as a problem with it as a concept. I suspect it will be used by a lot of smaller niche projects early on though. I will certainly be trying it out. But for really big projects? I just wouldn't take their silence as a negative sign necessarily. It can take years for bigger machines to seriously consider a new tech (See Bitcoin and even Nostr in general).

One huge benefit is that you don't actually need any external git server for Nestr so it's much easier than self-hosting any other git service.

You seem to think I'm arguing against the merit of the thing and in favor of another when I'm not. I'm simply pointing out that people don't tend to just immediately hop onto a brand new thing (before it's even available in this case) and that such a reality isn't a negative sign against the new thing. My comment applies to any brand new tech, regardless of the merit over alternatives or promises it makes.

No no, I actually think we're agreeing completely 😄

You make some good points there. I personally think the same way but I don't see Nestr as a backup since tracking issues over Nostr is more resilient than tracking them on a centralized platform. And I'm not expecting bitcoin core to jump on straight after launch 😄 that would be ridiculous given how slow core MUST go. And that goes for many other big projects as well like you said.

You are misunderstanding so many of my points that I'm going to go ahead and end the conversation. Thanks for your work and good luck.

I'm not worried. this is how new things begin. perhaps projects will start off using nostr alongside github and as usage grows on the nostr side, fully transition to only accepting issues and PRs over nostr.

nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr 's noStrudel is just one example of a repository on the journey. its got 99 open issues and 4 open PRs on github and 5 open issues and 0 open PRs on nostr.

https://gitworkshop.dev/r/naddr1qqykum6nw3e82er9dsqs6amnwvaz7tmwdaejumr0dspzqfngzhsvjggdlgeycm96x4emzjlwf8dyyzdfg4hefp89zpkdgz99qvzqqqrhny5zxf4f/issues

Issues and PRs raised on nostr get interest and engagement from across nostr and not just users using git specific clients. So the value proposition is quite different than self-hosted gitlab / forgejo.

Exactly. That's all I was really trying to say here. It takes time for things to catch on. Not seeing hype everywhere isn't necessarily a bad thing.

That and some people don't want to be alpha or beta testers for everything. I don't. Kudos to those who do. I do on occasion, but bandwidth is limited.

When I say bigger projects, I also mean developers even in the Nostr space working on some of the more popular applications. It may take time for everyone to learn and move over. All I'm saying is that crickets in the beginning aren't always a bad thing. It just takes time.