3rd party bulk senders likely know more about mail delivery than you do. Also DMARC aware recipients will treat ~ALL in SPF exactly like -ALl.
731 karma · joined June 6, 2020
Many European countries are forcing DMARC adoption for government infrastructure and it works just fine.
In this case configuration is handled by an unknown entity that you no contractual obligations to you. Don’t do it.
Lack of verbose feedback / delivery errors makes debugging issues in your own really hard, so you might want to contact someone who knows a thing or two about emails for help.
This is bad for IT. Maybe not as dramatic as an existential crisis but it’s certainly a lost opportunity.
My friend's daughter is 10 and she could pass job interview for a junior software developer any day simply because her first PC was running Ubuntu (it’s Arch now).
Cage's material will still get attracted to the black hole and close to the event horizon structural forces exerted by gravity will be hard / impossible to counteract with current materials: https://en.wikipedia.org/wiki/Strength_of_materials
It's almost as if there are good and bad math teachers (in all countries).
It is relevant because this requirement necessarily conflicts with strong e2ee. And since Apple is designing devices for end users that don’t necessarily even know or care what e2ee is, it seems completely reasonable to have defaults that will optimize for the problems that are relevant for the majority of users (losing decide and forgetting your password) while making strong e2ee a few clicks away to those who need it (and understand associated tradeoffs).
2. What’s more important is you can reverse engineer algorithm that’s used locally to compare these hashes. Unlike with cloud-based searches other providers run, this puts significant limitations to what Apple or LEA can do on your phone. E.g. they can’t extract strings from PDF or grep through image metadata or request all images of certain users without knowing what these images would depict in advance. The frequency of hash database updates even if opaque will still provide more insight into what is being searched for compared to current status quo where public has zero insights because all search / aggregation queries are run on the server.
Apple’s system on the other hand provides such guarantees, so I don’t see how it can be compared to these hypothetical rummaging operations.
For comparison, it's pretty obvious that there are certain things in physical realm that citizens shouldn't have. So it would be wrong to claim "my things are mine and no one should be able to inspect them or take away from me, no matter what those things are". Examples for things citizens should not posses: weapons of mass destruction and slaves.
Apple et al argue that CSAM should be digital content that nobody ought to possess. So while you're obviously technically capable of storing it, it shouldn't be legal.
In my book that's a step in the direction of privacy, compared to old status quo.
Even with this on-device CSAM thingy, Apple knows less about you than they did 10 years ago and random staffers at FAANG can't just go and spy on their spouses (the way they could not that long ago).