When I put down my mug 18 months ago, I promised I'd stick around, and I did. I've been keeping a distant eye on CR and meta, while remaining in our Rubberducking dev chat, and monitoring vba posts on both Code Review and Stack Overflow.
Seeing rolfl's resignation and the bleeding of several SE communities' moderator teams over the recent events, and since elected moderators that stepped down in good terms can easily be reinstated without putting too much strain on the SE community team, I offered to step back up and patch the gaping hole left in our moderator team, which has been stretched thin with Simon's departure a couple of months ago.
I do not, in any way, disagree or otherwise disapprove of rolfl's handling of the situation (despite how many times he'd tell me to "just blame the monkey"!). On the other hand, elections take a while to arrange, and the SE community team has plenty on their plate at the moment: my reinstatement as a moderator is likely not a complete solution to what's happening with real-life events in the Code Review moderator team - we will need a bit of time to assess whether an election should be held, but with me getting back on the moderator team now, we get to take urgency out of the equation, and let the dust settle a bit on the SE crisis while we determine whether we're all comfortable with the workload.
I can't just sit here and watch CR's moderator team struggle (thanks, monkey!) while the SE Community team is in full-on crisis mode.
So, I'm back, you'll be seeing me around much more often than in the past 18 months, and you can blame the monkey for that =)
Note: "blame the monkey" is kind of a meme among the CR moderator team, since the 2015 elections... I have absolute, complete and total respect for rolfl, and this blame-game is intended to be nothing more than harmless sarcasm.