-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
donreach.com share count API, limit of 1000 API requests per hour #24
Comments
Thank you @efernandesng, I had not noticed that they had put a limit. |
Hehe I'm just running into the same problem.
@olahol just to know, what do you plan to do on this subject? Not that I'm in a hurry but as I'm building a feature I'd like to know if I can count on count or if I'd rather remove the counts temporarily. BTW they seem to support Twitter for Count, is there a reason why this project does not expose a Twitter Count? |
@slorber at first I am going to add a warning about the limit in the readme. After that I will look for an alternative or hope that Google re-enables their count endpoint 😨 You are right that I should re-add TwitterCount with donreach. |
thanks @olahol . Isn't the count exposed by each social network? Is it really required to use a service to get the counts? |
Sadly not, twitter turned off their count api in October https://blog.twitter.com/2015/hard-decisions-for-a-sustainable-platform . And Google Plus does not expose a JSONP api anymore. |
Ohhh I see, no twitter count! (btw maybe donreach twitter count does not work then...) Is it really required to use JSONP? it's for CORS security reasons or something like that? |
Usually CORS isn't turned on and you have to use something like https://anyorigin.com to circumvent it. |
We regret to inform you that due to a massive rise in popularity of our service we've had to implement a rate limit of 1000 API requests per hour. If you require more requests please contact us to discuss premium or dedicated options.
In most cases, this is not a problem.. but an issue.
The text was updated successfully, but these errors were encountered: