@yorgos @radicle @tshepang @data0 @ayo

Thank you, that is wonderful.

I can add that people I work with already have a yearslong experience with #radicle, and they were very positive about its operation.

Kudos to the great efforts of you and your team!

@smallcircles

Anything we can do on the #Radicle side to help you try out @radicle , please do let us know!

We're currently working to smooth out the rough edges of the onboarding experience, so any problems you come across would be really helpful to know!

We're over on https://radicle.zulipchat.com/ . Please feel free to join us! :)

@tshepang @data0 @ayo

@voidcontext @radicle Signing a commit (with the radicle ssh key) and then pushing it to GitHub is certainly a great way to show the accounts are linked !

As far as I understand, that is only on the project level though - not on the user level.

I would ideally be looking for a generic way for the GitHub user to attest "this is my #Radicle public key and here is something signed by it to prove that it really is mine".

Maybe signing a commit to their "GitHub Profile Readme" though ??

@tshepang @data0 @ayo

For its 'hackability' as advertised on the project page, and that it is a more lightweight comprehensive codebase in Rust.

But at this moment we are looking into both, using #radicle as-is as a daily driver for our own purposes and #ayllu to integrate with. (Though this is currently on pause).

@ferki @radicle Start from https://radicle-ci.liw.fi/ and hang out on the Radicel Zulip "#radicle-ci" channel (https://radicle.zulipchat.com/#narrow/channel/452370-radicle-ci)

Hi @algernon o/

Would you mind if I asked "why" ?

I think it's important we capture that "why" on the #Radicle side, because our assumption so far is that exposing a homelab / laptop radicle-node as a Tor hidden service [1] was enough to get us around without having to worry about punching holes through NAT.

[1] - https://radicle.xyz/guides/user#4-embracing-the-onion

@liw

This is showing A LOT of progress. I would like to thank the #Radicle development team and community for their help!

We're getting closer to replacing our self-hosted #GitLab instance.

@Gray Was the repo set up with just a single delegate?

Generally speaking, in cryptography (that #radicle relies on), it's pretty destructive to lose a private key and there isn't a way to recover from that.

It is recommended to set up repos with at least 3 delegates (2 delegates have the problem that if one key is lost, you can't reach quorum for further changes to the repository identity).

You might want to join https://radicle.zulipchat.com and the #support channel there for more details.

@gvwilson You could look into #radicle and other projects which are trying to create truly federated forges.

@ayo did you come across #radicle yet? Looks really intriguing. They did a lot of R&D, seem to have nailed the #protocols now. I'm going to try it for my next #opensource project

https://radicle.xyz/