Prioritize discoverability, and self hosting on my own domain, with more customization for the protocol and ui/ux aspects.

Basically allow people to deploy something closer to gitea on a webserver initially, which has all the basic protocol features and sharing aspects implemented.

Currently the focus seems to have been very much on just the seeding & p2p part which honestly is good but not very useful for me as a developer/user who wants to work on a collaborative project.

Prioritizing P2P makes sense, but the UX/DX of radicle is not intuitive to put it mildly.

I went to the explorer radicle.network and my own as well and I still had no idea how to create an issue or submit a patch or login to an account or anything of that sort.

I opened the cli and figured out how to do all that, but then I created another node on my web server and now I have no idea how to connect to it, then I figured out how to do that, now how do I share my node without sharing it publicly, figured that out.

Cool now we are at the starting point, so every time I need to work on a project i will have to clone it, but why can't I create stuff in webui.

Maybe there is a setting I can't seem to find it yet.

But the jumping through hoops is mindbending. For a solution that could replace github for me and my friends who maintain a few public projects that wants small contributions from large number of folks as we try and maintain the local "tech" clubs.

Getting low information folks to use within 10 mins, is the bar that I have set for any platform I can use to replace github.

Radicle isn't that yet! anyways.

But I like the direction, putting contributors, access list, issues and prs in the repo is a brilliant idea, maybe put agent plans in it too, agent sessions as well maybe...

I would go as far as to say, something like a radicle network is better than every other alternative, but the UX is just not there yet.