search

serrat839 / mRkov_shiny

GNU General Public License v3.0
28 stars 2 forks source link

Rate limit exceeded #26

Open bryandmartin opened 4 years ago

bryandmartin commented 4 years ago

It was inevitable. We hit our free Twitter API rate limit.

Not much we can do to fix this, except explaining to users how to set up their own Twitter APIs and allowing them to use them as input. Let's add these options when we get the chance.

bryandmartin commented 4 years ago

We can also lower default n. Maybe cap out at 100?

bryandmartin commented 4 years ago

Also possible, if we hit the limit, set token = NULL. Possibly do not need dev account. That would be easy fix

serrat839 commented 4 years ago

I wanna say that the n isn't an issue (n != number of api calls). Maybe we should look at a way of limiting the number of searches a user can do, or somehow allow users to put in their own tokens

bryandmartin commented 4 years ago

I think we may be able to not use a token at all. I'm not sure if that would affect performance at all but it seems we can use token = NULL. Maybe worth testing locally on a few handles to see whether it impacts results at all.