cbi
The Force is Strong With This One
Hello,
this is an idea that was large "time" into my mind.
It arises from what the C's have mention that time isn't linear, but we percieve it in this way at density levels 1, 2 and 3; on next densities we are informed that it change. In the same way, we are told that 4D.STS usually goes back on time to impact on some action in order to change a future event. In some sessions, when C's are asked about a particullary event in the future, it seems that, given their omniscient ability, they analize the "possible futures" of the situation and then formulate a probabilistic answer, so to say, based on the weight of potential futures about they are asked.
Bridging the gap, this is really interesting from the point of view of a debugging scenario on computer programming. The process of debugging consists on analize a piece of code and watch how variables and methods (functions) are updated and invoked respectively. In debug mode it is possible to change variables, stop the process flow or make forced forks in a no-linear way, something that in natural execution scope will be impossible.
Furthermore, execution mode is the common and natural way which programs and applications (the operative system processes or tasks) run on a computer hardware: they have a starting point, a process and stopping point. But, in debug mode, which consists in find and clean errors, it is possible to stop the natural flow and alter variables or functions calls, and setting the Next Statement Pointer (the position in which will restart the program execution) in an artificial-way; of course, this isn't perceive by a program (although there are some technics on defensive programming to detect discrepancies on real time systems)... that's mean that alterations could be seen as occurring in zero-time.
In order to enrich this point of view there is an article at Montalk about Timeline Dynamics which tries to explain how 4D.STS could alter deeds in the past so to hack the present or the future, making unconcious widgets which we aren't aware of.
An execution mode as our time/space continuum and a debug mode capable on 4th density and beyond, could explain some concepts about time. There also another technical concepts as wedges that could appears as free will violation in order to insert malicious code into a memory block, one common way to inject a virus on operating systems.
If anyone interested, I could expand on it using a simple debug example on VBA (like Excel script) to view it in a practice way.
Best,
cbi
this is an idea that was large "time" into my mind.
It arises from what the C's have mention that time isn't linear, but we percieve it in this way at density levels 1, 2 and 3; on next densities we are informed that it change. In the same way, we are told that 4D.STS usually goes back on time to impact on some action in order to change a future event. In some sessions, when C's are asked about a particullary event in the future, it seems that, given their omniscient ability, they analize the "possible futures" of the situation and then formulate a probabilistic answer, so to say, based on the weight of potential futures about they are asked.
Bridging the gap, this is really interesting from the point of view of a debugging scenario on computer programming. The process of debugging consists on analize a piece of code and watch how variables and methods (functions) are updated and invoked respectively. In debug mode it is possible to change variables, stop the process flow or make forced forks in a no-linear way, something that in natural execution scope will be impossible.
Furthermore, execution mode is the common and natural way which programs and applications (the operative system processes or tasks) run on a computer hardware: they have a starting point, a process and stopping point. But, in debug mode, which consists in find and clean errors, it is possible to stop the natural flow and alter variables or functions calls, and setting the Next Statement Pointer (the position in which will restart the program execution) in an artificial-way; of course, this isn't perceive by a program (although there are some technics on defensive programming to detect discrepancies on real time systems)... that's mean that alterations could be seen as occurring in zero-time.
In order to enrich this point of view there is an article at Montalk about Timeline Dynamics which tries to explain how 4D.STS could alter deeds in the past so to hack the present or the future, making unconcious widgets which we aren't aware of.
An execution mode as our time/space continuum and a debug mode capable on 4th density and beyond, could explain some concepts about time. There also another technical concepts as wedges that could appears as free will violation in order to insert malicious code into a memory block, one common way to inject a virus on operating systems.
If anyone interested, I could expand on it using a simple debug example on VBA (like Excel script) to view it in a practice way.
Best,
cbi
