On the other hand, I don't know anyone with an @some-microsoft-property email address, so I don't know whether I'll be having trouble sending things there. I can reach Gmail and Yahoo (and after getting my own /64, Comcast) without trouble, though.
EDIT: Hmmm, mail-test.com seems to be a parked domain.
Apparently eShares is having the same problem. Shareholders with Microsoft-affiliated email addresses couldn't accept certificates.
Client host blocked using FBLW15; To request removal from this list please forward this message to [email protected] (in reply to RCPT TO command)
I did as it said and forwarded the message to that address, and got an automated reply and my IP removed a few days later.
Maybe your situation is different since you're not getting a bounce message, but try emailing that address if you haven't already.
If the most popular sites bring up the click-to-play prompt, users will get frustrated quickly or habitually click.
Just to be clear; I'm in favor of ditching the include Flash by default in Chrome, but I'm not in favor of them making exceptions for certain sites. That's just horse shit.
That's because most of the tech world in the 2010s understands the difference.
Seriously, Google is as bad as every other tech company, but for some reason, when they do shit like this, people tend to over look it (not sure if because a lot of folks directly or indirectly have their livelihoods connected to Google properties or what not)
(I sometimes worry I come across as a Google apologist. I suppose I am in a devil's advocate sense. It's not that I think Google is a shining beacon of decency. It's just that the quality of anti-Google thinking on HN is so low I find it difficult to let it pass. If you could all step up your game somewhat then I can stop chiming in).
It's an imperfect solution to be sure. But in these situations (officially ending support for WinXP/IE6, ending support for some plugin, etc) there is no perfect one. There needs to be some motivation to get users and websites to move on from Flash but there's also consideration for breaking commonly used services.
Aside from YouTube, I don't see any other Google properties in the list.
https://groups.google.com/a/chromium.org/d/msg/chromium-dev/...
My point is that they are building html5 versions of many of their sites (like Youtube, probably the biggest site supporting html5). Why would they care about serving the old flash versions of those sites to their html5 browser?
I agree that they have not moved all of their properties in lockstep over to html5. But I think Youtube supporting html5 provides more information about their motivations than the number of domains they are putting on the default whitelist.