I guess their thought process is, both alias and non-alias accounts use @icloud.com
You were always able to reserve a normal icloud email address just like you would a GMail account, so banning all icloud email addresses would be banning non-alias Apple customers
That being said, I'm not convinced anyone who wanted to ban aliases couldn't have already. The alias emails look weird enough I'm guessing you could ban them with few false positives.
The point of the article is previously banning Apple's temp domain would create many false positives (all the normal Apple registered emails that chose @icloud.com during setup)
The problem the article is about is that suddenly even those of us who refuse to argue with a machine are being dragged into it.
I've had simple prompt engineering tasks that cause 4.8 to clamp down. In the past "browbeating" it (read: a sentence telling it not to read the task in bad faith) was enough.
Now it digs in and starts ranting about why it won't capitulate, I'm actually wrong, etc.
Extremely frustrating, and it became a problem with Opus 4.7 because they're trying to make up for the downgrade in parameter count with more RL, but RL does relatively poorly with non-trivially verified things like nuance in instructions.
I'm staying in a hotel right now and the TV is locked in hospitality mode and was blocking me from just installing Plex. It (Opus 4.8) gave me this whole jeremiad about how I need to be careful and it probably won't work and I should just watch on my laptop, but it did give me the service menu code. But man, it was such a downer.
Gemini gave it and clearly explained how best to get in, and then troubleshooted a few other weird issues that cropped up, without the moralizing.
We're offering secure connections to sources like SQL DBs, warehouses, file stores, and MCP/API sources like PostHog or Salesforce. Customers can choose to set up credentials in our key store. We also support directly dropping data into BitBoard (where we sync it to object storage).
You're laying on enough qualifiers that even a recent robbery of a Waymo is precluded, because (if we really want to victim blame) their window was down which is asking for it.
But overall, not sure why the tone of these replies: then Venn diagram of "wants to rob people" and "cares Google's AV will record it" doesn't include as much overlap as you're implying.
A Waymo has even been used as a getaway vehicle a few times now, once even successfully
"Anthropic says these safeguards only affect 0.03% of developers. Maybe that's true today."
I don't think it's true today. It's like when schools mention "average class size", where that average is dominated by classes with like 2 students instead of classes with 100.
Much more honest would be the percentage of developers who previously used their models for the model development tasks they're targeting, but it actually looks like they're saying 100% of them are affected based on the language around it "always having been prohibited".
You were always able to reserve a normal icloud email address just like you would a GMail account, so banning all icloud email addresses would be banning non-alias Apple customers
That being said, I'm not convinced anyone who wanted to ban aliases couldn't have already. The alias emails look weird enough I'm guessing you could ban them with few false positives.
reply