Live data from Hacker News

Apple is getting this wrong

openai.com

261–270 of 312 posts

Re: Apple is getting this wrong

#261
post #164

Earlier quoted context omitted.

They aren't screenshots

Which, somehow, confused me even further. I get that it's a stylistic choice to make them easy to read or whatever, but my first thought was "wait, they just posted screenshots with the names censored like a bad Reddit post?"

Semantic HTML and CSS for text is infinitely better than screenshots for accessibility, as well as cheaper to process for LLMs/agents reading it.

For the first reason alone, it's worth it when you can.

Re: Apple is getting this wrong

#262

Earlier quoted context omitted.

I was a bit confused too initially, but it looks like Chang was asking for the data to be copied _off his iCloud_ by the existing employee on his final day of employment. And then everything after that is just the existing employee asking for help on things Chang had prior knowledge of

Why in the world would a high-level Apple employee not sign out of his personal iCloud on his work computer, and then also use his personal iCloud for data from his new company?

Because Apple has this unorthodox policy of using iCloud for work files, and recommends employees use their personal Apple IDs.

I'm not kidding.

Re: Apple is getting this wrong

#263
post #33

>They now admit that their outside lawyers emailed the wrong person after confusing two Asian last names—only after we brought this to their attention. I find it bizarre that they felt the need to specify "Asian". What does that have to do with anything?

Latin alphabet transcription of East Asian languages tend to be incredibly lossy and there tends to be a lot of ambiguities. That Vietnamese surname of Nguyen is formally written as Nguyễn in the current script, or as 阮 in the old adapted Hanzi script, and practically pronounced somewhere around "gwen". Most other EA countries tend to do equivalents of "阮" -> "gwen", and East Asian cultures generally prefer Last-Firs…

Even if Westerners maintained the characters for the names rather than transliterate them, there's still the problem that common surnames are used by literally hundreds of millions of people of Chinese descent, and there are a lot of commonly-used given names as well. I think in all of Chinese, Korean, and Vietnamese almost all given names are 1-2 syllables in length, so there's even less space for disambiguation, even before you get to the additionally ambiguities introduced by transliteration and dropping of diacritics.

Japanese has several advantages:

1. Both given names and surnames often use more than 2 syllables. This makes it more familiar to speakers of European languages, where multi-syllable words are no big deal.

2. English speakers find Japanese easier to pronounce and remember due to its simpler syllable structure and use of globally more common sounds compared to the other languages.

3. Unlike the other languages, Japanese names are always given in Given Name, Surname order in English media, while names from the other languages are inconsistently transcribed in either order.

4. Japanese is the "default" East Asian culture for the West in many ways, since it's the one that at least the US has most deeply engaged for the longest time. Many, many cultural exports that actually originated in China were introduced to the West via Japan with Japanese names. Also, Japan has been an advanced industrial economy since the late 1800s, while China only achieved that status a few decades ago.

5. Japanese transcription into Roman characters has remained consistent for a long time (helped by the simpler phonology). Chinese and Korean have been cursed with several incompatible transcription systems over the years - although Pinyin has been winning out for Chinese, there are still many names with legacy transcriptions, not to mention the other Chinese languages needing their own transcriptions. Vietnamese does exclusively use Latin characters, but the diacritics and unfamiliar pronunciation makes them harder to remember.

Re: Apple is getting this wrong

#264
post #107

What I don't understand that if two companies are in legal battle, can they discuss the case and try to influence public swing by doing a blog post or sharing evidence that is not verified by anyone other than the party sharing them. OpenAI, even after raising this much capital, had never anticipated that something like this could happen yet keeps digging it's own grave. At this point all that's left is for them to k…

OpenAI always has the option of transforming themselves to a 'national security corporation' as I'd like to call it.

I mean, just look at Kim Dotcom or Aaron Schwartz.

Re: Apple is getting this wrong

#265
post #97

Earlier quoted context omitted.

Roughly one in five Koreans have surname "Kim". Upward of 40% Vietnamese have surname "Nguyen". "Li" is quite popular in China. Specifying "Asian last name" in this context is quite apt.

But what makes that necessary context? That can be communicated clearly without specifying Asian, „Apple confused 2 people with the same name“. Adding Asian sort of excuse Apple for the mistake, which is strange for OpenAI to do? I would tend to believe they are implying some casual racism

> I would tend to believe they are implying some casual racism

There's probably a little bit of that, but also simple carelessness.

