3 ms·
We need a system where repositories are duplicated in different political jurisdictions that don't get along with each other. A copy in the US, a copy in the EU
by Animats 7y ago
We need a system where repositories are duplicated in different political jurisdictions that don't get along with each other. A copy in the US, a copy in the EU, a copy in China, a copy in Russia, a copy in Kenya, a copy in Japan, a copy in Vietnam, a copy in Iran. With hashes on a blockchain every few days to check for tampering.
- a_t48 7y agoYou don't need a separate blockchain (for the actual code stored in the repo). Git already provides hashing. How do you propose to deal with merges across half a dozen different repositories, though?
- clarry 7y agoDon't merge, just mirror. Sign everything. If a mirror finds fresh data on another host, with signatures that check out, grab it.
- a_t48 7y agoWhat happens when two different hosts merge at the same time? ...I guess that's what the blockchain is for - to mediate conflicts. Feels gross to me, though.
- clarry 7y agoWell you can come up with any number of solutions with various trade-offs. One obvious choice is that there's only one maintainer doing merges -- if they sign and push different content to different repos, it's a problem of their own making. So unless they screw up, there's no need to worry. Other than that, you could give priority to any change based on e.g. its timestamp or hash. Sounds arbitrary? Yes, but such is life. If two people push a branch to be merged simultaneously to a repo where everything is merged to master after rebasing, one of them (depending on luck) is going to find that their commits landed while the other soons finds out that they need to rebase and try again. In a scenario with multiple mirrors, you'd obviously want to try to use the same repo when possible, but if you don't, it'll take a little longer for you to find out that your stuff was overruled by changes in another mirror.
- csydas 7y agoWhile I appreciate what you're going for, this wouldn't fly for countries imposing sanctions and the next immediate question from said countries to the repos would be "so how do you plan to stop this replication or penalize persons engaging in it?" Sanctions aren't really logical when you get down to it -- at face value they're supposed to put a specific stress to either motivate a population for change or impact the bottom line of targets enough to frustrate them into cooperation. In reality, the targets of sanctions typically are not affected, and those who are affected lack the ability to make meaningful change in the near future or even an extended future. Basically, even if you do something like this and replicate using a system outside of the intended mechanism, the sanction-ers' response is simply "why aren't you just banning them?" Call me cynical, but if the cost is bad publicity vs favor with the US government, it's not hard to see why a given company would choose favor. (I don't condone this, but I've lived in Russia for 6-ish years now as an ex-patriate -- it's...pretty clear that the sanctions affect no one they're intended to, and it's not like Russians haven't tried to change the status quo (they really have). But really, nothing has changed since the sanctions were imposed except a readjustment of prices and salaries)
- michaelmrose 7y agoCouldn't you just have independent entities not obliged to each other or a central authority that choose to replicate the others content. Each entity can easy be forced not to replicate content from a sister jurisdiction or allow connections from within that jurisdiction but how are they supposed to keep entities from pulling data through a proxy they themselves are not appraised of or a client pulling data from multiple centers to get the complete picture. Censorship in that case merely makes service slower not nonexistent.