@jbulava EventSub still has a lot of outstanding issues, that I hope can be fixed switftly. For example, there are a lot of instances in the docs of mismatched types between example and type. One instance is EventSub Subscription Types | Twitch Developers where the example shows duration_seconds as…

[image] danthegoodman: Secondly, there are event missing crucial data, like EventSub Reference | Twitch Developers not including information about the gift recipient. This causes us to have to create a lot of hacky workarounds that are not fool-proof, and cause a lot of turbulence for both our d…

It’s also irritating that situations like resubbing after a sub expires sends both a new sub event, and a resub event. Again, this results in more hacky deduplication implementations for our Alerts. It’s exacerbated by the fact that Twitch sends the new sub immediately, but the resub only after they…

That doesn’t solve the other issue I just mentioned above. Also, events should be complete and correct, not abandoned. We’ve been moving events over to that, but I still think they should fix broken examples and missing properties in events

[image] danthegoodman: It’s also irritating that situations like resubbing after a sub expires sends both a new sub event, and a resub event. Becuase that is what actually happens. The user stops being a sub for whatever reason, so a unsubscribe is sent Then they realise and restart payment…

IIUC there is also no way to distinguish a prime sub in EventSub, that’s another pain. We never used PubSub, because that model doesn’t work as well for server-side managed reactivity to events. IDK if I’d consider it debatable, it’s clearly missing critical information required for the standard fu…

[image] danthegoodman: IIUC there is also no way to distinguish a prime sub in EventSub, There is on channel.chat.notification which is why I’m saying thats the migration path. channel.chat.notification is USERNOTICE as a topic so has Prime [image] danthegoodman: We never used PubSub, b…

I’ve been using PubSub for server side events for 10 years. Since I started doing overlays so I’ll disagree there. When you scale out to multiple servers, coordination becomes a massive PITA. I think if you have to rely on live events rather than documentation (which we also do when we can, but …

If the new chat events truly solve everything, they should plan to remove the others. That will probably break a lot of unmaintained integrations though (which I’m sure PubSub deprecation will too)

[image] danthegoodman: If the new chat events truly solve everything, they should plan to remove the others. Different topics have different use cases, so it doesn’t make sense to retire a topic. Sure those topics that are dry on data just need to be enhanced, I would assume that the underlyi…

PubSub deprecation feedback: danthegoodman

API

BarryCarlyon April 14, 2024, 11:54am 2

This issue is solved by using the chat notification topic instead as I answered earlier:

Topic		Replies	Views
EventSub vs PubSub for subscription events API	2	2926	January 6, 2021
PubSub deprecation feedback: ckohen API	6	329	April 14, 2024
Channel.chat.notification subscription type - not receiving resub events API	2	224	December 17, 2024
EventSub : Sub streak API	14	1055	September 14, 2021
Subscriptions Beta Changes API	119	20290	July 9, 2017

PubSub deprecation feedback: danthegoodman

Related topics