This situation is not new, blocks get orphan constantly
This is not what happened. Orphaned blocks are valid blocks, they just belong on a less-worked chain and are therefore ignored.
What really happened is this: the developer was trying to mine a block which was invalid, because of ordering. According to
this Twitter post, the developer included TX A that spends an UTXO from a TX B which was included
after A. That's invalid from a protocol perspective.
orphans are the child(next block) of a invalid parent.. where when the parent get rejected the child is orphans and lost to society too
mara did successfully (not try) to mine a block.. but it happen to not fit the rules so was rejected after it was broadcast to the network.. and there was no network drama because it disapeared as quickly as it was seen..
its not the first time this has happened and has not caused any network issues.. its a non news event that is just a point of interest for other pools to take note of to learn what not to do to ensure they too dont have their blocks rejected.. to the rest of us it was a "nothing happened" non event with no problems caused to the network