A more challenging problem is that this protocol allows Alice to cheat by double spending her infocoin. She sends the signed message “I, Alice, am giving Bob one infocoin, with serial number 1234567″ to Bob, and the message”I, Alice, am giving Charlie one infocoin, with [the same] serial number 1234567” to Charlie. Both Bob and Charlie use their copy of the block chain to verify that the infocoin is Alice’s to spend. Provided they do this verification at nearly the same time (before they’ve had a chance to hear from one another), both will find that, yes, the block chain shows the coin belongs to Alice. And so they will both accept the transaction, and also broadcast their acceptance of the transaction.
When we want to acquire useful knowledge, we have to search the web broadly, find experts by word-of-mouth and troll through various poorly designed internal document sharing systems. This method is inefficient.
However far-fetched that may sound, what identitarians like Mr. Spencer have grasped, and what ostensibly anti-racist thinkers like Mr. Coates have lost sight of, is the fact that so long as we fetishize race, we ensure that we will never be rid of the hierarchies it imposes.
No real sync exists like you mention exists.
The closest solution is what I and a few others do. Using a cloud replication service, such as Micorosft OneDrive, Google Drive, Dropbox....
You put the catalog, all pictures, and make sure to include preferences and plugins in the same base folder, in the replication service. Now, everything will be replicated between the computers. However, and this is a big one, you CANNOT open Lr on the second computer until replication has finished between both computers. Otherwise, your catalog can become corrupted and/or end up with duplicate conflicts.