Hi, these simplifications are very nice indeed! I was wondering if we could go one step further by removing email confirmation. Once you’ve signed up (and let’s say the app doesn’t require you to confirm your email), then you can only log in using a magic link, which means receiving an email and clicking the link inside. This is exactly the same as confirming your email! Then you can add a password in your settings if you want and stop using magic links, but your magic link login will be enough to ensure that your email address is valid. What do you think about that?
ppff01
Eiji
A bit off-topic, but after reading the comments about changes to email I wonder how long it take for frameworks like Phoenix to implement passkey support in the generators. This is much more modern and secure approach. I’ve seen many sites implement that already, so it’s definitely not “too new” kind of thing. 
steffend
Phoenix Core Team
Confirming the email is important for security reasons, see mix phx.gen.auth — Phoenix v1.8.0-rc.3.
ppff01
I understand that it is important, but what’s the difference between the confirmation process and the magic link login? I’d argue there’s none. In that case, the first login (using magic link) could be used as the confirmation.
This is even already supported by the code because login_user_by_magic_link is used as the confirmation entrypoint. Then, we could just remove the confirmation live view and simplify the registration process.
To be clear:
Currently: registration → specific email → confirmation → login
My idea: registration → magic link email → login (if the email was not confirmed, confirm it now without requiring the user to click a button or anything else)
steffend
Phoenix Core Team
It is mostly the same, yes. We decided to still have separate emails with a slightly different wording, because that seems quite useful to have. If you want to treat it the same, you can change that.
The separate confirmation screen is there because otherwise email clients like outlook tend to break one time links, as Microsoft visits them server side for security scanning. I’ve seen reports that they even started executing JavaScript while doing that, breaking some workflows that relied on the GET request triggering a POST with JS.
steffend
Phoenix Core Team
I‘d personally love built in passkey support, but it would require a separate library, so we decided to keep it simple for now. It is definitively worth to explore for the future though.
ppff01
Kevo
I think I may have gotten a final answer to my problem with tailwind.
https://github.com/oven-sh/bun/issues/20859
It seems the baseline build of bun is deprecated for MacOS. 
steffend
Phoenix Core Team
That is indeed unfortunate, but now we have an answer. We should probably add a note about that to the :tailwind repo.
szluyufeng
Just wondering if there’s any ETA for RC4 and the final release. I’ve been holding off on upgrading until RC4 is out.