Summary:
Filling in the holes of what chat provides and EventSub provides would be appreciated. In this case hosts, raids, and potentially front page promo attributions. There isn't much reason to have multiple unique events in this case as all of the aforementioned events are the same, a provider of a redirect (user), a recipient (broadcaster), and an attribution amount (viewers attributed to the event). The only specifier needed is a type or context. However, different events wouldn't be necessarily rejected in concept, it would just seem unnecessary. Since a condition is sent for the subscription to the event, one could use this to focus on which type they want to receive.

New Topic(s):
- channel.redirect

Structure:
event: {
public string userid;
public string username;
public string userdisplayname;
public string broadcasteruserid;
public string broadcasterusername;
public string broadcasterdisplayname;
public string type; //auto host, host, raid, front page promo (twitch would be the user in this case)
public int amount; //viewers attributed to the redirect
}