This seems like an amazing change. I know I for one would absolutely love for this to be implemented, and it would make it really easy as my application grows as to not have to put in a limit increase request.
My only other interest that I’d like to see added is a way to automatically delete subscriptions once a revocation has been made.
A subscription’s “cost” will automatically update if the user grants or revokes authorization from your application.
If an update to a subscription’s '“cost” causes the value of “total_cost” to exceed “max_total_cost,” the offending subscription may be revoked.
I for one don’t subscribe to any Events for users that haven’t authorized my application, especially now that CLI exists for testing events. I know previously some developers would subscribe an event to larger streamers either for testing of events, or for stress testing their notification systems.
With this change I could listen to the Revoke event, and then manually delete events that now have a cost to them. But this is additional resource use, such as bandwidth, API request-per-second limitations, etc.
It’d just be nice to delete any events related to a user as soon they revoke, rather than the cost ever increasing.
Otherwise, I’m with Barry. Best change.