[wp-trac] [WordPress Trac] #65012: Fix: Register Akismet Anti-Spam as a connector

[WordPress Trac]

#65012: Fix: Register Akismet Anti-Spam as a connector
------------------------------+-------------------------------
 Reporter:  jorgefilipecosta  |       Owner:  jorgefilipecosta
     Type:  defect (bug)      |      Status:  reopened
 Priority:  normal            |   Milestone:  7.0
Component:  General           |     Version:  trunk
 Severity:  normal            |  Resolution:
 Keywords:  has-patch         |     Focuses:
------------------------------+-------------------------------

Comment (by jorgefilipecosta):

 Replying to [comment:20 peterwilsoncc]:
 > That's my point, without the plugin being active the Akismet key does
 not serve a purpose. As the AI connectors are designed to be shared
 between various plugins. The Akismet API key serves a purpose exclusively
 for a single plugin.

 That's a good point that is worth addressing. The UI doesn't actually
 allow setting a key without activating the plugin first. What it does is
 let users activate the plugin directly from the connectors screen, without
 needing to navigate to the plugins screen, and then provide the key right
 away without any page reloads. So by the time the key is set, the plugin
 is already active.
 The connectors screen serves as a place to configure connections to third
 parties that enhance the WordPress experience. Showing Akismet there
 provides an easy and intuitive way to activate the plugin, and it also
 reinforces the idea that the connectors screen is not exclusively for AI
 providers. And, though connectors really shine when they can be shared
 between plugins, connectors with a tighter relationship with a single
 plugin still have a place in this new central screen.

 > Where was this discussed? Like the AI client connectors, the wider
 contributor group should have had a chance to discuss this.

 We are discussing this publicly here both on Trac and GitHub and @gziolo
 also raised awareness for this discussion on the release leads slack
 channel. Everyone is welcome to share their thoughts and feedback. And I'm
 open to other alternatives/possibilities that achieve the goal of showing
 Akismet on the connectors screen before activation and that are feasible
 during the 7.0 release cycle.

 > Looking in to this further, I've noticed that the plugin's development
 version already includes a connector, as posted in Slack last month, so
 this definitely needs to be reverted in order that WordPress users don't
 end up with two Akismet connectors in the settings.

 It is fine and expected that plugins can define their register connectors.
 For instance, AI providers can overwrite the core UI to include token
 information; or akismet can overwrite the UI to show plan information. The
 connector will not appear two times. The same connector does not appear
 multiple times when registered, provided the IDs used are the same. I'm in
 touch with Akismet developers so that we're in sync. For example,
 @bluefuton had a look into related changes in the Gutenberg repo and left
 some comments; if there is any plugin incompatibility it will be addressed
 in Akismet before the 7.0 release.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65012#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform