From: Eugene Leitl (Eugene.Leitl@lrz.uni-muenchen.de)
Date: Tue Jul 10 2001 - 04:51:09 MDT
On Mon, 9 Jul 2001, Adrian Tymes wrote:
> Main differences between uploading and inloading:
> * Uploads typically emphasize an all-at-once shift to some other
> platform, inloads emphasize gradual replacement of the natural with
> the artificial.
Um, no. Uploading describes a framework for many scenarios. Old, but still
authoritative: http://www.ibiblio.org/jstrout/uploading/MUHomePage.html
> * Uploads have potential for radical transformation of self's physical
> representation over short time periods; inloads chain the self to an
That assumes you understand how you're working, and have full access to
the substrate, i.e. a specific scenario.
> architecture very similar to the starting architecture for quite some
> time (at least until inloading replacement is complete). Similarly,
> inloads wait on most of their benefits until a significant number of
> connected neurons are replaced (though merely having a neuron that
> is not as susceptible to age or damage is, itself, a benefit).
I think it is a little to early for a schism into the People's Liberation
Front of Judae, and the other guys. The current term is adequate, and
there's absolutely no point in introducing another one, already contained
in it.
Terminology is important. Please try to contain the namespace bloat.
> * Uploads require at least some knowledge of human cognitive processes
> (software) prior to development; inloads make sure the replacement
Um, no. "Inloading" is a subset of uploading. The canonical "freeze,
slice, scan" approach does not require the understanding of anything but
the wetware low level function.
> neurons (hardware) are 100% emulating the old, and thus do not care
> about the software (except insofar as how, exactly, the software uses
> the hardware, so the hardware *can* be emulated).
I see the schism has already happened.
> * Therefore, inloads are expected to be an easier path to upgraded
> intelligence than uploads.
I doubt it, because "inloads" describes a specific upload scenario.
-- Eugen* Leitl leitl
______________________________________________________________
ICBMTO : N48 10'07'' E011 33'53'' http://www.lrz.de/~ui22204
57F9CFD3: ED90 0433 EB74 E4A9 537F CFF5 86E7 629B 57F9 CFD3
This archive was generated by hypermail 2.1.5 : Sat Nov 02 2002 - 08:08:37 MST