A process can spread on a network by instantiation, an object orientated design method that lets one source class direct many objects. For example, for many similar screen buttons, instead of duplicating the same code for each, programmers let one class direct them all. This saves time and lets all the buttons of a class be changed in one place. Instantiation works for all screen objects like pop-up or drop-down menus and can set feature parameters like color. Computing calls such objects instances of a source class.
A quantum wave can then be a cloud of instances directed by a server with a frequency parameter. Why then does the wave weaken as it spreads? If a network server instantiates many buttons on different screens, feeding them preferentially might give some screens a complete button but others nothing at all, so it is better to feed one instruction to every button, then repeat, to keep every client busy. A server that supports all its clients equally will then inevitably weaken its support as their number increases.
If quantum servers instantiate the same, more photon instances each get fewer up-down instructions per cycle so their amplitude reduces. Quantum waves then weaken as they spread, just as a water waves do, because the quantum flux follows Gauss’s law. As the wave spreads to give more instances, each gets fewer vibration instructions which reduces its amplitude, but not its frequency which depends on wavelength. But if one server supports all the instances of a photon cloud, what is actually meant by the term photon?