https://youtu.be/OK4atxPn270

They say this is pretty common, it's nothing to worry about, and they have some theories as to what causes it that may unravel some more mysteries of how the human brain processes sounds and sometimes visual effects. This fellow explains it pretty well.

Only those highly trained in both electronics and electricity can understand.

I’ve heard of people hearing unexplained noises, but they are always based on something.  So my older relative once heard a noise that sounded like someone was inside, due to the way sound carries, it was actually coming from the next door neighbor.  They crashed something. By the time the sound travelled it sounded like something dropped in their house.

The double post isn’t caused by Delphi, it happens when you click post again while it’s cycling.  If you don’t see the post appear right away, wait a while and you will.  I’d forgotten but this was a big issue a while back.  If you have made a huge post and worry you will lose it, highlight it and copy and either save it or hold it in your cache until the original posts. 

That would explain it then, because sometimes my internet connection lags really, really badly with a lot of dropped packets. Sometimes the browser stops responding for, say, 5 to 10 minutes straight, while it "counts out" of some horribly inefficient bit of code. It's nearly impossible to tell if it is hung internally or if it's retrying and retrying packets, because, oh, it's become non-responsive.

So you press a button, and the button doesn't seem to respond at all like the browser has frozen or hung, maybe it actually isn't polling the buttons while it's off running who knows what, maybe attempting to process some Javascript in another tab entirely, or something else stole the focus but then has hung, so a click really didn't even go to that tab or even the browser at all.

After 2 to 10 minutes, suddenly the browser starts to act as if it has accepted focus again and awakened from whatever grand mal seizure it was in. So one clicks on it and this time it accepts the mouse click. But it, opaquely hidden from the user, apparently queued the first not visibly acknowledged click, and the second one made it process the queue of inputs all in a burst.

It's hard to believe that with a million times the computation power we used to land on the moon, that anything should just hang in a nonresponsive state for 10 minutes. But bloatware, and inefficient code with a lack of any network progress tattletales built in, is not surprising these days.

40 years ago we didn't have such issues.

I had an unexplained humming noise when I first moved out here about 37 years ago, that took weeks to figure out. What it turned out to be was, a train going down the tracks more than 7 miles away. At a certain speed, infrasound would be conducted through the earth, which then would cause the structure to resonate at a higher odd harmonic, like how a frequency multiplier circuit operates in an older UHF radio transmitter, where the carrier needs to be several times higher frequency than any quartz crystal can possibly oscillate.

So human ears can't hear the fundamental frequency, but each peak would cause nonlinear coupling into the trailer house structure when I had the little trailer. So let's say that the actual sound from the train was 5 hertz. The 5th harmonic would be 25 hz, the 7th would be 35 hz, and the 9th would be 45 hz, which would be audible but a deep humming.

Step outside into the open and you'd hear nothing at all. In the days long before Google it took a lot of detective work to figure out what was happening.

They are going to ask tech anyway.

Maybe a bug can be found, or possibly a fix that doesn't break something else. It can take 3 minutes for the complete edit screen to fully load. Not always but it's due to slow and laggy connections.