The post says that "Sign in with Apple" will issue emails on @private.icloud.com but "Hide my email" will continue issuing addresses on @icloud.com
These are two separate services. The problem was with the latter not the former. If the service decides to block @private.icloud.com they might as well remove Apple's sign in button.
Sure, but technically proficient users often have other things they want to spend their time on, outside of exercising technical proficiency on every single thing.
Heck, I don’t even do my own oil changes anymore despite it being easy. Life gets busy, you know?
Many systems out there have specific exceptions from their VPN policy for iCloud emails and iCloud private relay. Places that would immediately block fastmail because of its alias feature will not block iCloud because too many people use it. Market share is real power. You can ban 0.1% of your customers, you can't ban 30% of your customers.
Does it need to though? After so many years I can assume the program is complete as in there aren't any bugs left that need fixing and there aren't any new features needed in the scope of the program
Moreover, many websites now only allow login via state-affiliated identity providers and if you're one of those people that prefer email you're forced to use .ru email that is, in turn, requires validation via mobile phone, and it is now illegal to have an anonymous SIM card.
Basically, any online forum user can be _trivially_ tracked down to a real person. What a great day to be a hacker really.
Sometimes you can't even rely on harness not allowing ai to access certain files. "Oh, user doesn't want me to use `read_file` on .env? Well how about I run `cat .env` then?"
That's scary. Really should run it under different user with carefully assigned permissions.
iOS has the thing they call “time-sensitive notifications” which is a flag you put when submitting notification that is supposed to be Really Important Right Now. Unfortunately it’s not easy to mute everything that is not time-sensitive