
Back Orifice
I still remember chuckling at the name of the cracking tool against Microsoft BackOffice being called Back Orifice.
When it comes to bork, Microsoft has always been ahead of the game. To be honest, we should have seen this one coming. We at Vulture Central do like our acronyms after all. However, it took veteran Microsoft employee and current Azure Stack HCI customer lead Carmen Crincoli to remind us of the true meaning of bork. BackOffice …
"I wonder what The Muppets are up to now-a-days?"
You can find old episodes of The Muppet Show streaming on demand at Disney+ ...
... However, unfortunately the hand-wringing namby-pamby set have managed to force Disney to graft on an Offensive Content Disclaimer. On the Muppets. Really. You can not make this shit up.
"I think the term BORK in the context of computer fail is based on the chef's phrase."
I've read a 1968 log book from SLAC describing the software keeping an eye on a detector array as being well and truly b0rked. It was hand-written, with a slash through the 0, so there is no mistaking the intent of the author.
"I think it was someone's successful effort to inject a little humour in to a stuffy organisation."
Or, more likely, a useful coincidence. There were a number of Resource Kits emanated from MS, all the way back to the original Windows 1.0 Resource Kit[1]. Even that may have been pre-dated by others for DOS or other products, but the Win 1,0 Resource Kit is the first I ever saw.
[1] IIRC it was a a bunch of libraries, tools and graphics resources for creating Windows based programmes, before they became known as Resource Kits became SDKs.