Primary BrowserID email cannot use the automatic photo importers

[François Marier]

If a user creates a new account through BrowserID, the email address will be automatically confirmed, but the photo import page will not be shown (due to a limitation in the Django authentication API).

Therefore we probably need a way to manually trigger the automatic email-based photo import. This would also help when people confirm the email while logged out because they miss out on the photo importers too in that case.

An alternative would be to keep track of the first view of the profile page and to run the automatic photo importer then (i.e. first login).

[François Marier (fmarier)]

Another (better?) approach would be to always kick off a photo import job whenever an email address is confirmed.

Changes:

- photo imports are automatic (no need for the user to approve them)
- photo imports are asynchronous (done in a gearman worker as per bug #769760)
- imported photos are labelled with the service they're from (requires new "origin" field in DB)

Advantages:

- we can add as many importers as we want since their speed is no longer an issue
- we can increase the timeout (which might help with the Identica importer)
- confirming an email address while logged out would still run the importer (it would also resolve bug #886464)
- reduces the number of steps (i.e. cognitive load) that users have to take
- the main BrowserID email can benefit from these automatic imports
- we can run imported images through the optimization process

Downsides:

- no way for users to prevent the import from happening (they have to delete unwanted imported photos manually)
- photo will not be there immediately after confirming an email address

[François Marier (fmarier)]

Superseded by bug 1533018.