> That's entirely service dependent, and the standard doesn't mandate "Service must not allow multiple passkeys"
Unfortunately, given the laziness, incompetence, and cost-consciousness of organizations like traditional financial institutions, telcos, governments, etc., many of them have & will end up with that implementation.
Yeah - and as a user, I don't want my device manufacturer to have that level of influence or control over the authentication that I use for unrelated services.
Stronger than "don't care about" (at least if I and some friends I've discussed this with count as normal people): this is actively what I don't want! I want control over my authentication and I don't want it bound to device, browser, OS, etc.
Yeah - for sure I found it a bit strange... I guess the use cases (and maybe target users) are different:
Merlin - Use lots of data, storage, and analysis to help me identify what bird this is
eBird - I can personally identify lots and lots of birds: keep track of all the ones that I and other have seen with maximum speed and efficiency
And their eBird app! A masterpiece of design for a user base that they deeply understand. Something of a learning curve, but extremely efficient and useful for advanced / expert users.
There are many examples of important paper records (property, birth/death, etc) being lost in fires or floods, so it's not the case that "everything worked perfectly fine" in those days either.
>> The purpose of a college degree is NOT a job
>> If knowledge and prestige is all that matters
I disagree. The primary purpose of the college degree is the job. If you don't need a job (which derives from the signaling factor of the degree == the prestige), you can just study the same material and gain the knowledge by yourself without getting a degree.
Which is actually a good reason for entities subject to GDPR to forbid use of personal messaging apps on work devices... (And to forbid users to use work / official apps for personal messaging.)
So... I used to work in the "digital movie & TV selling" industry. Our product detail pages, like pretty much all our competitors, had language on the call-to-action buttons that said "purchase" (and also, as an alternative, "rent," for 48- or 72-hour viewing).
At one point, about 10 years ago, one of the major Hollywood studios came to us and required us to change that because they believed that exactly this sort of thing would happen and we would all be setting ourselves up for liability because consumers would rightfully assume that that meant they owned the movie "forever."
You can fit about 8,000 MacBook Pros into a 40-foot container in their retail packaging. If the cost of shipping a container went up by USD8,000 (a very large amount), that would be about USD1 per MBP. It's not the shipping that's driving the price increase.
A strategic reserve of a commodity that (historically) depreciates at ~50% per year is a terrible trade for occasionally avoiding demand-driven price spikes.
Pretty sure that the agreement that Google employees sign (a "contract") when hired reflects exactly that. At least at did when I joined (I left > 3 years ago, speaking here only for myself...)
>> how can a general purpose robot perform them better
Better than what? It seems that as long as they perform the tasks "better" (cheaper / faster / lower-error) than the humans that are currently performing them, that is an improvement for the factory owner.
Sorry, but why is that a problem? If they didn't find someone, they closed the posting, then reopened it later, what is the issue?
Or, as in some cases, perhaps they did find someone? I've been at companies where we hired many engineers sequentially over time using the same job description. Should we just have arbitrarily changed the JD?
> That's entirely service dependent, and the standard doesn't mandate "Service must not allow multiple passkeys"
Unfortunately, given the laziness, incompetence, and cost-consciousness of organizations like traditional financial institutions, telcos, governments, etc., many of them have & will end up with that implementation.