We have had this same issue. We are migrating from our old ably.io domain to our new domain ably.com. We've been contacting Facebook through public channels, and private channels (our network) for around 7 months, and we're hitting a brick wall. Facebook is touting how they are doing what they can to validate what people are publishing on their platform, yet they incorrectly classify our domain ably.com as "the content doesn't meet our Community Standards" yet won't reclassify, respond, or engage in any way to change that (see https://developers.facebook.com/tools/debug/?q=ably.com). Like Alex from JitBit, Facebook truly is a tiny channel for us, but we have found it has a wider impact for us it stops people sharing links with the domain in it in other Facebook owned media too.
If anyone knows how on earth we can actually get Facebook to respond, I'd be hugely in your debt. This issue has blocked us for 6 months in migrating over our primary traffic from www.ably.io to ably.com.
If anyone knows how on earth we can actually get Facebook to respond, I'd be hugely in your debt. This issue has blocked us for 6 months in migrating over our primary traffic from www.ably.io to ably.com.
Contact me at matt at ably.com