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

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...

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

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...

We'll have more docs on this very soon. Also see https://news.ycombinator.com/item?id=48153535 for more info

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

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.

Comments URL: https://news.ycombinator.com/item?id=46076809

Points: 12

# Comments: 1

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.

https://www.iroh.computer/

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).

Comments URL: https://news.ycombinator.com/item?id=44325617

Points: 294

# Comments: 424

I highly recommend reading Lila, by Pirsig too!