Curious what the use case is that you're needing to block more than 60 an
hour, for one user?
Hugh
On Wednesday, 7 May 2014 09:30:53 UTC+10, Michael Ridland wrote:
You can use the web version with automation, but that still blocks if
overused.
Thanks
Michael
On Wed, May 7, 2014
Sometimes you just decide you hate a lot of folk.
On 8 May 2014 17:35, Hugh Stephens hughsteph...@hughstephens.com wrote:
Curious what the use case is that you're needing to block more than 60 an
hour, for one user?
Hugh
On Wednesday, 7 May 2014 09:30:53 UTC+10, Michael Ridland wrote:
(15 mins
window means only 60 blocks per hour)
Does anyone know why Twitter restricts the number of people you can block
via the API to only 60 per hour?
- https://dev.twitter.com/docs/rate-limiting/1.1/limits
Is there any way of getting around this?
Cheers,
Dean
@googlegroups.com] On Behalf Of UV Hertzog
Sent: Thursday, May 08, 2014 8:09 AM
To: silicon-beach-australia@googlegroups.com
Subject: RE: [SiliconBeach] twitter blocks restricted to 15 per window (15 mins
window means only 60 blocks per hour)
You sure you're reading it correctly?
I know Twitter
Does anyone know why Twitter restricts the number of people you can block via
the API to only 60 per hour?
- https://dev.twitter.com/docs/rate-limiting/1.1/limits
Is there any way of getting around this?
Cheers,
Dean
--
--
You received this message because you are subscribed to the
You can use the web version with automation, but that still blocks if
overused.
Thanks
Michael
On Wed, May 7, 2014 at 9:06 AM, Dean Collins d...@cognation.net wrote:
Does anyone know why Twitter restricts the number of people you can block
via the API to only 60 per hour?
-
