Moderator Actions PubSub topic should work for all moderators of the channel
chat_moderator_actions topic in the PubSub documentation appears to only work with a broadcaster OAuth token. This prevents third-party modding tools that don't use some kind of centralized system from accessing information that is vital for effective modding (such as which mod performed an action, actions that aren't otherwise visible like unbans and viewing and approving messages filtered by AutoMod).
With a centralized system the broadcaster could provide a token somehow that the moderators don't need to have access to directly, however with purely clientside tools this is not feasible. I'm also not sure why moderators should not have access to that kind of information.
The moderator actions PubSub topic previously announced by Twitch Staff on the developer forums (https://discuss.dev.twitch.tv/t/in-line-broadcaster-chat-mod-logs/7281) does allow moderators to access this information. The announcement of the added "channel:moderate" scope requirement (https://discuss.dev.twitch.tv/t/upcoming-oauth-scope-requirements-for-pubsub/23203) gave me the impression that the old topic was now officially supported, so it's quite surprising and worrying that the topic added to the PubSub documentation has changed in a way that would break tools that many moderators have been using for years.
It would be very helpful to either add/clarify the old topic as officially supported as well, change the token requirements for the new topic or provide some other way to get the same information with a moderator's token.
Seeing which mod did what is really useful for moderators and they can see all this info in the browser already so it's in no way secret or protected.
It should be officially available to moderators of a channel via the API so it can be used in third party mod tools, mod bots and chat clients which tens of thousands of moderators on twitch rely on (and they all already use the undocumented one anyway).
The old topic (`chat_moderator_actions.<modid>.<chanid>`, only requiring mod auth, announced by Staff on dev forums a few years ago) still seems to work for my app, but I've also gotten reports from other devs that it doesn't work for them, so it's unclear what exactly is going on. It would be great to get some clarification as to the future of this quite important moderation API.