this post was submitted on 05 Mar 2024
68 points (90.5% liked)

Open Source

31230 readers
306 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS
 

Just finished writing out a lengthy comment,
with the up/downsides I can see
on each of the code forges I currently deem promising,
on the Github Discussion "Alternatives to GitHub"

And I was wondering, out of following 2,
which code forge would you guys prefer and why?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 14 points 8 months ago* (last edited 8 months ago) (2 children)

I don't need or want replication of my private projects to a peer to peer network. That's just extra bandwidth to and from my server, and bandwidth can be expensive. I already replicate my code to two different places I control, and that's enough for me.

I'm not sure who Radicle is for, but I don't think the casual hobbyist looking to self host something like Forgejo would benefit at all from Radicle.

Loading the source code for Radicle on Radicle also seems fairly slow. It seems this distributed nature comes at a speed tradeoff.

With the whole Yuzu thing going on, I can see some benefit to Radicle for high profile projects that may be subject to a takedown. In that respect, it's a bit like "Tor for Git."

I suspect that over time, pirate projects and other blatantly illegal activities will make use of Radicle for anti-takedown reasons. But to me, these two projects solve two different problems, for two different audiences, and are not really comparable.


Edit: There is already enough controversy surrounding Radicle, that, if I were someone looking to host a takedown-resistant, anonymous code repository, I would probably be better served hosting an anonymous Forgejo instance on a set of anonymous Njalla domains and VPSes. The blockchain aspect was already a bit odd, and what I'm now seeing from Radicle does not exactly inspire confidence. I don't think I'll ever use this.

[โ€“] [email protected] 0 points 8 months ago (1 children)

There is already enough controversy surrounding Radicle

LMAO!

Please get rid of: node.js, npm, packages from npm, Electron, svelte. Cargo and crates are also not good. #1469

Are you seriously calling this "controversy"? One dude saying npm is backdoored? ๐Ÿคฃ And he wants them to remove JS from the project as well as rust. My sides. What should they be using? The almighty C?

Amazing. I literally was wheezing while reading the "issue". Thanks for giving me a good laugh.

CC BY-NC-SA 4.0

[โ€“] [email protected] 0 points 8 months ago

I'm not talking about that. I'm talking about this:

I agree with the sentiment here, but all the technologies mentioned allowed us to ship a working application in a timely manner. I think that should always be the first goal. Now that this is out of the way, we can start looking at improving efficiency, security, resilience etc.

"Security Second" is not good messaging for a project like this.

But I'm glad my comment was hilarious to you.