@DallasNChains So there’s currently not a way to distinguish if someone is a Prime sub via API?
In the PubSub example, “prime” is listed as one of the sub_plan options.
@mko0mko0 Correct. PubSub and chat have the differentiator but the API doesn’t.
With the fact that a user can appear multiple times in the list of subscriptions for a partnered streamer (with different sub_plans), will there be an endpoint to have the chronological events of subscriptions (instead of the current behavior, which is keeping the first subscription and not deleting it until it expires), which would help determine the amount of months a user has been subscribed to a channel ?
I guess it would be close (but different, due to subscription time != announce time) to a non-live version of the new pubsub topic.
Does this still work?
Yes @parswagg, I am currently using that script.
I think many will support me, I would like to twitchnotify remain, or rather, would remove for example the display that the user sub/resub, but left the notification itself. My bot collects statistics on users, it has its own database. I would like the bot to know that the user subscribes, without notifying the chat, think about it please.
Your bot can still know when a user subscribes by polling the subscribers endpoint for the channel and looking for changes.
so far unless a user refreshes and hits the button new subs only show up with twitchnotify - will the initial sub now go out over usernotice or is that ability just going to be lost ?
There are so many people who don’t know you have to refresh and announce for their subs to show up - our channels especially are landing points for new users from outside of twitch. This will confuse people a LOT more if we can’t grab initial subs without derping around through the API.
@DallasNChains This will seriously confuse all new users to twitch, can we at least look at a way that leads new subs through the “Announce button” path? Having to go back and refresh to announce is something NO new twitch user would ever think of.
I’ve been setting up a bot in C# to listen to the PubSub WebSocket for new subscriptions. So far I haven’t been able to test it as much as I’d like, but I’ve been looking at chat and noticed something odd…
A $4.99 resub got sent to my bot as expected, but a (new) prime sub didn’t seem to register at all. Is there a different topic for this I need to listen to or is there something else I’m missing?
Edit: After some further testing I noticed that anything that isn’t a fresh new Prime sub is going through as expected. That said, I did detect some Prime subs that had a streak of 1; essentially also new. Those might have been returning sub that let their subscription expire before re-upping with Prime, but I can’t verify that right now. In any case, I’m still seeing a lot of new Prime subs in chat that aren’t being registered in the PubSub that I’m listening to.
Are these messages:
[twitchnotify] 11 viewers resubscribed while you were away!
Gone forever then? I don’t see any mention of them in the updated documentation.
1 Like
@WittyAdrian Are they being registered over twitchnotify? PubSub and USERNOTICE only happen when the user decides to share.
@iamthem00s3 I do believe those are gone. I’ll check with the team.
I’m just using PubSub to register these subscriptions, so that could explain it. Assuming the messages in Twitch chat are being driven by twitchnotify, it would make sense that the two aren’t always totally in sync.
Is there any way to detect every new sub with the new system? Ideally just using PubSub as I have that running already.
@DallasNChains I switched over from twitchnotify to the USERNOTICE for new subscribers in my code, however it appears that some new subscriptions coming in are only being received via twitchnotify, and no corresponding USERNOTICE. I presume this is not intended?
@Ninja101 Are you sure the users that you are not receiving a usernotice for are simply not clicking the share button after subscribing? as if they don’t then there wont be any notification (other than twitchnotify, which will soon be gone).
@Dist Okay yeah, that was it. The subscriber never clicked Share before complaining ._.
Still failing to see the benefit to removing twitchnotify then - Losing features and ‘privacy’ concerns can be circumvented by polling the API anyway so, I dunno, just would like to understand why ?
What features have you lost exactly? Things have to be done differently, and if your app wasn’t prepared for it then it might be an inconvenience for you, but you can still do everything you used to be able to do. As for the benefits, some have been mentioned in this thread already, if none of them help you in any way then there’s no helping that, but for other developers, streamers, and viewers, it’s a nice little change 
with appropriate authorization from the broadcaster.
Sounds like you are breaking the developer TOS… Collecting and storing anonomous data about a channel.
Use the provided scopes to fetch data.[quote=“Ninja101, post:77, topic:10023”]
I switched over from twitchnotify to the USERNOTICE for new subscribers in my code, however it appears that some new subscriptions coming in are only being received via twitchnotify, and no corresponding USERNOTICE. I presume this is not intended?
[/quote]
Means the user has not announced their sub yet, the same as a resub does, either they are lurk subbing, or just not hit the button.
TWITCHNOTIFY fires Immediately when payment clears, usernotice and pubsub when the user presses the purple button and leaves a message.
Basically just IGNORE TwitchNotify completely/pretend it doesn’t exist and it’ll solve your confusion
Twitch now has ONE code path to announce subs/resubs, no matter how they subbed or what kind of sub it is, in addition we only have to test a nice JSON packet.
No idea what “feature” we are losing here… Subs and Resubs are still announced over pubsub.
Also fixes the “issue” about getting the “English” name when a user has a “international display name” for new subs, as it’s right there in the packet.
So am I correct in assuming that there is no way to receive every single sub (regardless of user preference in sharing) in the PubSub? And the only subs you will receive in there are the ones that those users chose to share?