Should SmokeDetector scan Collectives Articles?

[CoconutMacaroon]

Is your feature request related to a problem? Please describe.

As of today (November 14, 2023), SmokeDetector produces an error (That does not look like a valid post URL) when running !!/scan on Articles. I tested that in CHQ. While hardly urgent, if the frequency of Articles significantly increases, automatic scanning of them would be nice. Autoflagging of Articles would be nice too.

Describe the solution you'd like

I propose that SmokeDetector will automatically scan for new Collectives Articles that might be spam (and report them too). I'd also suggest that !!/scan and !!/report functionality be included.

Describe alternatives you've considered

It doesn't happen, and SD doesn't handle Articles. As of now, the volume of Articles is low enough that's probably fine. But, if the number of them picks up, having a GitHub Issue to track it seems worthwhile.

Additional context

Even if we agreed this was worthwhile, the endpoint for Articles is currently broken, so that might need to get fixed as a prerequisite.

I don't think this is needed or necessarily worth implementing right now, nor do I have time at the moment. Still, it seemed worth tracking in case it becomes relevant later on.

Update: per an answer by a CM, it seems the API had Articles functionality removed, so I don't know if this is even possible without scraping currently.

[makyen]

I've marked this as status: deferred, as it's not something we will do until the SE API supports supplying the data. That doesn't mean we will do it at that time, just that it's not possible until that happens.

Note that we would also need some way to know that a new Article had been created and/or edited. I haven't looked into if there's a WebSocket that reports Article creation/edits, but polling would not be the preferred manner of looking for those events.