Also Canadian. I don't often see "pint" on the menu, usually something like "16oz." Evidently restaurateurs and bar owners are wise to the law. Though I am pleased when I see "20oz" on the menu!
I kind of understand the logic by not serving 20oz and saying "pint". Customers might avoid a place because their "pints are more expensive", when in reality that place is also serving them 4oz of extra beer. A bit like the classic 1/3 lb cheeseburger being "smaller"[1].
Annoyingly, I do find that servers will often refer to their larger size beer as "pint" regardless of whatever the menu says.
Much more sophisticated and reliable than Xfinity.
Good datacenters have redundant and physically separated power and communication from different providers.
Also, in case something catastrophic happens at one datacenter, the author mentions they are peered to another datacenter in a different country, as another layer of redundancy. Cloudflare handles their ingress, so such a catastrophic event wouldn't likely to be noticed by their customers.
SPF alignment ensures the MAIL FROM domain matches the From header.
DKIM alignment ensures the From header matches the domain in the DKIM signature header.
In the DMARC policy, you can set both adkim=s and aspf=s.
Google owns and manages all of this, so they can send emails with a google.com MAIL FROM, a google.com header, and signed with a google.com DKIM key. And they could do likewise with gmail.com emails.
I'm not clear on why this isn't practical, perhaps there is something I'm missing though? I would appreciate your viewpoint.
They probably sent it from gmail which would pass the SPF check (google.com and gmail.com have the same SPF).
They wouldn't have it signed to pass DKIM, but google doesn't use strict alignment checking so to pass DMARC either SPF or DKIM are acceptable.