Hello ! Do you know Radicle? It's a decentralized alternative to Github, I don't know if it would be possible to connect the two, but it would make it possible not to rely on centralized services to host code.
Login to reply
Replies (4)
โ
EtherFi Airdrop Is Live!.
๐ Claim your free $ETHFI.
Telegraph
EtherFi
โ
EtherFi Airdrop Is Live!
๐ Claim your free $ETHFI.
๐ A total of 9 million $ETHFI will be distributed.
๐ฅ You are eligible...
I like radicle and I had some discussions with them about this. Unfortunately they use a different cryptographic curve which means you can't have a key which is provably a radicle key and a nostr key.
Ultimately, I think nostr is the better solution because it has its own ecosystem and doesn't try to create one from scratch.
I'm really impressed with radicle v1.0.0-rc4. There is a lot to like; some great ideas, well executed with good engineering, publicity and momentum.
NIP-34 on the other hand, has no usage, little momentum, and really basic tools with jagged edges and confusing interfaces.
I can see why your question arises and here is my answer:
Nostr has fundamentals which set it apart as a superior protocol for code collaboration.
Radicle has had 6+ years, $7m in funding and a team of 12 to mature, create polished experiences and build momentum.
NIP-34 is new and has 1 person full-time alongside a small number of contributors who are focused on other priorities.
With patience and a concerted development effort the features of nostr can shine through and provide an attractive decentralised alternative to github.
From the simplicity of design, existing relay infrastructure, and vibrant development community to the growing userbase and ecosystem of social clients which will notify users and enable them to interact without leaving their app.
I have drafted quite a few more thoughts about what we can learn from Radicle but they must wait for another note on another day.
View quoted note →
Wouldn't either of these 2 solutions work?
1. Have radicle and nostr protocols add support for each other's key formats as alternatives, updating related apps and backends to reflect this change
2. Fork radicle to a nostr version, with dual-access apps and backend implementations then likely emerging naturally
Nevermind
Looks like I've found the answer - radicle seems to just be malware that lies about being P2P
View quoted note →