Opened 14 years ago
Closed 13 years ago
#14443 closed enhancement (duplicate)
Stop notifying spammers about newly installed blogs
Reported by: | Viper007Bond | Owned by: | nacin |
---|---|---|---|
Milestone: | Priority: | lowest | |
Severity: | minor | Version: | |
Component: | Comments | Keywords: | has-patch |
Focuses: | Cc: |
Description
We got caught. Time to remove the offending code.
Attachments (1)
Change History (10)
#6
follow-up:
↓ 7
@
14 years ago
What about the kickbacks all core contributors have been getting from the spammers? Does that mean we don't get our cut anymore?
#7
in reply to:
↑ 6
@
14 years ago
Replying to coffee2code:
What about the kickbacks all core contributors have been getting from the spammers? Does that mean we don't get our cut anymore?
Yeah, nacin and I discussed that on Twitter. We're all going to have to sell our Ferraris and extra houses.
Hopefully though filosofo's solution will still provide enough income.
#8
in reply to:
↑ 3
@
14 years ago
Replying to filosofo:
I think we should keep it but add to Settings > Discussion:
- A radio selection:
"Be spammed [X] now or [] later?"
- An input field, so users have the freedom to choose:
"Enter the evil spammer to notify (required): [spammers@stupidjerks.com]"
- Two new action hooks for plugin developers:
pre_spammer_notification
andprior_to_pre_spammer_notification
Wouldn't it be better to add these options to the install-prosess as well. - You know, it's already hooked for public, so adding a "be spamed now" option should not be that much efort to add..
Anyway, there should be a prefered_spammer_network() hook somewhere..
I think we should keep it but add to Settings > Discussion:
"Be spammed [X] now or [] later?"
"Enter the evil spammer to notify (required): [spammers@stupidjerks.com]"
pre_spammer_notification
andprior_to_pre_spammer_notification