Oof, I didn't know there was a hardcoded use of EventLogging inside of MediaWiki core. This seems pretty fragile. This migration makes sense, but are we sure we want to continue doing this in the long term?

In T323828#8424857, @Ottomata wrote:

Oof, I didn't know there was a hardcoded use of EventLogging inside of MediaWiki core. This seems pretty fragile. This migration makes sense, but are we sure we want to continue doing this in the long term?

I think the question of whether we want to have pingback really depoends on the question of how much we want to support 3rd party installations. If we want to support them, having statistics about them is really helpful. So I personally think it's suprt important to have this.

What makes this difficult is that it's somethign that needs to happen during installation, so we can't rely on extensions. That makes it a bit awkward...

needs to happen during installation, we can't rely on extensions

We also can't rely on them, as perhaps we want stats on a MediaWiki with no extensions installed?

Perhaps receiving these stats should be fully encapsulated within MediaWiki core then, rather than relying on EventLogging/Event Platform? Some hardcoded API endpoint to receive and store stats in a MediaWiki database table?

In T323828#8425757, @Ottomata wrote:

Perhaps receiving these stats should be fully encapsulated within MediaWiki core then, rather than relying on EventLogging/Event Platform? Some hardcoded API endpoint to receive and store stats in a MediaWiki database table?

That code and table would be unused on all except one MediaWiki installations... There is only one instance (mediawiki.org, I guess) that receives Pingack, right?

So the code for sending it should be in core, but the code for receiving it shouldn't. It doesn't even need to be in MediaWiki at all, could be something else entirely.

Hm, yes, but I guess I mean at least this hardcoded producer code in MW core wouldn't have a hardcoded external dependency?

Meh, too much work for what this is. I don't love it, but I don't have a better solution. Proceed! :)