jogu

The auto updates are actually quite broken and the lead up to this release has been a poorly communicated mess (see https://www.reddit.com/r/backblaze/comments/de1179/macos_610338_manual_vital_upgrade_prompt_lack_of/?utm_source=share&utm_medium=ios_app&utm_name=iossmf ).

I really hope backblaze up their game as a result of this. I really don’t care if my backup app looks nice on high resolution displays or not, but it hugely worries me that they don’t seem to feel it necessary to apply normal engineering practices like issuing change logs or having the app tell  users when auto updating is failing.

(That said, they’re still miles ahead of crashplan - I evaluated crashplan for our company and quickly realised it is a security nightmare we shouldn’t touch with a barge pole.)

mjtomlin said:

Since no one outside of Apple knows exactly how "Sign in with Apple" works anything said or compared is purely conjecture.

It's literally documented on Apple's developer website how it works.

I seriously doubt Apple "copied" OpenID...

See the Apple documentation. Apple return an id_token that is exactly the same format as the one defined by the OpenID Connect standard, right down to the field names. There's no reason you'd do that unless you were basing your tech on OpenID Connect.

They are very capable of coming up with their own implementation even if some of things happen to "appear" similar. Anyone who's every designed anything knows there's a huge difference between implementation and appearance.

They are, but if they want it to be interoperable then they need to follow existing standards (and they do seem to want this, so that it's easy for third party website backends to support sign in with apple; otherwise as you say they would have invented something completely new).

OpenID obviously has an issue with Apple (probably not joining their group), otherwise, what would they care? This reaction reminds me a lot of CurrentC.

As long as we have an option that is NOT Google or Facebook, (or any group supported by either) count me in!

OpenID's issue is with Apple's implementation being incomplete and not including the mitigations for some known security/privacy issues. This is because the very goal of the OpenID Foundation is to promote interoperable implementation. That's why they make testing tools available for free & open source, and why all the standards are 100% free to read / implement / use. I'm guessing you didn't read the link I shared, or had trouble understanding it. Here it is again: https://bitbucket.org/openid/connect/src/default/How-Sign-in-with-Apple-differs-from-OpenID-Connect.md

 I 100% agree that it's brilliant Apple are doing SIWA - I'm massively looking forward to as many apps as possible supporting SIWA.