121–130 of 216 posts
I wish I could set up "Sign in with Apple" on a blog without paying $99/yr for a developer license.
Why do you want this. Is it a benefit to you? If it is why should you not pay for that benefit? Nothing is free.
I wish I could set up "Sign in with Apple" on a blog without paying $99/yr for a developer license.
Why do you want this. Is it a benefit to you? If it is why should you not pay for that benefit? Nothing is free.
Plus, it's not for the dev, it's for the users of the website.
I wish I could set up "Sign in with Apple" on a blog without paying $99/yr for a developer license.
Why do you want this. Is it a benefit to you? If it is why should you not pay for that benefit? Nothing is free.
No leaked email address, no need for anyone to store password, people using iCloud instead of Gmail.
What they're asking, for it to cost zero, sounds perfectly reasonable here.
Earlier quoted context omitted.
So any mail to anyrandomstring@yourdomain.com is actually received? Sounds like something that works great when only you do it, but might quickly be abused if it catches on?
If you do this you immediately get thousands of emails a day from bots trying common first names etc. Much better to maintain an explicit list of names you're currently allowing.
This is a huge selling point. Private email relays often get blocked, the only lasting solution is to put them on the same domain as, and in the same format as, a significant number of non-private email addresses. As far as I’m aware the only other provider doing this is Fastmail. Comments about lock-in aren’t wrong, but it has to be this way. You can make arbitrary email addresses at your own domain, but anybody who…
You assume that the domain is used by one person or what?
Also, the point of these is typically to prevent spam. Noone is going to spend a fraction of a cent or second to try and figure out who is behind the adress.
Earlier quoted context omitted.
So any mail to anyrandomstring@yourdomain.com is actually received? Sounds like something that works great when only you do it, but might quickly be abused if it catches on?
If you do this you immediately get thousands of emails a day from bots trying common first names etc. Much better to maintain an explicit list of names you're currently allowing.
Can someone explain the backstory behind this? I'm reading some of the comments here and I feel like I'm missing something here.
For the "hide my email" feature, Apple currently and has always used "@icloud.com". This masks you amongst all iCloud users. They were planning to change it to a custom domain, which would allow sites to easily filter out and reject "Hide my email" users based on the email. They have now reverted their plans to change this, meaning "hide my email" is still "@icloud.com".
Whereas people's Apple emails are often at @icloud.com
So I don't think it masks you amongst all iCloud users. I'm confused how this is much better!
UPD: I obviously mean alias addresses template make most of them too easy to recognize.
Earlier quoted context omitted.
Why do you want this. Is it a benefit to you? If it is why should you not pay for that benefit? Nothing is free.
You say nothing is free, but Amazon, Discord, Dropbox, Facebook, GitHub, Google, Instagram, Microsoft, Paypal, Reddit, Slack, Steam, TikTok, Twitter etc all offer it for free. Plus, it's not for the dev, it's for the users of the website.