Transaction revocation within transaction malleability via anyone-can-revoke hashlocks

The conversation is about revocation keys and their usage for security purposes in the Lightning Network. The idea of publishing revocation keys with conditions is discussed, which would allow for immediate revocation if online or for anyone to poach if certain conditions are met. It is noted that using SegWit is a better option. Additionally, the concept of trusted watchers knowing the revocation keys is mentioned, specifically A sharing the key to spend B's old commitment transactions. Terminology is clarified in the discussion.