There's a greentext that's been floating around for a while, I don't know the original author and can't remember the exact text to search for it, but it's along the lines of
> my deepest fantasy is that one day I'll be in the hospital for some random thing, they'll take blood for some test, and then when they read the results, their eyes will go wide and they'll call for a consult. The other doctor will read the results and say "you don't have the nutrient?! How do you live? You're so brave". They give me a shot, and just like that, I'm able to conduct myself in society, understand social cues, hold my attention on anything i want for any length of time, etc
... so perhaps the Nutrient is a product of a gut bacterium.
The story for sensitive/proprietary repositories doesn't feel well-fleshed-out yet:
> Radicle supports private repositories that are only shared among a trusted set of peers, not the entire network. These are not encrypted at rest but rely on selective replication and are thus completely invisible to the rest of the network.
There's no structural separation of public / private repositories; this is one bug or fat-finger away from a leak.
I was looking into how to get a radicle node running, but connected to only my own devices.
You can't seem to start the radicle node without it automatically connecting to the (generously provided) global shared seed nodes, and you can't examine/change the config without starting the node (at least with rad subcommands).
If you do `rad auth` and then delete the four seed addresses from ~/.radicle/config.json before starting the rad node, it helpfully re-adds them on startup:
[...]
INFO node Opening node database..
INFO node Address book is empty. Adding bootstrap nodes..
INFO node 4 nodes added to address book
[...]
(It doesn't add the bootstrap nodes if I instead add a seed "<randomDID>@10.254.254.254:8776".)
Is there a guide to using Radicle like one might use Fossil within a small company / within a small group of people (disconnected from the iris/rosa radicle.network seeds)?
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!
My idea of the term "bleeding heart" is more like "painfully aware of the plight of people (and often wants to make sure you're also painfully aware of it)", whereas the author's tone struck me as simply charity, and I enjoyed it as such.
For a brief hopeful moment, I thought this was the .io kind of sandstorm