i was wondering if you are planning on adding some kind of functionality to give us information on how long a subscription is valid, e.g. a timestamp, datetime or whatever.
I’m asking because the website I’m building has a special subscriber area. This area should obviously only be accessible if you are subscribed to a specified channel. Right now I have to make an API call every time the site get refreshed to find out if the navigation bar should include a link to the subscriber area or not. If there was a way to see how long the subscription is valid I could add this information in my database and refresh this information every time the user reauthenticates with twitch. Obviously on the subscriber page itself I would make an API call to get “live” data about subscription status.
Normally I wouldn’t care about making an API call every time the site gets refreshed but especially the subscription call - in my opinion - takes really long and slows the web app down a lot. As a workaround I added the subscriber area link asynchronously by using jquery and making a call the Twitch API in background. Sometimes the page is fully loaded but it takes up to 5 seconds until the sub link gets added from the async call.
From what I get the “Recurring Payment Date: xx/xx” should be exactly the information needed in the API.
How many days after a user’s subscription ends are they removed from the API channel_subscriptions? (either because they ended paid subscription or did not resub on their Prime subscription)
I have a Prime viewer whom I know has not resubbed. They subbed on May 3 but they’re still appearing in API as of June 4.
Refresh the Subscription data for the user when the user logs in. And keep the session times to a day instead?
Or, if you have channel permission, refresh you channel subscribers once (or maybe four times a day) and just allow that “free” access for that “short” timer period?
Theres usually a small window of delay for clearing up a sub, it’s weird but it should be dead, but seems to have a window
Currently the only way to calculate is to iterate over all the subs, but I think that sub points is gonna get added to the API as a few people have requested it. Who knows
twitchnotify was deprecated regardless, so 99% sure it will still be through USERNOTICE. The only change is that sharing/announcements will now be automatic for first time subs.
Yeah I wasn’t too sure on how they’d approach that but possibly 2 separate messages? Or something like: you get 24hrs to share with a message, but after that it gets shared without one? We do still need confirmation like @iamthem00s3 said and hopefully we can get one soon.
I was just saying it’s highly unlikely they’ll go back to twitchnotify.
TLDR:
TwitchDev: FYI, devs, this means that first-time subs will send USERNOTICE and PubSub immediately with an empty message. Resubs are the same as before. twitter.com/TwitchSupport/…
They confirmed on Twitter new subs won’t get to send messages - https://twitter.com/twitchdev/status/872248710901760000 so basically nothing changes apart from people can’t send first time sub messages. Remains a USERNOTICE/PubSub.
Correct info above. Basically, first time subs are sent over USERNOTICE and PubSub at the same time as twitchnotify was sent previously. First time subs will not be able to share a message. Resubs are the same.
I think Twitch will probably end up putting a message field before a final confirmation on first subs. Though differentiating first subs from resubs might be a bit tricky! Oh well, can’t wait to see what Twitch’s devs decide to do!
Just about to start work on a WordPress plugin that integrates Twitch subscriptions with the Ultimate Members plugin. These changes open the door to a range of features for popular streamers to use in a WP site and pull traffic to their own domain. Another step towards streamers owning their community and offering an actual service tailored to suit their style.
So glad this has gone (is going?) back to default behaviour!