That's absolutely possible. Everyone is empowered and encouraged to run their own seed nodes. Which would allow you to have an isolated network. Check the docs to find out how to run your own: https://docs.radicle.xyz/docs/using-radicle/running-a-seed-n...
This comment is spot on, people who jump to the conversation with the argument that Git is already decentralised don't understand where the most value is captured when it comes to collaboration. It's the social artifact, issues, PRs, etc. And the cost of migrating the community of a project/organisation and their social artifacts is a massive cost, carrying the risk of splitting the community and or stifling any other progress to stay relevant.
This is really helpful feedback. Especially the part about not getting enough feedback during operations. And yes social features like issues and PRs have not been the focus in this release, as we focused on replication. If you are looking for more help you can join the community matrix and we take it from there: https://docs.radicle.xyz/docs/using-radicle/join-the-communi...
The reason you can push/pull works offline is that the database of radicle lives on your machine. Once you are online it will gossip with other peers to exchange updates of projects. This means that your workflow stays the same no matter connectivity and eventual the network convergences to communicate all relevant data. If you are interested in the details check out the docs: https://docs.radicle.xyz/docs/understanding-radicle/why-radi...
Important to note that "Free" here doesn't refer to "for free". You rpoint about funding of popular projects was at the heart of radicle from the beginning. We believe that FOSS as backbone of the digital infrastructure needs to be sustainable, which includes the resources/funds to maintain it and keep it free and open. If you wanna find out more about the philosophy we follow, here is the original research and premise: http://oscoin.io/
Or you can file an issue on the app repo directly over here: https://github.com/radicle-dev/radicle-upstream/issues/new