In the U.S., rooting does not void the warranty unless the manufacturer can prove the rooting itself caused physical damage. Just having a blanket policy of rooting = voided warranty is illegal because of the Magnuson-Moss Warranty Act.
Sometimes, that’s exactly what you want though: you don’t care (and the user has bigger issues if their email is compromised) if the email is compromised. In the terms you might say “access is granted based on access to email that you register with” and if someone loses access to their email, you don’t need to do any id verification or “proof” to recover the account. You can just say “tough.”
For accounts which hold something of value (monetary and/or personal data) then sure.
But every once in a while when I need to login to GitHub it blocks my logon and demand what I give it a code sent to my e-mail. In essence this doean't seems that different from the scheme in the article.
Thanks for mentioning. Nice logo!
I have seen that and borrowed verbose sql logging. Nice gem, I see the differences.
My gem:
1. has more checks
2. has more migration helpers (renaming tables/columns, changing columns types, backfilling etc)
3. more flexible in terms of configuration
4. has background data migrations
5. does not disables wrapping migrations in a transaction, which can be inconvenient and dangerous
