starfox64_
Joined 10 years ago
Joined 10 years ago
I would have hoped for Boeing to add a warning system in the case of dual input, like in Airbus aircrafts, but it seems they did the bare minimum here. Simple warnings were added to the pilot hanbook that basically amount to "don't apply opposite inputs".
It seems to also have learned from one of Extended Certificate's shortcomings by relying on trademark instead of company name. I actually wish something similar was created to replace EV certificates as it's easier than ever to perform phishing attacks now that everyone and their grandmas has a DV certificate on their site (which is a good thing).
More like a pre-emptive measure to charge customers more for access to Teams
It's unlikely to happen but still possible and it has brought down some of our parallel worker pool because once you have a collision, you are bound to keep generating the same id sequence until you restart your whole process to randomize the counter again.
However the fact that you need to go to every domain provider to get your template manually approved makes this completely useless, what even is the point? This barely adds any security too since I can just use each provider's official API and create whatever records I want this way.
It's really sad because the protocol is designed for auto discovery but then does a 180 by having this manual step.
They had just added SMS notifications to production but to my horror left some test code that would text you "Hey motherf**r" every time you would change your phone number.
To this day I still wonder how many people got that text.