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:
You sure you're reading it correctly?
I know Twitter throttle any API call down to 15 per window which limits the
number of API calls to only 60 per hour, but in each BLOCK call you can
stringify multiple ids
(https://dev.twitter.com/docs/api/1.1/get/blocks/ids).
I'll ask my developers for
Thanks UV,
Basically the developer I'm working with is saying even if we have a large list
of people you want to block the maximum is 15 per 15 minute window..its
pretty slow going at this rate.
Cheers,
Dean
From: silicon-beach-australia@googlegroups.com
geoff.mcqu...@affinitylive.com wrote:
You're right - not everyone is crazy busy. Some people are time rich doing
the 4 hour week thing and building a lifestyle business.
You seem to have a common misconception that the only representation of
resultant value is generated by is slogging it
I'm a net beneficiary (rather than contributor) to the Australian startup
scene, so my views on this issue shouldn't carry much weight. Nevertheless,
here they are:
* When StartupAus was announced, with Google in the lead, my first thought
was hijack. Lots of individuals had done a lot of hard
