I believe this is the most common scenario, yes. If you're used to actively pushing and pulling from the same branche as your colleagues, you need to learn how to manipulate diverging changes and conflicting bookmarks, but other than that all the jj magic is limited to your local activity.
I intuitively feel like more realistic games could be more fun, and that I might just have fondness for Space Cadet from growing up with it; but the more I played other pinball games the more I appreciate that space cadet is a simply great game to play, it feels great and there's a great variety of things to keep you hooked.
I wish I could find another pinball game I enjoyed as much. The closest experiences I could find are Xenotitle and Demon's Tilt but I found them harder to get into and get good at.
(My external barely informed understanding is that proponents of unification are largely right wing nationalist, pro-Russians call for a unification with Bessarabia while ceding Transsinistria to Russia; Moldovans are largely against union in polls.)
I was not aware of Radicle; it's a truly peer-to-peer Git forge which aims to guarantee commits are signed by current maintainers (among, I suppose, other goals).
The article mentions an us and a you, but I feel like it would have been an useful occasion to explain why move (from where?) and why Radicle. Maybe this was already discussed elsewhere?
I suppose similar discussions regarding GitHub are happening today and could explain why this was posted to HN.
> Radicle’s Collaborative Objects (COBs) provide Radicle’s social primitive. This enables features such as issues, discussions and code review to be implemented as Git objects. Developers can extend Radicle’s capabilities to build any kind of collaboration flow they see fit.
So instead of their self-hosted Gitlab instance being hammered, now their self-hosted Radicle instance will be hammered (and if they are lucky some of the other seeders will tank some of the load)?
I'm not sure that this will actually solve the problem. This seems more like a facade for a move they wanted to do anyways.
The load will be spread across the network, but I guess the main benefit is that everything continues working even though HardenedBSDs official seed is down.
Every user has their own node, and everyone's node talks to several seed nodes. Even if the official HardenedBSD seed is down, there's still going to be another node to sync with.
Does that actually work out in practice? Do you/someone here have experience with that in Radicle?
IPFS in theory has a similar model, but in practice I've mostly found that if the original seeder goes away, at least part of a dataset becomes inaccessible.
I think the difference between source repos and arbitrary data objects (which are as often as not images or videos) is that people tend to mirror repos locally indefinitely, especially if it's a local cache of something that they're repeatedly using as a dependency for other software that they develop.
If anything is good for the bittorrent model, it's git/source control. Movies and images get moved to different drives or deleted, movies become far less worthy of keeping after being watched, and images may have never been useful to the person mirroring them anyway; just a favor they were doing for a site they like. Source code sits, and source code continues to be used. If I understand correctly, Radicle works as your local git server, too.
The question is whether people will dedicate a little bit of bandwidth to seeding, but I don't think it's a serious question. It's a cheap and easy thing to do if you want to help FOSS, and it's obviously a good and a nice thing to do. It's not like you're seeding stuff that you don't know what it is, or why it is useful.
And, again, they can keep a seed up indefinitely. But they don't need to have either great uptime or great bandwidth.
I'm not doing anything huge, but my local radicle node is connected to ten other nodes at present, one of which is my own hetzner-hosted seed. Even if half of these go down, I still have full access to all the repos I follow.
Slightly worse in English, av2age mav2ick
reply