On Fri, 19 Apr 2013 18:42:22 -0400, "Sea Wasp (Ryk E. Spoor)"
<
sea...@sgeinc.invalid.com> wrote:
>My apologies. I responded without fully reading and comprehending your
>question and made myself look like an ass.
No apologies necessary, and you didn't look like an ass.
I apologize for the snippy reply. My only excuse is that I spent more
than an hour writing a reply to address each point you made, but it
was virtually unreadable (causing a high level of frustration), a
migraine was starting, and I realized our exchange was heading down
the same old road which is futile, often borders on hostility, and has
given me a bad rep. So I deleted everything and wrote something so
terse I couldn't screw up it's meaning.
The 'old road' usually goes like this -- I posit a situation and ask
for help on a specific point. Rather than understanding that I might
know something about the situation I propose and double-checked each
facet I could, people attack the concept of the scene.
I respond with explanations of why their points don't apply, but
obviously I don't write in a comprehensible manner since their reply
ignores what I said, I reply again, etc. etc. etc. ad infinitum ad
nauseam until people say I'm acting like a troll and won't accept any
advice.
Example:
My protagonist is lost and wants to go home. That is her only
motivation.
A secondary character can quickly and safely send the protag home.
Instead of doing that, this character steals clothing from a corpse
and makes the protag wear it, then tells the protag to make a long and
dangerous journey to seek help from a person who can't actually do
anything.
This secondary character is blatantly bigoted (she states that ugly
people are evil). She also likes to instigate trouble (insinuating the
protag murdered a person who died accidentally and taunting the
deceased's only living relative just before sending the protag to
where the relative, now hopping mad, has a great deal of power).
Question: how do I make this secondary character lovable and seemingly
worthy of respect and even awe?
What I'm seeking is someone with the brainstorm: "Have her wear a
beautiful gown, say she's a good witch, and name her Glinda."
What I get often ranges from "it'll never be believable" to "you don't
understand anything about psychology, human interactions, or the
female psyche."
The frustration is so high I'd just quit asking for help if it wasn't
for the fact that there's almost always at least one suggestion which
is a perfect gem, and more than once, someone has had the brainstorm
which solves all my problems.
>On 4/14/13 3:50 PM, Jymesion wrote:
>> What is the minimum length of time, irrelevant of cost, the reads
>> should be kept in case they are needed?
> Minimum time if we're considering legal evidence consequences --
>probably seven years. That's one of the classic "statute of limitations"
>lengths of time. I think that's also the "tax returns" limits.
Thanks! I hadn't actually thought of that angle.
As for taxes, it was a long time ago, but I remember someone being in
trouble because the IRS found errors going back four years, which gave
them the authority to go back another ten.
> A lot of this depends on how much you think it takes to store the data,
>and how much data storage is available. If Moore's Law keeps crankin'
>along, storing all your garbage data for a year becomes trivial
>eventually; you store it all, forever, for $5 a year.
I don't think this could be considered in the same way as normal data
storage. The amount of information is so large it would be like trying
to put the whole Internet on a flash drive.
My thinking on it is this:
You can't just say: an iron atom at location 34,16,26. Without
duplicating the atom's spin, electrons in the proper shell, etc., it
might not interact with neighboring atoms in the same way. A beautiful
crystal of hardened steel might come out of the duplicator as a lumpy
line of dust.
Even if it's mostly the same, it won't be exact. One of the best
things about proper duplication is you can test an item until it
fails, so you know exactly what it can, and can't, do. If even a few
atoms in a piece of steel migrate from one microcrystal to another
because of a coarse duplication, the fracture pattern will change. The
original bolt might withstand 150,000 psi, a duplicate might shatter
at 134,000.
I think, therefore, useful duplication has to be at the quark/lepton
level. This would require taking measurements (x, y, z co-ordinates)
in nanoangstroms. For a duplicator with a 1 cubic meter chamber, that
means three 10^19 numbers, plus an identifier for flavor.
Multiply that by quarks in a proton, multiply that by protons in an
atom, multiply that by the atoms in the chamber.
Complicating matters is that two reads would have to be taken at a
very short interval apart. It is by comparison of the reads that the
particle's vector is determined.
Even with ingenious shortcuts and the best data compression, it's
still an insane amount of information.
I think it'll have to be, at the very least, some sort of holographic
storage.
The media will be essentially free, but I suspect it'll be of
considerable size.