You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To audit for spam and dead contacts, we will need external data sources. Two examples:
StopForumSpam provides a list of known abusive email addresses. When a user attempts sign-up with an email address in this list, they should be gated (eg: emailing support to request an unblock). For existing accounts, we'll need manual validation before classifying the account as spam.
Both databases are significantly larger than our own, so it doesn't make sense to overload the existing EmailAddress and PhoneNumber models to hold this data. Instead, we should follow the model adopted with Geoname data, hosting this in a separate database with periodic updates.
This will entail:
New bind_key alongside geoname for hosting contact data, or maybe rename geoname itself to be an extdata for external data.
New CLI commands for downloading these databases, loading them, and scrubbing existing data.
For the spam lists, a bloom filter for rapid lookup before doing a full index scan.
The text was updated successfully, but these errors were encountered:
To audit for spam and dead contacts, we will need external data sources. Two examples:
StopForumSpam provides a list of known abusive email addresses. When a user attempts sign-up with an email address in this list, they should be gated (eg: emailing support to request an unblock). For existing accounts, we'll need manual validation before classifying the account as spam.
TRAI publishes a Mobile Number Revocation List (MNRL) for expired Indian mobile phone numbers. These should be forgotten from our database, unlinking them from user accounts.
Both databases are significantly larger than our own, so it doesn't make sense to overload the existing EmailAddress and PhoneNumber models to hold this data. Instead, we should follow the model adopted with Geoname data, hosting this in a separate database with periodic updates.
This will entail:
geoname
for hosting contact data, or maybe renamegeoname
itself to be anextdata
for external data.The text was updated successfully, but these errors were encountered: