A process can spread on a network by instantiation, an object orientated design method that lets one source class direct many objects. For example, when screen buttons look and act the same, instead of duplicating the code for each, programmers let one class direct all of them. This saves time as they can 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 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 sequentially might give some screens a button but others nothing at all, at any moment. It is better to feed one instruction to every button, then repeat, to keep every screen busy. If a server supports all its instances equally, as their number increases, that support will inevitably weaken.
If quantum instantiation is the same, more photon instances will get fewer up-down instructions so their amplitude will reduce. A quantum wave will then weaken as it spreads, just as a water wave does, as the quantum flux follows Gauss’s law. As the wave spreads to give more instances, each will get fewer vibration instructions, and so vibrate less. Spreading a quantum wave then doesn’t alter its frequency, which depends on wavelength, but its amplitude will reduce as it spreads. But if one server supports all the instances of a photon that spreads on the network, what then is “a photon”?