Some more satire:
                           _COPIES_

     You've always got to handle copies. ByTes will copy. Obsessive
duplication is a ByTe characteristic. Maybe all that engrams are is
excessive copying.

COPY:                               Posters on usenet (& their BTs) may
                                    obsessively copy the postings of
                                    others 'netters. Therefore you can
                                    find it seems that the geek who
                                    just left is still there because
                                    there is a posting left. Spot the
                                    fact that someone else copied it. 
                                    it usually goes. (When it has
                                    expired or exceeded the BI and gets
                                    canceled as spam)
                                    

CROSS-POSTING:                      When a number of ByTes and spammers
                                    are restimulated or awoken, each
                                    can start making copies of each
                                    other's pictures and copies of the
                                    copies - called cross-posting.
                                    (Mostly MMF-schemes and other spam)
                                    

After a ByTe leaves, some other ByTe may copy it on the internet.
Just run.

Thetans on the 'net may obsessively copy the postings & websites of
other 'netters.  Therefore you can find it seems that the thetan
who just left is still there because there is a website left.
Spot the fact that someone else copied it and it usually goes on.

Be Three feet in back of your monitor. Whatever you are looking at,
copy it a dozen times, put it on your HD. Find the two back corners
of the keyboard and hold onto them without thinking for two minutes.

     Misconception of identity. Thetan X thinks he was logged in to
"woof.com" (host) - but actually he's copying the GIF of somebody who
uploaded to "woof.com". He hangs up on the misconcption of identity
(thinks he's the other thetan), and misconception of event (thinks he
was implanted when he wasn't).

     The 3 - 10 days to expire rule; it's not the article that
was posted that takes 3 - 10 days to expire, it takes 3 -
10 days for all the copies and copying to fade out.

     "Enter" is also a heavy button. You get a lot of copying of
whatever. So you handle the original, then copies - somebody copying
what was run.

     What you are really handling is a cross-influence of life, and
the idea that "A" can assume the characteristics of "B". So now in
trying to audit "A", you're auditing "B", but he's not there. It's
the general cross-influence - somebody copies a JPG, somebody
copies a copy. It's all on the basis of the misconception that "All
is one" and they can't tell whose JPG is whose, or whose GIF
is whose. You're basically trying to untangle this mish-mash. And
what's amazing is that there are as many life netizens as there are -
there are lots of them.

     Because of the number of netizens it can get quite complex. It all
starts out originally with a hacker obsessively copying the virtual
universe around him. And when he starts doing that, he sets himself up
for copying other nerds' computergames and then he gets pretty confused
And the basis of it all is _misconception_ . First and foremost is
_misconception_of_identity_ . That's actually what the RD is structured
on (it's not structured on "he's got ByTes, so blow off the ByTes") it's
structured on the disentanglement of confusions. This RD handles the
entanglement of the ByTes.

     It is essential to check for and handle copies. This is done _by_
_spotting_the_fact_that_someone_else_copied_it_ and it usually goes. If
not, you could _find_the_ByTe_or_cluster_who_is_copying_what_was_just_run_
and blow it off

     Grinding an incident on Dianetics or NED will result in some ByTes
run past erasure, so they have to hack it again to run. Or they
never got to VisualBasic and C++ because the auditor never asked for
E/Beg or E/Sim, and were left hanging incomplete on the chain. And
other ByTes will copy all this obsessively.

     Copies. The auditor asks "copy?" and if reading has any
copies spotted and blown. Often the ByTe or cluster who originally ran
the item will have blown, leaving ByTes or clusters who copied the
auditing or copied the overrun, etc. And don't nag the critic for
copies or you'll start a flame-war and some other ByTe copying now.

When very bad such a session can itself have been a cluster
making incident and is the _latest_mutual_incident_for_those_BTs_and_
_clusters_ stirred up in that session. There will have been
considerable cross-posting. Do not attempt to R3R or R3Ra such a
session. Handle it as described above under Repairing Past Posting.
Repeat those steps until all ByTes and clusters have been blown off that
session.

The pc was left hung up in things that did read, but weren't taken up,
and when things that didn't read are taken up, it will stir up dormant
ByTes and clusters, and misowership and misidentification occurs. Add
to that cross-copying of Nudy pictures and you get a mess that can
recoil very heavily against the Pre-OT's body, dangerously so.
(In such a case hit Ctrl-Alt-Delete or push the reset button to reboot)

     A Byte who think he is a picture; (some ByTes will mock up or
become whatever is suggested - hence you get a recurrency of grafix
due to copying).

     Most commonly drugs have shown up on NUTcases as _either_
_cluster-making_incidents_ , or on individual _ByTes_being_the_drug_ or
affected by the drug, or copying other ByTe or cluster GIFs of
drugs.