Re: Apple is getting this wrong

#266
post #83

Reading through this, the Apple side of the story is actually the more fascinating one. It's frankly bizarre that a company of that scale had to rely on a former employee's (Chang Liu) personal iCloud access. It exposes a massive flaw in Apple's offboarding and internal system management. Combine that with their legal team confusing an Asian surname and emailing the wrong person, and publicly, Apple just ends up look…

> Whether Apple's tech was copied or not is almost secondary. The real existential threat for OpenAI is the legal discovery process, which could expose their internal AI architecture and training data to the public (and to Apple). That risk is exactly why OpenAI is playing this out in the court of public opinion—to force Apple's hand.

Why would that be relevant for a hardware project? Discovery doesn't mean carte blanche to dig around in arbitrary company secrets - and there's significant danger to Apple as well. Did Apple give corporate secrets gathered from the former OpenAI-Apple deal to Google for their Gemini integration, or for Apple's own AI?

Re: Apple is getting this wrong

#267

Earlier quoted context omitted.

I mean it makes sense. They somehow still don't have a proper product for businesses to manage Apple devices and accounts. Instead people have to rely on third party integrations. What happens if someone is fired and had kept info only on their personal account that is highly valuable ? Or wants to steal corporate info?

> They somehow still don't have a proper product for businesses to manage Apple devices and accounts I am not sure why that should matter. If company can handle BYOD model then they should solve that on hardware level - by issuing work phones (and other devices).

> If company can handle BYOD model then they should solve that on hardware level - by issuing work phones (and other devices).

But OpenAI's allegation is that Apple doesn't do that, either out of incompetence or malice (to add legal uncertainty when their employees go to competitors).

Re: Apple is getting this wrong

#268

Earlier quoted context omitted.

I have as well but if you want to use any software that is only on the App Store like Numbers or Pages then you are out of luck. It is a sub-standard experience and it looks like it is only going to get worse as Apple pushes iCloud into more areas of macOS.

But I don’t have to use any apps from the store, in fact I’d say that at my company there aren’t any apps available on the store that we use. So the parent is right, it’s perfectly usable without ever touching iCloud. I don’t think I’ve ever even opened the settings for it on my work laptop

Apple certainly uses Numbers, Pages, etc. internally extensively, so you really do have to sign into an iCloud account as an employee.

Re: Apple is getting this wrong

#269
post #97

Earlier quoted context omitted.

Roughly one in five Koreans have surname "Kim". Upward of 40% Vietnamese have surname "Nguyen". "Li" is quite popular in China. Specifying "Asian last name" in this context is quite apt.

But what makes that necessary context? That can be communicated clearly without specifying Asian, „Apple confused 2 people with the same name“. Adding Asian sort of excuse Apple for the mistake, which is strange for OpenAI to do? I would tend to believe they are implying some casual racism

Because confusing two people because of having the same name is much less likely for European names than for Asian names (there are only about 100 Chinese family names, for instance), so it's an indirect dig that Apple wasn't paying attention (since they presumably employ a lot of Asians, and thus should know better). There's no need to bang on the racism drum, it's pretty tiring.

Re: Apple is getting this wrong

#270
post #14

Earlier quoted context omitted.

I've heard multiple times directly from Apple employees that there is no way to login to iCloud on your work machine using a company-controlled account. Many people create new Apple ID's which they only use while working there, but others just use their personal iCloud accounts. You are, of course, not supposed to store company data in iCloud. But thanks to Apple's own efforts, it's difficult to use a Mac without bei…

Yes this seems incoherent and incompatible for a company that supposedly care about their trade secrets.

Which is what OpenAI will argue - that Apple is negligent in protecting their trade secrets. Trade secrets are not protected in the USA if the company doesn't take reasonable effort in protecting them. I would feel quite confident as a lawyer arguing against a company that intentionally has their employees use personal accounts on their corporate devices, long after using separate work accounts and devices has become SOP for large companies with serious security concerns (almost certainly including OpenAI itself).

This is better explained in The Information article (which is paywalled): https://www.theinformation.com/articles/apple-icloud-policy-.... Emphasis mine:

> When new employees join Apple, the company often issues them an iPhone and Mac and pays for an iCloud account with a large amount of online storage capacity. Crucially, during the onboarding process, Apple encourages new hires to use their preexisting personal Apple IDs with this iCloud account, through which their co-workers can share internal Apple documents and other files with them.

Post reply on HN