Apple is about to make Hide My Email useless

304 points - today at 6:37 PM

Source

Comments

jawiggins today at 7:54 PM
> If you use iCloud+ and Hide My Email, there is still time to generate more aliases on @icloud.com as the change has not yet landed and the rate limit for creating aliases is at least 30 per hour.

Part of the reason to use Hide My Email was that it made keeping myself private hassle-free. Making a system to pre-generate values and then catalog them for later use is quite the hassle.

giancarlostoro today at 7:50 PM
If your website will block me out because I used a privacy friendly email, I want nothing to do with your website.
frollogaston today at 9:54 PM
"Useless" is a leap. The kind of site that would block private relay emails is the kind that was already getting my burner anyway. The private relay is for sites I want to hear from, but also want a failsafe in case they're hacked later.
jonotime today at 9:10 PM
Pro tip for doing something like this without apple. Buy or get a cheap domain name. Create a subdomain on it and have it catch and forward all messages to you when sent to that sub. For example:

nytimes@mailsub.example.com -> jono@gmail

anything-else@mailsub.example.com -> jono@gmail

You dont even need to materialize aliases at all.

mortenjorck today at 7:49 PM
> Long story short: now both Sign in with Apple and Hide My Email aliases are going to be issued on the @private.icloud.com subdomain. This makes it much easier to ban all aliases without affecting non-relay mailboxes on iCloud mail.

Could someone clarify why having Sign in with Apple and Hide My Email on the same domain would make a blanket ban easier rather than harder? What am I missing?

trollbridge today at 9:31 PM
In the flip side, someone who blocks private.iCloud.com will block the ability to do SSO with Apple, thereby cutting themselves off from Apple’s ecosystem.
teekert today at 9:42 PM
I use Proton aliases everywhere...Well not everywhere, there are indeed quite some places that don't accept a passmail.net address... So I can imagine this becoming a useless feature, at least on some sites.

Btw I only use these aliases for sites where I don't mind loosing the login, otherwise it would the mother of all lock-ins... Would have been nice if I could opt for aliases on my own (secondary?) domain... At least then I could still move them (using wildcards or some exported list).

abujazar today at 9:37 PM
Almost all of my iCloud relayed addresses are already @privaterelay.appleid.com, and they've been working perfectly. So I don't expect this to change any time soon.
Cider9986 today at 8:05 PM
Determined sites could already easily do this. Just detect the patterns used. I agree it's a useless change though.

heave_balks_0g@icloud.com

It shouldn't matter for the sign in with apple because sites are already expressly supporting that.

Email aliasing is hard because you want privacy from a herd of users, but then you're locked into that ecosystem versus a domain you control has no herd, but the upside is no lock-in.

k1next today at 8:35 PM
For me personally, Hide My Email is binding me to the Apple ecosystem more than iMessage (but I'm European).
frollogaston today at 8:12 PM
Maybe they've started seeing sites ban @icloud.com addresses
deleted today at 9:52 PM
deleted today at 9:44 PM
elcombato today at 8:21 PM
The rate limit seems to be 20/hour and not 30/hour as mentioned in the article.
deleted today at 8:25 PM
getcrunk today at 8:16 PM
Okay but banning private relay emails would also mean your site is blocking Apple sign in?
wxw today at 7:58 PM
I pay for Fastmail just for masked email and its integration with 1Password.
KiDD today at 8:29 PM
I guess I don't understand the concern... what does it matter if a different domain is used for Sign in with Apple and Hide My Email?
nerdjon today at 7:50 PM
I would bet that doing so would be a pretty quick way to have your app pulled.

They already require that you use Sign in with Apple, I would think that it working fully is also a requirement?

smth-smth-ai today at 9:06 PM
simplelogin from Proton works great, can recommend; for Uber I generate uber.random-word@simplelogin.com, for Slack slack.random-word etc to easily see who leaked my email
deleted today at 8:11 PM
Mindwipe today at 9:52 PM
Urgh, that's a huge downgrade. What a shame.
vslira today at 8:21 PM
Where do I sign to show my opposition to this change? Hide My Email has been essential to keep my digital life protected from abusive mail lists and frankly one of the features that make me associate icloud with a premium service
kylehotchkiss today at 8:48 PM
Did Hide My Email addresses cause problems for deliverability for actual emails/users on iCloud?
righthand today at 8:19 PM
Emailfake.com

Fastmail also has wonderful random email functionality you can link up to your Bitwarden client or use the Fastmail API.

risyachka today at 7:57 PM
Shameless plug - I created a chrome extension that allows to create unique email addresses that forward to your real inbox. It uses Cloudflare email routing, simplifies creating/labeling of new addresses and keeping track of them. Always 1 click away.

The addresses are pre-allocated and recycled when deleted so creating a new one is faster that with Apple's hide my mail.

https://github.com/webmonch/hide-my-mail-cloudflare

doctorpangloss today at 8:02 PM
email isn't really a decentralized system at all. Google, Microsoft and Amazon own e-mail delivery. Perhaps Google ads customers complained that they could not correlated private @icloud addresses, and we are now witnessing the consequences. What Apple got in exchange from Google, I don't know, I'm sure it is related to their Siri deal.
Razengan today at 8:04 PM
Oh fuck. I love Hide My Email and it's been the best feature about iCloud ever since it came out.

It's actually useful compared to Gmail's useless "yourrealaddress+alais" that gives away your actual email anyway, and it helped me catch quite a few spammers/data sellers.

Hide My Email addresses already have a peculiar format that others could guess, and some do block those, and there's no reason to add a blatant "private." tag.

This is a win for privacy-intruders, not users, just like Apple's iCloud Keychain API that has allowed Facebook, TikTok etc. to secretly track users across multiple devices and device reinstalls for years.

deleted today at 8:59 PM