After a webhook fires, I'm given context to the UserID and Username. In the instance of "stream.online", I would like more information. In the old webhooks, I was given the full stream data object. Will there be a standard way of accessing the full data object of whatever is "notifying" the webhook? Or is it on me to use the existing Helix API to then get that information(user info, game info, broadcast info)?

One thought would be to simply give the appropriate URL to POST to for more information, similar to how some APIs give a paginated cursor URL to access "more" info.

My fear is that switching to the new webhooks is going to increase my API usage significantly since I will generally need the full data object after any event.

Please provide an eventsub topic that notifies when the extensions active on a channel change.

The payload should match what https://dev.twitch.tv/docs/api/reference#get-user-active-extensions outputs.

For a broadcaster tool we generally wouldn't need to know what the change was. Just what the current config with.

This would save two payloads (for an extension changing from panel 1 to panel 2)

It would be useful to know what changed but less important.

So add a "was_changed" boolean to the relevant record.

So

    "component": {
      "1": {
        "active": true,
        "id": "lqnf3zxk0rv0g7gq92mtmnirjz2cjj",
        "version": "0.0.1",
        "name": "Dev Experience Test",
        "x": 0,
        "y": 0
      },
      "2": {
        "active": false
      }
    }

becomes

    "component": {
      "1": {
        "active": false,
          "was_changed": true
      },
      "2": {
        "active": true,
        "id": "lqnf3zxk0rv0g7gq92mtmnirjz2cjj",
        "version": "0.0.1",
        "name": "Dev Experience Test",
        "x": 0,
        "y": 0,
         "was_changed": true
      }
    }

In this example both componet slots are marked "dirty". And in this example we swapped which slot the component extension was active in.

Now that Subscription Limitations are capped by a "Cost", it would be nice to have these subscriptions disable themselves automatically, rather than ever applying to the limit.

IE; I never make any subscriptions to events, unless I have authorization from that channel. When that channel revokes authorization, private events that require authentication (Such as subscriptions) get disabled. Public events, such as stream up/down do NOT get disabled, but instead start having a cost against my limit.

I would rather ALL subscriptions get disabled, not just private ones.

Otherwise I need to handle disabling subscriptions after a REVOKE is made on my end.

This is something with the intention for client rather than server side.

So the idea is to subscribe to the streams.online topic but instead of specifying a broadcasterid you specify a userid. This topic would give the streams.online notifications for the broadcasters that the user is following and has notifications enabled for. You could subscribe to streams.online for each broadcaster a user is following which is indeed a possibility but at the same time cause a problem as some people follow a good 200-300 channels of which for quite a lot they probably don't even have notifications which is something we can only check with v5 and probably won't be on helix. Which at the rate v5 is shutting down we would probably be good till 2021 but then we would start to give them notifications for all streamers and would probably need a insane high maxtotalcost to catch up with users that follow a insane amount of channels. Which is why I would like to see a topic that does stuff the other way around perhaps hidden behind a scope or something because internally within twitch there already exists something for it I mean there's gotta be something that's triggering the onsite and mobile notifications and send out emails for the channels people have notifications enabled for.

Possible use case:
Users can sign in with Twitch to a custom minecraft client or use a mod for minecraft or any other game can receive live notifications ingame via the in some games already existing notifications system.