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.
You can deploy production workloads to spot instances, just make sure you have the rest of your infrastructure setup to handle the spot terminations. Excluding spot instances from the discussion, for any robust use case your infrastructure should be able to handle a single point of failure anywhere. See https://netflix.github.io/chaosmonkey/
Over COVID I couldn't wargame with friends in person, so I started an N scale railroad to fill the hobby void as they share a lot. Also it was fun doing all the automation etc as mentioned in other comments there. I've sold the railroad off since as I started wargaming again though.
My email is <first initial><last name>. I also have the same first initial as my father, sometimes I get email intended for him. Fortunately our last name is unusual so that's about the extent of it.
I imagine you avoid Google because you don't want to get locked into their centralized closed source ecosystem and don't want them to track your entire online presence.
So I'm surprised to see you say email should be avoided, as a completely open decentralized communication protocol.
Your stances on these two topics just seem to be in contrast with each other, would you care to elaborate?
It unfortunately would probably only do the opposite as this validation occurs during the SMTP transaction when the message is delivered to the server.
Going back after and saying you don't exist is like answering the phone and going "nobody is home".
Edit: I suppose this ghost setting could be used for future delivery attempts though. Perhaps this is what you meant originally.