Subscriber points are now accurately fetched from Twitch.
Subpoints are now cached for 1 minute instead of 2 minutes.
This is a shared cache between "subcount" and "subpoints".
The subtract parameter is now ignored, as the accurate subscriber points are given by Twitch's API.
Subcount
Subscriber count is now using the Helix API instead of Kraken V5.
Subcount is cached for 1 minute and is part of a "shared" cache with subpoints.
Accountage
Accountage now uses Helix and caches the created_at timestamp (containing the date & time of when the account was made) for up to 6 hours. This timestamp is shared with creation.
The "cache" does not mean that the same response will be 'wrong' for up to 6 hours, but there may be extremely rare scenarios where you get a wrong response, such as:
Account suspensions (banned account still has a valid accountage)
Username changes (old username still works)
Creation
Creation now uses Helix as well. Similarly to accountage, the created_at timestamp containing the creation date & time of the account is cached for up to 6 hours, which is shared with accountage.
Related to issue #22
The following endpoints have changed:
Subpoints
subtractparameter is now ignored, as the accurate subscriber points are given by Twitch's API.Subcount
Accountage
Accountage now uses Helix and caches the
created_attimestamp (containing the date & time of when the account was made) for up to 6 hours. This timestamp is shared withcreation.The "cache" does not mean that the same response will be 'wrong' for up to 6 hours, but there may be extremely rare scenarios where you get a wrong response, such as:
Creation
Creation now uses Helix as well. Similarly to accountage, the
created_attimestamp containing the creation date & time of the account is cached for up to 6 hours, which is shared withaccountage.