Players claiming to be cursed, and the curse was real!
A very different sort of event that it reminds me of is the old World of Warcraft plague: https://en.wikipedia.org/wiki/Corrupted_Blood_incident
When they added the ability for Kerbals to be killed in Kerbal Space Program, they tripped over a bug where the first Kerbal in the game's engine, Jebediah (the one who dated back to the original introduction of astronauts at all, where only one existed), could not be killed. Because of some of the game logic having gone unmodified from the earlier versions, some operations would cause him to be loaded into the pilot seat and those operations didn't check if he was deceased. As a result, you could lose him on a mission only for him to spontaneously appear at the controls of another mission.
The community responded with fan-art of "Jebediah Kerman, thrillmaster."
When it strikes, it eats you swiftly, and eats you whole. It disassembles your crafts, spaghettifies your crews. No weapon or speech will save you. The Kraken transcends reality - even time travel, reloading from a saved game state, does not always stop the attack.
--
Of course, the Kraken is just a manifestation of unstable physics calculations and a floating point-based coordinate system: as you travel further out, the spacing between two consecutive coordinates gets bigger, until it overwhelms the physics engine and your craft disintegrates. And if you start doing crazy stunts, particularly involving high impulses or very fast rotations, the physics will break even if you're close to coordinate origin, due to rounding errors.
> Somewhere in this outer space, a gruesome death awaited, death and horror of a kind which Man had never encountered until he reached out for inter-stellar space itself. Apparently the light of the suns kept the Dragons away.
[0] https://www.gutenberg.org/files/29614/29614-h/29614-h.htm
What I find interesting is the substantial curiosity and effort people will put towards solving questions in video games, but when asked to solve problems in the game of life that we are embedded in, people often seem to have opposite instincts.
Of course, it wasn't any kind of UI bug or automated moderation. The experience gave me a visceral understanding of what eventual consistency means - a term I also first learned around that time, during internship in an Erlang company, and connected the dots.
I was one of the first people in my social circle to spot the issue, but as it became apparent over a year or two before eventually getting fixed (or at least made less obvious), I ended up giving a very high level intro to distributed databases to quite a few non-tech people, in order to alleviate their concerns about Facebook gremlins.
This and other experiences using and building software systems make me agree with you. Especially for large web platforms, that weird thing you're experiencing could be some nasty form of shadow ban, but if you just noticed it after doing something, then chances are it's just a transient issue with queues or database consistency.