This. Yev, if you are not in the upper management chain of Backblaze, please show mnw21cam's message to someone who is. The problem is not that there was a li

This. Yev, if you are not in the upper management chain of Backblaze, please show mnw21cam's message to someone who is. The problem is not that there was a little bug which caused the Facebook tracker to get a few little pieces of information it shouldn't have. The problem is that Backblaze failed to understand how to distinguish appropriate and inappropriate uses of third-party trackers for signed-in users on a security-critical application. The Facebook pixel should never have been there at all. It shouldn't even have been considered. It should've been an absolute no-brainer that Facebook has no business being on secure pages on a critical infrastructure service for paying customers. The fact that the pixel even showed up at all on a logged in page represents a breach of trust for customers and casts doubt on Backblaze's competence in handling security issues. This warrants a serious reply from the CEO, not a copy-pasted meaningless reassurance.