I too would like more clarity on the original incident that prompted the concurrent thread re B!B!, but in the meantime here is a happy opportunity: