Le projet #Radicle (forge en P2P) a publié une interface desktop
https://www.radworks.garden
https://radicle.xyz

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

@jerger @yorgos @radicle #radicle is architecturally _very_ different from conventional forges - including forgejo.

Fellow #GitHub users ! I need your help!

Context: More and more people are trying out @radicle as a #decentralized #GitHub alternative.

#Radicle has a different identity system than Microsoft's, so when moving projects over to Radicle it is important to know which GH user the Radicle projects belong to.

What would be a way you would use to link your Radicle and GitHub identities?

(Radicle identity is based on #SSH keys, specifically `did:key`).

Boosts for reach - appreciated.

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

I'll be hosting an open Radicle CI office hour meeting today at 13:00 UTC at https://meet.jit.si/RadicleCI for anyone interested in CI with Radicle. (That's 3 hours 15 minutes from when I post this.)

Radicle is an open source, peer-to-peer code collaboration stack built on Git. I work on its CI support.

cc @radicle

#Radicle

@radicle looks like an interesting Free Software to check out: it’s a peer-to-peer, local-first git forge for the decentralized Web! 👀

#Radicle #p2p #DWeb #decentralization #decentralized #git #gitForge #software #FreeSoftware #openSource #localFirst

https://radicle.xyz/

@boramalper

Correct! ;)

@roy_calum

You could start with seeding the #Heartwood repository (the reference implementation of the #Radicle protocol), for sure!

In addition, you could look at a couple of community resources to help you decide:

- The awesome-radicle repo: https://app.radicle.xyz/nodes/seed.rhizoma.dev/rad:z3yQUb9HDAC7TQrUDGkQsXDsYFj9G
- A quick search tool to help you discover more content: https://radicle.kuehlewindt.com/

@radicle

starting out with #Radicle
if you know good repos to seed, hit me up!

@radicle
https://radicle.xyz/

#OpenSource #Collaboration #Decentralized #Peer2peer #P2P #Git #GitForge

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

Maybe I should set up #radicle today.

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.

#HardenedBSD

Here we go!

#Radicle #HardenedBSD

Do you like @radicle but aren’t exactly enthusiastic about self-hosting your #codeForge?

Talk to us to find out about a hosted #radicle node offering!

Have us spin up your team’s seed node and CI runners and move your code to the global #peerToPeer network!

#OpenSource #ForTheWin #foss #git

Really exciting new features announced for upcoming @radicle protocol versions!!

1. Canonical references (branches, tags, releases)
2. Identity improvements: more #DID methods, e.g. #bluesky ‘s `did:plc` / `did:web`
3. Multi-device identity
4. Agent repositories for richer user profiles

🥳🍾🤩

#radicle #peer2peer #localFirst #git #privacy

Really looking forward to the
@radicle meetup in a couple of hours in #Berlin !

Some interesting presentations and exciting announcements coming up !

Don't miss it if you're in the area! ;)

https://lu.ma/ijduqnfe

#radicle #localFirst #peer2peer #forge #git

For #remote work … to work, in person meetups are **essential**!

Recommend: 2+ a year, as circumstances allow.

This week I’m visiting #Berlin to catch up with the @radicle team.

Enjoying every minute of this face2face with my wonderful colleagues and the great atmosphere in this city!

A+++

#radicle #localFirst