<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style='font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;'><div id="message"></div>I would live to have a local copy; Tim raises a very important issue.<div><br></div><div>The peer to peer of croquet and massive distribution with no single point of failure.</div><div><br></div><div><br></div><div><div id="signature"></div><div id="content"><br> ---- On Wed, 08 Sep 2021 15:55:24 -0400 <b> tim@rowledge.org </b> wrote ----<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); padding-left: 6px; margin-left: 5px;"><div>One fun issue of working remotely with a monticello repository on the other side of the world comes when something messes up the connection - power, network issues, war, asteroid strike, the usual things. Sure, we have the very local package-cache as a backup of sorts but given how easy it is to run a local SqueakSource instance it would be nice to have a way to to use it as a smart buffer to the 'real' repository, or maybe have repository types that have two (or more) outputs, whatever.<br><br>Some googling suggests a few other people have been interested in the general idea but I didn't spot any solutions suggested. Before I burn any brain cells on it, has anyone actually worked on this?<br><br>tim<br>--<br>tim Rowledge; <a href="mailto:tim@rowledge.org" target="_blank">tim@rowledge.org</a>; <a href="http://www.rowledge.org/tim" target="_blank">http://www.rowledge.org/tim</a><br>Useful random insult:- A gross ignoramus -- 144 times worse than an ordinary ignoramus.<br><br><br><br></div></blockquote></div></div></div><br></body></html>