PDA

View Full Version : "psi zip files"


miri
12-17-2005, 07:28 PM
Basicly one creates a deacent density Psi-ball and places information into the psi-ball like programming a how-to article into the thing, It's best if your good at programming and the thing you're zipping into the ball. Be sure to tell it to "run" the program once activated by the recipiant, or it's just a ball of subjective, and quite uselss, information.


An example is to think of a cloaking shield, once you have the psi-ball ready, and how it works and is made. Then stuff that information into the psi-ball as best you can, this takes some skill, and then send it to the recipiant. the recipiant then pulls the construct into themselves and let the program "run" if done properly you could make nearly anything with this method, from an "attack-in-a-can" to a highly advanced shield.


This is ideal to protect those of lesser skill, such as children or the newly awakened, whom are sensitve enough to run the program and to be harmed by one seeking to harm them. I've experimented with these a fair deal and don't think that someone should do these unless their atleast intermediate at programing or skilled in what they're sending.


Note: With proper programing and storage the recipiant can "save" the program and run it if it becomes neccasary. Also screwing up the programing can lead to problems, probably a two on the psionic danger scale for a shiled that you mess up, but if you screw up something more dangerous (like a bomb program) you could cause significant harm to the recipiant, and so I encourage all readers to practice this (at least at first) with someone skilled enough to fend off or cancel out whatever it is they're sending them.

Please use this type of construct wisely.

Vernand
12-18-2005, 04:33 AM
Just a few questions...

You have included a termination feature in this construct, haven't you? Or at least a termination date for the construct, so it has no chance to settle in any great degree?

Personally, if something like this is used, I'd affix some termination code to destroy the construct on a weekly/fortnightly basis. It'd be a pain in the ass to keep renewing it... But I'd be fairly wary of keeping any type of construct actually inside someone for extended periods of time.
That leaves a lot of room for potential disaster.

I'd also advise against giving any construct like this, the ability to think for itself and/or the ability to learn from it's environment.

miri
12-18-2005, 05:06 AM
I'll address your questions in order

1.) YES it's quite important. However, with proper programming "settling in" isn't a problem.

2.) By storing the construct as a memory that isn't a problem. However, stored as a construct I'd say 48hrs. is the limit. Keep in mind, this is a compact version of the process of making the desired reasult, in simpler terms: a program. This only starts as a construct, the information is what matters.

3.) Thinking & learning are not required for such a construct. So, I agree.

alphaomni
07-19-2007, 03:42 PM
this is currently the technique i use for programming see i mix different psi "zip files"

Bacus23
08-21-2007, 11:20 PM
Good,

But kind of complicated

Thanks for Sharing the idea

~Bacus~