There are more robust solutions out there for protection against spam, and as this is an Automattic product it makes sense to remove it from a fork perspective.
What are the more robust solutions? But no reason why it has to be forced on install. I really like the idea of ClassicPress as a clean install without ANY plugins.
Daniele Scasciafratte
· September 10, 2018 · 10:32
I think that we can remove from the default plugin and let to the users to choice.
Neal Umphred
· September 10, 2018 · 16:27
Remove.
James Nylen
· September 11, 2018 · 19:55
This seems pretty straightforward to me. If anyone wants to submit a pull request for this one, please do it :)
Neal Umphred
· September 13, 2018 · 17:07
Just received an email notification from Wade Streibel that removing Akismet—which I use, by the way—is "Planned for v1.0.0."
Excellent!
John
· September 16, 2018 · 20:20
On a meta level: I've always thought of this plugin as spam.
James Nylen
· October 1, 2018 · 05:32
· edited
The link under "Completed" here is not pointing to the right place. We actually didn't need to do anything to resolve this - adding Akismet to WordPress releases is done on the WordPress build servers, and we will not have this step.
What are the more robust solutions? But no reason why it has to be forced on install. I really like the idea of ClassicPress as a clean install without ANY plugins.
I think that we can remove from the default plugin and let to the users to choice.
Remove.
This seems pretty straightforward to me. If anyone wants to submit a pull request for this one, please do it :)
Just received an email notification from Wade Streibel that removing Akismet—which I use, by the way—is "Planned for v1.0.0."
Excellent!
On a meta level: I've always thought of this plugin as spam.
The link under "Completed" here is not pointing to the right place. We actually didn't need to do anything to resolve this - adding Akismet to WordPress releases is done on the WordPress build servers, and we will not have this step.