Error'd: Neither Here nor There

... or maybe I should have said both here and there?

The Beast in Black has an equivocal fuel system."Apparently, the propane level in my storage tank just went quantum, and even the act of observing the level has not collapsed the superposition of more propane and less propane. I KNEW that the Copenhagen Interpretation couldn't be objectively correct."

Darren thinks YouTube can't count, complaining "I was checking YouTube Studio to see how my videos were doing (not great was the answer), but when I put them in descending order of views it would seem that YouTube is working off a different interpretation of how number work." I'm not sure whether I agree or not.

"The News from GitLab I was waiting for :-D" reports Christian L.

"Daylight Saving does strange things to our weather," observes an anonymous ned."The clocks go forwards tonight. The temperature drops and the wind gets interesting."

"I guess they should have used /* */. Or maybe //. Could it be --? Or would # have impounded the text?" speculated B.J.H.Ironically, B.J.'s previous attempt failed with a 500 error,which I insist is always a server bug. B.J. speculated itwas because his proposed subject (<!-- You can't read this! -->)provoked a parse error."

[Advertisement] Keep the plebs out of prod. Restrict NuGet feed privileges with ProGet. Learn more.