News for hackers. Stuff that matters.
Re:Face ID and Touch ID for the Web by ogre_codes on Monday October 19, 2020 @04:35PM (#24830711)
As a user I would prefer no account in most cases. As a distant second, I would prefer the convenience, security, and privacy of Sign in with Apple over Google, Facebook, or the headache of managing yet another web account.

As a developer, I use my preferences as a user to steer my choices, but recognize that the world doesn't revolve around Apple so would allow other options.

> Having saw Epic's developer account t...

Since I have zero need to deliberately violate Apple's App Story policy, I don't worry about this overmuch.

Re:Face ID and Touch ID for the Web by simonw on Monday October 19, 2020 @04:51PM (#24830874)
> Since I have zero need to deliberately violate Apple's App Story policy, I don't worry about this overmuch.

That may be true today, but their policies are a moving target. Who knows what they'll be like in a year's time?

Re:Face ID and Touch ID for the Web by ogre_codes on Monday October 19, 2020 @05:44PM (#24831373)
> That may be true today, but their policies are a moving target. Who knows what they'll be like in a year's time?

Likewise Google, Facebook, or any site/ API that a developer deals with on a daily basis.

I wouldn’t bet my company on any sign in with _____ service. I just feel the trade-offs with Apple’s sign in versus Google/ Facebook to be less bad. With any of the services, I might do something that causes me issues down the road. With Apple at least I’m not selling out my users immediately.

Re:Face ID and Touch ID for the Web by variaga on Monday October 19, 2020 @07:12PM (#24832096)
This is why (as a customer) I always prefer "yet another web account" vs. "sign-in with ____" - yes, it's a hassle to manage a different account for every different thing I use (although not much of one with a decent password manager), but I get the advantage of not risking losing access to _everything_ because <list of all the things that might go wrong with a sign-on provider>.

Single-sign-on means single point of failure.

Re:Face ID and Touch ID for the Web by derefr on Monday October 19, 2020 @09:11PM (#24833032)
Is that still true when those accounts are literally just backend-side caches of your shipping+billing address and credit card details?

I had to create an "account" to order a pizza. That account does nothing other than to make ordering pizzas slightly faster. I would be literally not inconvenienced at all if I had to input all that information for each order (because AutoFill.) I would also be literally not inconvenienced in the slightest if I lost access to that account and had to create another one.

To me, that's the type of "account" for which "Sign In With Apple" is a perfect solution. The type of account where it's only the provider insisting on having an account in the first place, and you would be get on just fine without one if they'd let you.

(Or, for an even more annoying example: web forums that you have to "create an account" for to read certain posts, or download attachments on those posts. Thanks for making me take five minutes to verify my email just so I can click a link on a page!)

Re:Face ID and Touch ID for the Web by ogre_codes on Monday October 19, 2020 @11:00PM (#24833550)
I suppose it depends entirely on what the account is securing.

My bank? Needs to be pretty independent of everything else.

Some random web store or something like Kickstarter? The only reason I care about those accounts is to track orders or for the convenience of not having to re-enter credit card info. The risk of losing my Apple account because ??? and dealing with recreating those accounts is negligible. In many cases I just use guest login for exactly that reason.

The convenience accounts are the ones I might use Sign in with Apple for. The bank? Not so much. But I won't trust Google or Facebook with even the convenience accounts.

I would also use something like this Touch ID on the web feature for 2FA, particularly if the only other options are SMS or email.

Re:Face ID and Touch ID for the Web by stickfigure on Tuesday October 20, 2020 @12:51AM (#24834028)
> I wouldn’t bet my company on any sign in with _____ service.

With Google Sign-In, you get an email address. If push comes to shove, you rip out the Google code and email everyone a traditional password.

Re:Face ID and Touch ID for the Web by mushufasa on Monday October 19, 2020 @05:15PM (#24831104)
You could say that about anything -- nothing is completely static -- but it's worth mentioning that Apple vs. Epic is a counterexample; Epic wants apple to change their policies (lower than 30% cut) while Apple wants to maintain the same structure since the inception of their app store.
Re:Face ID and Touch ID for the Web by throwaway894345 on Monday October 19, 2020 @05:54PM (#24831472)
> You could say that about anything -- nothing is completely static

1. Contracts are a thing. You can draft a contract with your vendor that guarantees certain terms for a certain duration.

2. You should be wary of wandering into commitments (including de facto commitments e.g. "vendor lock-in")--there are plenty of good reasons to do so, but one should make sure to properly consider the cost.

The problem is that doing business with Apple can make or break a company--companies can scarcely afford not to do business with Apple. I'm not an economist, but this seems pretty monopolistic (which isn't to say Apple should be broken up, but perhaps more tightly regulated).

Re:Face ID and Touch ID for the Web by ogre_codes on Monday October 19, 2020 @06:31PM (#24831754)
It is more of an monopsony[1] than a monopoly. If you are looking to buy a smartphone there are still options. If you are looking to sell software for smart phones, Apple is by far the most lucrative platform and they have a lock on publishing software for iOS. It is very difficult in the US to survive as a software developer for Android only.

The anti-trust frameworks in the US are based largely on monopolies and there is little in the way of legal precedence for protecting sellers in a monopsony market. If Epic wins their legal battle, it will likely set precedence for later cases.

Google and Facebook are also largely in weird legal ground. They have more or less exclusive access to large networks of users which is hugely disruptive to the advertising market.

[1] A monopoly is a market where there is only one provider. A monopsony is a market where there is only one buyer.

Re:Face ID and Touch ID for the Web by throwaway894345 on Monday October 19, 2020 @08:10PM (#24832523)
Perhaps I should have said “anti-competitive”. As you note, it’s very difficult to survive as an app developer on other platforms, and that’s bad for users ultimately.

I would like to see the US crack down on anti-competitive behavior in general, but especially in cases where companies are deriving value by gate-keeping some large network. To this effect, I think Apple is a relatively minor problem compared to social media networks. Consumers have no meaningful choice (hopefully I don’t need to elaborate on why Facebook vs Twitter is a false choice) and it allows social media companies to get away with all kinds of awful behavior, but especially the ability to steer the course of democracy (by determining at scale who is exposed to which ideas and at what potency) and then selling that as a service to the highest bidder or even serving as an attack vector for other states to steer our democracy (or other democracies for that matter). A monopoly over the flow of speech is intolerable for a democracy, and at least in America where conservatives are concerned about censorship of conservative speech by Silicon Valley progressives and liberals are concerned about Russian manipulation, it seems like a naturally bipartisan concern.

Edit: genuinely wondering what downvoters are objecting to in particular? Do you not believe that social media companies have a monopoly over their own networks? Do you disagree that they can and do steer public opinion and thus public policy? Do you disagree that this is a bad outcome? Perhaps it’s a bad outcome but regulation is an ineffective solution (e.g., libertarianism)? Educate me.

Re:Face ID and Touch ID for the Web by gowld on Monday October 19, 2020 @07:07PM (#24832052)
Apple sits between users and developers. If it's a monopsony on one side, it's a monopoly on the other side.
Re:Face ID and Touch ID for the Web by ogre_codes on Monday October 19, 2020 @11:06PM (#24833569)
Not remotely. Users can buy Android phones.

Having ~50% market share is not a monopoly.

Even suggesting Apple has monopsony as I did above is a stretch and is only the case if you define the market based on paying users.

Re:Face ID and Touch ID for the Web by throwaway894345 on Monday October 19, 2020 @11:12PM (#24833611)
The monopoly/monopsony distinction is pedantry. The important point is that consumers and developers suffer because one company controls access to the lion’s share of a market. That point can be criticized and debated, but litigating semantics makes for boring reading and anyway it’s off topic.
Re:Face ID and Touch ID for the Web by ogre_codes on Tuesday October 20, 2020 @12:26AM (#24833917)
> The monopoly/monopsony distinction is pedantry.

Expecting people to be in the general ballpark of the definition of a thing isn't pedantry. It's kind of hard to have any sort of meeting of the minds when people ignore even the basic premise of a term.

Re:Face ID and Touch ID for the Web by ascorbic on Tuesday October 20, 2020 @02:10AM (#24834376)
> Having ~50% market share is not a monopoly.

Most competition regulators disagree. 50% of a market is well above the threshold for both the US and EU to consider a company to be a monopoly. They usually treat the cut-off as around 20%.

Re:Face ID and Touch ID for the Web by stouset on Monday October 19, 2020 @10:03PM (#24833294)
How does this argument not apply to Facebook and Google?

Hint: It does, 100%. Epic could pick a fight with Google, tomorrow, that culminates in the same exact outcome.

Re:Face ID and Touch ID for the Web by enos_feedler on Monday October 19, 2020 @06:13PM (#24831608)
It isn’t productive to establish defense against an arbitrary future that turns on you. Spend those brain cycles focusing on your user and building a great product. Choosing Sign in with Apple is great for Apple users.
Re:Face ID and Touch ID for the Web by vinceguidry on Monday October 19, 2020 @06:19PM (#24831662)
It absolutely can be productive. So many people have done as you said and had the rug ripped out from under them by $ARBITRARY_PLATFORM_DECISION (cough cough YouTube) that if they had thought the risk they were taking on by going with one platform they might still be in business.
Re:Face ID and Touch ID for the Web by enos_feedler on Monday October 19, 2020 @08:31PM (#24832689)
I heard a guy died getting struck by lightning once. I am _never_ leaving my house during a storm again.
Re:Face ID and Touch ID for the Web by asdfasgasdgasdg on Monday October 19, 2020 @06:30PM (#24831742)
Maybe so. But how is this different than saying, "I have nothing to hide, so I'm not worried about having my car searched?" It's a somewhat pragmatic point of view but I wonder if it is a good idea in the limit.
Re:Face ID and Touch ID for the Web by enos_feedler on Monday October 19, 2020 @08:37PM (#24832758)
So what are you saying then? We shouldn't agree to a system that allows our car to be searched because under some limit it might be bad for us? What are we comparing this to in the Apple case? What is the equivalent of the "car search"?
Re:Face ID and Touch ID for the Web by gowld on Monday October 19, 2020 @07:04PM (#24832018)
"I have nothing to hide, so I'm not worried about having my car seized"
Re:Face ID and Touch ID for the Web by Teever on Monday October 19, 2020 @06:38PM (#24831803)
> It isn’t productive to establish defense against an arbitrary future that turns on you.

It isn't?

Isn't that like, the hallmark of intelligence?

Re:Face ID and Touch ID for the Web by danudey on Monday October 19, 2020 @07:09PM (#24832064)
Against an arbitrary future? No. Against a likely future? Yes.

It is not the hallmark of intelligence to come up with every possible thing that could go wrong and build defenses against it just in case someone somewhere does something counter to their wellbeing.

If you use any third-party login system, think about how you can migrate users between accounts, or validate that they are who they say they are, that's perfectly normal. What if Twitter OAuth goes down? What if your Google dev account is suspended by some automated system for some reason? You should definitely have some kind of plan for that.

Spinning off contingencies in case Apple changes its developer policies out from under you and suddenly no one on iOS can log in? Too specific and arbitrary.

Re:Face ID and Touch ID for the Web by enos_feedler on Monday October 19, 2020 @10:05PM (#24833312)
I think you watch too much Doomsday Preppers
Re:Face ID and Touch ID for the Web by wtetzner on Monday October 19, 2020 @04:52PM (#24830879)
> or the headache of managing yet another web account.

Honestly, I find this to be the distant second behind no account. I treat my password manager as my SSO provider in some sense.

Re:Face ID and Touch ID for the Web by qppo on Monday October 19, 2020 @04:50PM (#24830870)
I've had an issue with sign-in with Apple where using an autogenerated emails ruins certain support interactions. One of them was cancelling a subscription service that was eventually resolved (they required me to email their customer support, which I couldn't figure out how to do using the autogenerated email address created by "sign-in with Apple").
Re:Face ID and Touch ID for the Web by matthewmacleod on Monday October 19, 2020 @05:47PM (#24831409)
While it’s frustrating and worth pointing out of course - what really happened there was a bug in the service provider’s support process!
Re:Face ID and Touch ID for the Web by qppo on Monday October 19, 2020 @05:55PM (#24831477)
It was actually a dark pattern, not a bug.
Re:Face ID and Touch ID for the Web by tchalla on Monday October 19, 2020 @08:10PM (#24832522)
It would be helpful if you could let us know how you managed to send that e-mail.
Re:Face ID and Touch ID for the Web by mr_toad on Monday October 19, 2020 @09:19PM (#24833076)
You can see the email that Apple generates:

https://support.apple.com/en-us/HT210426

Re:Face ID and Touch ID for the Web by tchalla on Tuesday October 20, 2020 @05:56AM (#24835570)
Yes but the situation I asked for a solution is different. It is not about not seeing the e-mail, it is about sending from the private e-mail. Example

You subscribe with `[email protected]` which relays to `[email protected]`. Customer support asks you to chat with them from the same ID you signed up. Your e-mail client sends email from `[email protected]`. How can you quickly respond to the customer support from `[email protected]`?

Re:Face ID and Touch ID for the Web by qppo on Tuesday October 20, 2020 @12:57PM (#24839704)
I didn't, I found an alternative that was specific to the service.
Re:Face ID and Touch ID for the Web by mszcz on Tuesday October 20, 2020 @03:16AM (#24834650)
> convenience, security, and privacy of Sign in with Apple over Google, Facebook

Unless of course they block you for whatever reason. Then the process of getting back access has nothing to do with convenience, security, and privacy...