In Grammerly’s Privacy Policy[0], it states as part of information they collect:
“User Content. This consists of all text, documents, or other content or information uploaded, entered, or otherwise transmitted by you in connection with your use of the Services and/or Software.”
and yet they don’t define this as a keylogger. I do understand keyloggers record everything a user types and Grammerly claims to not read “sensitive fields”.
I have never even noticed the ability to log in with my AppleID (as opposed to local authentication), but GP is arguing that Apple actively makes it difficult to avoid doing so. Something about that is wildly incongruent with my own personal experience and I am truly, genuinely confused.
I will acknowledge my language was not as precise as it could have been, but I did not say that Apple is actively trying to be difficult or does this in a way that is unclear to all audiences. They definitely do a heck of a lot better than Microsoft, who I believe has removed the local login option from Windows 11 Home.
However, the commenter I responded to did not realize this. Likewise, most of the non-technical Apple users that I encounter in my work make the same incorrect assumptions. I probably overcorrect a bit here, but I’ve learned that it helps to to validate the experience of the person I’m trying to educate.
To be more precise in my initial statement, I don’t think Apple makes this part of their interface as clear as it could be (or should be), and I don’t think they provide the average user with the information to understand the implications of using Apple credentials to sign into their device. I don’t assume that this is malicious. I’m sure they are driven some by benefits to the company, but I also suspect they think that this makes life easier for their users. There may be some truth to that, but I think it’s a poor default.
I work with small business owners and employees in the health care field (and teach as a University adjunct). At least in the health care context, there are compliance implications associated with these features (something that Apple Support and Genius’s often fail to understand as well).
In terms of the interface, when I’m working with a developer or tech worker, I consider the first-time setup and system preferences UI to be good enough. But I don’t think that’s true when it comes to a therapist, office manager, non-profit director, or even the majority of my undergraduate informatics students.
On a separate note, I do have thick of enough skin not to be bothered by this response, but I hope you consider some of the replies regarding the tone. In this type of forum, reframing that bewilderment as curiosity will be much better received and help you avoid invalid assumptions about your intent!
Being condescending is not nice, but some people have it hardwired as part of their personalities. For example, people who suffer from Narcissistic Personality Disorder.
One important decision argument against AWS SES is their policy to keep bounce rate below 5% (account put under review, if unresolevd until end of month, will be suspended, with hard limit of 10%) [1] compared to least strict Postmark's bounce rate of 10% [2].
Sometimes for SAAS products with a huge userbase or freemium pricing model is super difficult to keep the bounce rate so low for transactional emails.
Policy like this is meant to protect sender reputation, not just provider IP pool. High hard bounce rate lowers your inboxing in the long term. If your bounce rate is consistently above 5% consider verifying all new emails before sending them an email > https://www.bigmailer.io/blog/email-verification-service-pro...
Natural email decay rate is 2-3% per month so the goal is to stay close to this range, but the lower the better.
