#header-inner {background-position: right !important; width: 100% !important;}


Communication Randezvous & Stationary Relays.

how devices can communicate using directional communication rays, when on move?

... these can use an idea of Stationary Communication Relays, a stationary points in space to contact when needed or neccessary.

Stationary Communication Relay can use a broadcast communication (with communication signal sent in all directions) to 'alert' a device that communication is neccessary.

when we wish to reduce amount of broadcast sources, Stationary Communication Relay can be used as well.


A Space-Coordinated Stitie GRID.

Stitie Machines can form a vast GRID, and function on their own without Space's interference.

When neccessary, however, a Space-Coordinator Machine can fly to a point at a proper coordinates, 'Scan' for network topology at that location & communicate with chosen machines using a Machine-Coordinator interface ... with all security mechanisms as Certificates for example applying.

... what if machines move after scan? there can be a broadcast communication for handling that. replay attacks can be negated by using nonce (a value used once) as a part of encrypted transmission.

... i think there can be many Stitie Space Coordinator machines cooperating or even competing for resources.

Which Machines obey which Coordinator is matter of a proper 'Negotiation', Programming Strategies & Certificates as well.

There's a risk of a brute-force Certificate forging, one of possible threats ... as well as a Machine-Lockdown / DoS attacks.

... i'll leave these issues to the end-user Programmers, however ... after letting them know about.

See also, if You wish or need, ... :
- Stitie Machine 1.1 'Sunsail',
- Stitie Machine 1.2 'Satellite'.


Code's Elements' Visualization & Kabbalah.

... had this an idea for a while, now sharing it to the public.

Mindful Imaging aspect of the Stitie Space's code can present program (LightPoint object graph) in many ways.

One of these ways is showing Qabbalistic elements' composition in the code, perhaps auras as well. we can visualize how elements play, how auras transform, etc ... ;)

... i think that 'Ola AH' Programming Language's compiler should have it done as well.

- there are tools for .class files analysis, which make the task of imaging in the interpreter quite trivial,
- still class trees have to be built, one file's analysis is not enough - more work, but still fairly short due to tools.

see also, if You wish: Stitie Machine 1.2 'Satellite'.


... why Kabbalah (& Qabbalah) are important?

it's because i hold in my perceptions an opinion that they are worthy of allying with them, even at the cost of other markets.

... mostly because of Anti-Terrorism, but also i think that Judaism is intelligent.

... what is the difference between Kabbalah & Qabbalah?

Kabbalah is more Judaism, Qabbalah is more Hermetic.


Proposed elements' visualizations:

Elements & Spirit Symbols of The Golden Dawn.
(colors may differ).

Spirit as represented by above symbol is abstract,
not restricted to a certain group(s) of people.

Aether or Ether - Western Term for Akasa or Spirit.

(This symbol is used in Dragonfly Algorithm's context,
to represent Spirituality as practiced by Western Buddhism for example).


Stitie Machine's Communication Shortcuts.

In a Single Computer System.

This can be done in one of the two ways:
- we can have an Object with references to other Stitie Machines that can be put in the State - this is the most simplistic way.
- we can modify Stitie Machine's Router to keep a data structure with references to Stitie Machines, accessible with a proper Certificate Privileges - this is a design-level solution, better way, i think.

In a GRID.

Same as above, just with references replaced by the network connections, perhaps via dedicated wires or via other ways.

Moving Machines & LightPoint Objects.

In the case of when we wish to keep the reference to a LightPoint Object rather than to Stitie Machine, we can have a reverse-shortcut-communication & notify the Router of the coordinate changes - before & after moving the LightPoint object. In case of movement failure - for example due to privileges lack, it's up to notified Router to decide whether to keep old coordinates or to remove the 'reference' to it.

We might consider moving the same or newly-created the Stitie Machine as well, updating all of the neccessary coordinates & references as well.

There should be 'autowiring' method in the Router or in the Stitie Space, allowing it to connect with other nearby Stitie Machines as neccessity arises as well.

Stitie Space & Stitie Machines should be aware of 'potential machine' coords as well as of 'present machine' coords as well, with Stitie Machines querying Stitie Space if neccessary.

'potential machine' coords - is point where a stitie machine might be present but is not.

'present machine' coords - is point where a stitie machine is present already.

Moveable Stitie Machines should be Stitie Space Aware (in a way at least) & notify Stitie Space after movement ... either by link to it, or with an encrypted broadcast,

Movement method should be smart in case of physical machines moving through space ... not only moving toward the center of coordinates, but also including collision-avoidance.

Part of movement, there should be option to reserve 'destination coordinates' for a given machine to move in, perhaps 'corridor' to it as well.

To manage a large numbers of machines, task coordinator machines & subtask coordinator machines should be used, ... - in a proper amount. These should act as intermediaries between 'leaf-node' machines & a Stitie Space.

'Corridor', as well as as 'destination point' reservation should occur in a 'Coordinator' machine, not in the Stitie Space itself. Coordinator machine can contain Stitie Space in itself, however.

See also, if You wish or need, ... : Stitie Machine 1.1 'Sunsail', Stitie Machine 1.2 'Satellite'.