[elbajo]

Would be curious to hear how something like this happens.

My first guess was that the domain was part of a FB deny list but I don't see why it would. It's still up for grabs https://www.whois.com/whois/di.wang and I can't find any history on https://web.archive.org/web/*/http://di.wang/\\*.

Context is that this is part of an email address and my friend can't send their email anymore.

[pryce]

My guess is that facebook engineer named 'di wang' of which at least one exists[1] was attempting to ensure the blocklist functionality worked in production.

Then again, the employee I found is an engineer in the ads department, so blocklist functionality seems unlikely for him to be working on.

[1] see linkedin. I have removed the link to an employees profile who may or may not be relevant and is not a public figure.

[shadowgovt]

> Then again, the employee I found is an engineer in the ads department, so blocklist functionality seems unlikely for him to be working on

... Unless there's also a blocklist for ads, and someone misconfigured the messenger list to pull that one in also. I've seen similar errors in other companies.

[toyg]

Or maybe somebody in FB blocklist dev carried out a vendetta against such engineer…

[NobodyNada]

Could it be some sort of doxxing filter gone wrong, like when Twitter banned the word "Memphis"? https://www.telegraph.co.uk/technology/2021/03/14/twitter-su...