The lesson learnt from this fiasco is that CF can't trust its upstream ISPs, so tunneling traffic over to another ISP in a different geo adds additional overhead without actually solving the problem.
The right approach to fix upstream MITM is to drop http+https mix and match mode.
So, Facebook says they "fixed" the issue of showing notifications to people outside India -- How exactly would they fix this? If an email is delivered to TRAI's mailbox, it stays delivered, doesn't it?
It is for this reason Elasticsearch 1.x advocates using 'copy_to' on mapping attributes that may encounter collision. Elasticsearch 2.x explicitly throws exception whenever it detects mapping collision.
Correct. There was a time, pre-acquisition, when some separate management-console bits were not open source, but nobody cared about those bits anyway and now they're long gone. The "GlusterFS" file system part, which is the part everyone except one misguided CEO (now at Docker) cared about, has always been completely open source.
More like "Both companies didn't immediately respond to requests for comment. Its 8:30PM and no one's taking my calls or responding to my emails, but we're an online publication and want our content to go viral and get maximum eyeballs, so we'll run this story anyway."
