Craig Heydenburg

this issue must be resolved with #3720

@robbrandt please read #3720. the proposal is to disallow registration of a new Authentication type (Facebook in your scenario) because of the duplicate email.

> #4197 would - if desired - need to bypass all validation of duplicate emails and implement some kind of 'secondary authorization' method. To do this, the currently logged in...

Because the rate limiter is marked experimental in Symfony 5.2, I am postponing this ticket until the feature is no longer experimental. The code diff link I posted above has...

yes. this should be done. Although it can be a little complicated deciding which modules to include and making sure they are 100% functional, etc. I don't remember why they...

that would be most excellent. but would require some serious infrastructure.

ok to put off to 4.0 for me.

I agree that the simple anti-spam question is ineffective and probably implemented wrongly. Certainly, it would be better implemented as a hook or listener. I'm not sure another core module...

it won't be useful to the core if it is [built for Core 2](https://github.com/Kaik/KaikMediaAntispam/blob/master/composer.json#L23)

https://github.com/zikula/core/blob/master/docs/Development/General/Refactoring_3.md