How can a process spread on a network? The proposed way is instantiation, an object orientated design method that lets one source class direct many objects. For example, screen buttons often look and act the same, so instead of duplicating the code for each, programmers define one class to direct all of them. This saves time and lets them change all the buttons of a class in one place. Instantiation works for any screen object, like a pop-up or a drop-down menu, and local differences like color can be a parameter. Computing calls such buttons instances of a source class.
A quantum wave can then be a spreading cloud of instances from a server source 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 sequentially might give some screens a button but others not, at any moment. It is better to feed them all one instruction, then repeat, to keep every screen busy, so if a server supports its instances equally, as their number increases, that support will weaken.
If quantum instantiation is the same, more photon instances will be fed equally but each will get fewer up-down instructions, reducing its amplitude. A quantum wave will then weaken as it spreads, just as a water wave does, because the quantum flux also follows Gauss’s law. As the wave spreads, to create more instances, each will get fewer up-down instructions, which reduces amplitude but not frequency. The frequency of a processing wave depends on its wavelength, while its amplitude depends on how much it spreads. But what then is a photon, if it is just a spreading cloud of instances?