Marco

Thanks! Glad that this works for you, but I’m not sure if we really want it in this repository here. There’s also a way to disable email verification and thus...

> I just don’t think the user should be marked as verified in the database if they’re not. That is certainly a good point. Thank you! You could later reverse...

Totally agree with all of what you said here! And as I said before, your solution seems to be the one that is conceptually clearer. If you allow logins without...

Thanks for the feedback on InnoDB compatibility! I think you may have to change the two columns `users.email` and `users_confirmations.email` from `varchar(249)` to `varchar(191)`. Preferably, you would change this right...

@darkalchemy Thank you! This is a more fundamental and intrusive change than changing the length of the two email columns. So if you’re fine with email addresses being limited to...

@eypsilon Thanks a lot for sharing your experience with InnoDB instead of MyISAM here. It’s great to have another confirmation that it’s really only a little extra work that is...

You are right. Thanks! While the library already provides methods for generating random tokens and for throttling, and you would only have to store that token in a custom database...

@ponasromas Can you explain this? Is there any relation between the storage engine and the garbage collection that we’re planning to implement? As noted above, we’re planning to clear the...

@Aristotle22 (1) I see no reason why all this cannot simply be handled by deleting *expired* entries only. Do you have strict (storage/performance) requirements that make it impossible for you...

The library is not specifically *designed* to work on the CLI, but instead is made for the browser. However, for tests, you should be able to make it work very...