2color

In the quick start guide you can find Radicle on package managers: https://radicle.dev/guides/quick-start

In addition to the issue and patch COBs, there's also radicle-job COB for registering CI runs with commits (https://radicle.network/nodes/iris.radicle.network/rad%3Az2U...) and radicle-artifact, a COB for artifact distribution (https://radicle.network/nodes/radicle.norman.life/rad:z4VYyJ...).

A bit like how ES2015 adopted a lot of features from CoffeeScript

As someone who joined the project at the beginning of the year, I can assure you that the team cares a lot. Hindsight is always 20/20.

We will work hard to regain the trust of the community.

We have a prototype demonstrating writes from the web:

https://radicle.zulipchat.com/#narrow/channel/369278-Explore...

This is definitely on our radar.

You can see public network metrics here: https://probelab.io/ipfs/

About 800k unique DHT clients are seen weekly.

The way I would put is as: Iroh + iroh-blobs == libp2p + UnixFS + Bitswap, and the latter three are some of the critical components that have defined most IPFS implementations.

We built an IPFS-like system for distributing files in the radicle ecosystem with Iroh and iroh-blobs: https://radicle.network/nodes/iris.radicle.network/rad%3Az4V...

The way I would put is as: Iroh + iroh-blobs == libp2p + UnixFS + Bitswap, and the latter three are some of the critical components that have defined most IPFS implementations.

We're using in Radicle for artifact distribution: https://radicle.network/nodes/iris.radicle.network/rad%3Az4V...

And also working to replace the Radicle's networking stack with Iroh: https://radicle.zulipchat.com/#narrow/channel/369274-General...

Try the getting started guide: https://radicle.network/guides/getting-started

Radicle uses a key for your identity. There is no username. You can self-assign an alias for a more human recognisable name.

Radicle contributor here.

It's the same project. radicle.dev is for the protocol, radicle.network is for the network explorer.

Note that that radicle.network is a static site that you can also self host: https://radicle.network/nodes/rosa.radicle.network/rad:z4V1s...

It seems like the core dev is behind this: https://x.com/callebtc/status/2080608602432082217

Regarding 2, we're actively working on radicle-artifact as an alternative to Git LFS with transport agnostic distribution (https/p2p), attestations, and redactions.

https://radicle.network/nodes/iris.radicle.network/rad%3Az4V...

radicle-artifact is currently under active development: https://radicle.network/nodes/iris.radicle.network/rad:z4VYy...

Radicle contributor here.

When a repository is initialised as private [1], it's encoded in the repository identity document. The only way to change a repository to be public is to update the identity document; in the case of a repository with multiple delegates (repo maintainers in Radicle nomenclature), such a change requires a quorum to be met. So I'd say it's more than a fat-finger away from leaking.

> I was looking into how to get a radicle node running, but connected to only my own devices.

There's an open proposal [2] to introduce the concept of network configuration that would help with these kinds of use cases. Moreover, we're working on other ways to improve the collaboration experience for small teams, so stay tuned and thank you for this feedback!

[1] https://radicle.dev/guides/user#initializing-a-private-repos... [2] https://radicle.network/nodes/iris.radicle.network/rad:z3trN...

The general idea is using the radicle-ci-broker [1] to hook into repo events, and trigger different adapters based on the specific CI/CD tool you use.

We'll have more docs on this very soon!

[1]: https://radicle.network/nodes/seed.radicle.garden/rad%3AzBNX...

What are you missing from Radicle today that would make you chose Tangled over it?

Same here. They've built an amazing toolkit that's such a joy to build with. Feels like game changer to have p2p that both reliable, fast, and fun.

I like that more people are thinking solving some of the problems of digital inheritance we face. These are problems that are so important now that so much of our lives are digital and tapping into ones actual social circle seems the best way to do this.

Also, kudos for packaging it as a static web app. That's the one platform I'm willing to bet will still function in 10 years.

same

I am sympathetic to the criticism of the naturalistic fallacy, however there are some aspects of modernity that are unquestionably toxic, like air pollution.

A good way to avoid the "how are you?" small talk trap, is to ask "how are you sleeping?"

There's a `loadOrCreateSelfKey` function which you can use to load the key from a persistent datastore (fs).

It's documented here: https://github.com/libp2p/js-libp2p/tree/4420fad686921f88785...

I'll be sure to update the docs to include an example in the config docs.

I wouldn't be surprised if it's built with Iroh

https://www.iroh.computer/

Same. It's much more customisable out of the box and has a lot of nice features.

It's a very exciting moment for this movement. A lot of the research and tech for local-first is nearing the point that it's mature, efficient, and packaged into well designed APIs.

Moreover, local-first —at least in theory— enables less infrastructure, which could reignite new indie open source software with less vendor lock-in.

However, despite all my excitement about embracing these ideas in the pursuit of better software, there's one hurdle that preventing more wide spread adoption amongst developers, and that is the Web platform.

The Web platform lacks building blocks for distributing hashed and/or signed software that isn't tied to origins. In other words, it's hard to decouple web-apps from the same-origin model which requires you set up a domain and serve requests dynamically.

Service Workers and PWAs do help a bit in terms of building offline experiences, but if you want users to download once, and upgrade when they want (and internet is available), you can't use the Web. So you end up breaking out of the browser, and start using Web technologies outside of the browser with better OS functionality, like Electron, React Native, Tauri et al (the https://userandagents.com/ community is doing some cool experiments in this space).

Fun read and great reference to Zen and The Art of Motorcycle Maintenance.

I highly recommend reading Lila, by Pirsig too!

> Writing expands your working memory, lets you be more brilliant on paper than you can be in person.

So true!