Time, Not Cloning
Jeff Wilson · 29 Jul 2013, 15:13
· from 2013-July.txt.gz
This is the message as the crawl holds it, before anything
here touched it. What the conversation shows has been through ingest: transfer
encodings decoded, attachments dropped, quote markers repaired, and the
archiver’s ? resolved into quotation marks and dashes. Those
repairs are judgements and some of them are wrong, which is what this page is
for. Email addresses are obscured here as they are everywhere else on the site,
so it is before our repairs rather than byte for byte.
From: jwilson at clueland.com (Jeff Wilson) Date: Mon, 29 Jul 2013 10:13:12 -0500 Subject: (urth) Time, Not Cloning In-Reply-To: <20130729135412.1764.qmail at server281.com> References: <20130729135412.1764.qmail at server281.com> Message-ID: <c9e2349328bf7fe0dab8e17ca7da664d.squirrel at webmail.prismnet.com> On Mon, July 29, 2013 08:54, Brian wrote: > Jeff, > > I meant that when a Severian died (drowned, for instance), the Yesodis > replaced him by pulling a Severian from another time line. If they had > manipulated "their" time line to "undo" the death, there would not be > multiple corpses. And their is no "other Severian" to struggle with , > because a new Severian is only obtained when one dies. I'm still not seeing why a particular timeline is privileged above the others and made the recipient of their Severians when he keeps dying. Do the other timelines not have Yesodis watching over them? If it's the same gang of Yesodis watching over several Urthly timelines, why do they need to move a live Severian from Urth A to replace the one that died on Urth B ? Why don't they just concentrate on keeping the one from Urth A alive there, since he is in the identical circumstances until that moment? -- Jeff Wilson - < jwilson at clueland.com > A&M Texarkana Computational Intelligence Lab < http://www.tamut.edu/cil >
An unofficial mirror of a public mailing list · about & removal requests · download the archive · before the list · original archive at urth.net