[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:22 desrosj]:
 > I commented on the PR already because I saw that discussion first. But
 just to respond to a few points I did not see specifically called out on
 the PR's discussion.
 >
 > Replying to [comment:19 jorgefilipecosta]:
 > > The long-term ideal solution is making sure all plugins in the
 filesystem that have connectors appear on the connectors screen even when
 not active and allow their activation from there, but that is something
 that needs additional thought and will require bigger changes.
 >
 > I strongly disagree that this is the ideal solution here. This will be
 not only be abused by plugins rendering the Connectors page essentially
 useless (all you need is to be installed, and you can bug the site owner
 to reactivate and renew forever on this page). It will most certainly also
 be a vulnerability gold mine.


 That's a fair concern, but it's not quite what I had in mind. Inactive
 plugins wouldn't be able to execute arbitrary code to register a
 connector. We're considering a few options, for example a special syntax
 in the plugin definition header or a dedicated connectors.json file.
 Either approach would also allow the WP.org API to expose connectors that
 core can use to render the default connectors list, removing the need for
 any hardcoding. That said, I think we need more time to land on the right
 path forward here, and I appreciate the thoughtfulness around security.



 > I am of the opinion that it ''should'' be different. The AI connectors
 have a specific purpose that the project is trying to champion by
 empowering users with the tools they need to be successful in an
 increasingly AI world. If it were up to me, the two groups would be `AI
 connectors`, and `API Keys` or `Everything Else`.


 I hear you, and I agree that the AI connectors serve an important purpose
 in empowering users. At the same time, Akismet also play a meaningful role
 in helping users succeed, in this case by saving them from spending
 significant time dealing with spam. Given the existing decision to include
 Akismet with core, I think it's natural for its connector to appear on the
 Connectors screen before activation, with an easy path to activate it from
 there. If we're already showing connectors for AI services whose files
 aren't even included in the installation, it seems reasonable to do the
 same for something that's already bundled.

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