Thanks,
Why no more than 10 per hour? I think it's not hourly limited, because I
tested it sending up to 250 messages to a friend in 10 minutes and all was
received.
In the other hand, 8/hour is a good rate, about 190 DM (invitations for the
event) is enough for almost everybody.
What do you think?
2011/5/29 Tom van der Woerdt i...@tvdw.eu
250 per day per sending account, spread over the day. Try not to send more
than 10 per hour, although I think Twitter divides it in blocks of 4 hours.
Better way? I'd say that you shouldn't use Twitter for this. :-)
Lifetime of tokens: infinite until revoked.
Also, yes you can report an user as spam, but you shouldn't report a
Twitter user for things they do on your site.
Tom
On 5/29/11 2:25 AM, dnog wrote:
Hi,
I'm planning to build a tool to convocate events, like events on
Facebook, but Facebookless, just for twitter users.
There is any limitation (added to the 350req/h rate limit) sending
direct messages?
Is there any better way to notify users?
What is the lifetime of the tokens? Can I store it in a DB for example
(if infinite lifetime)?
Finally, if somebody make a SPAM event, blocking is enough or there is
any mechanism to notify Twitter the problem and block the user?
Thanks
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Daniel Doña Álvarez - Visit www.qk6.in
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
