Re: [twitter-dev] TweetDeck technical problem
Hi Patrick, You may find the answer here: http://support.tweetdeck.com/entries/181425-how-do-i-install-air-tweetdeck-in-linux-ubuntu-variants. If not, I suggest asking @desktopdeck to see if they can help. Best, Tom On Sun, May 29, 2011 at 2:37 AM, Patrick Kennedy kenned...@gmail.comwrote: This is not strictly a dev question, but I was hoping others here may be able to suggest or redirect. I have recently started using Bodhi Linux, but I have not been able to get TweetDeck to work on it. Bodhi is based on the Ubuntu distro, but it's a minimalist version, and the user must use apt-get to pull down other software and components. TweetDeck works great on Ubuntu, but I have yet to make it work on Bodhi. I can install AIR and TweetDeck, but when launching TweetDeck the first time, it says: Oops, TweetDeck can't find your data TweetDeck is having trouble using some of your passwords that are stored securely on your machine. Clicking Submit will clear this data so that you continue to use TweetDeck. Please note that you will have to add your accounts to TweetDeck again. OK There is no submit button, per se, but clicking the OK button leads to second dialog box that says: Sorry, Adobe AIR has a problem running on this computer TweetDeck is having trouble storing your passwords securely. Please check the article at http://kb2.adobe.com/cps/492/cpsid_49267.html for information on what may be wrong and how to fix it. OK Clicking OK will only redisplay this second message repeatedly. Clicking the close control button will close the dialog, but it is impossible to subsequently add a user account. I plan to try to contact Adobe, but perhaps someone here may know the issue or can provide a solid reference for help. The question is what component needs to be installed to store passwords on Linux with Gnome? Kwallet is not the ticket (KDE). The gnome keyring service is running, but there appears to be a subsystem missing for the password storage for Gnome Desktop apps. Any ideas? -- 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 -- 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
Re: [twitter-dev] DM enforcement date has been extended to the end of June
On May 27, 2011, at 18:39 , Matt Harris wrote: This makes the new enforcement date Thursday, June 30th, 2011. Thank you Mr. Harris and the Twitter development and policy team team. Anon, Andrew Andrew W. Donoho Donoho Design Group, L.L.C. a...@ddg.com, +1 (512) 750-7596, twitter.com/adonoho When you can't imagine how things are going to change, that doesn't mean that nothing will change. It means that things will change in ways that are unimaginable. Bruce Sterling, January 02, 2009 -- 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
Re: [twitter-dev] DM enforcement date has been extended to the end of June
Hi,
When the new permission is enforced we will return an HTTP 403 Forbidden
error with the response body:
{errors:[{code:93,message:This application is not allowed to access or
delete your direct messages}]}
The format of the error message differs from the one described in the following
page.
http://dev.twitter.com/pages/responses_errors
I'm hoping it to be consistent.
Best,
--
Yusuke Yamamoto
yus...@mac.com
this email is: [x] bloggable/tweetable [ ] private
follow me on : http://twitter.com/yusukeyamamoto
subscribe me at : http://samuraism.jp/
On May 28, 2011, at 08:39 , Matt Harris wrote:
Hey everyone,
We wanted to say a big thank you to the developers who have been sending us
debug information, and details of steps to follow to reproduce device
specific issues. An especially big thank you to those of you who have shared
the changes you made to your applications on the mailing list.
All of this information has helped us to improve the OAuth flow for you and
your users. But, we know that we're getting close to the DM enforcement date
and that some of these new features aren't available to you yet.
We understand this means you might not be able to fully test your updated
flow so we are going to extend the deadline until the end of June.
This makes the new enforcement date Thursday, June 30th, 2011.
Below is a list of the features we are adding in response to your requests
and feedback:
1. Adding the force_login parameter to the /oauth/authorize screen to ensure
the /authorize screen displays a login screen.
2. Adding the screen_name parameter to the /oauth/authorize and
/oauth/authenticate requests. When provided with the force_login parameter we
will pre-fill the username box on the OAuth screen.
3. Adding a Back to app button on the webpage which is loaded if a user
selects no, thanks. When selected the Back to app button will open the
provided oauth_callback URL with a 'denied' parameter. The value of the
denied parameter will be the request_token obtained from the /request_token
request.
For example: http://example.com/callback/?denied=xyz123abc
4. Design updates to the OAuth screens to improve compatibility across
devices.
5. A lightweight OAuth screen flow for devices which are slow or incompatible
with the new screens.
6. A new header on authenticated requests which tells you the access level of
the oauth_token you are using. The header is available now and is called
X-Access-Level. More information for this is available here:
https://dev.twitter.com/pages/application-permission-model-faq
Thanks for working with us to ensure users can make informed decisions about
the access an application has to their account.
Best
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
--
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
--
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
[twitter-dev] Rate limit status keeps decreasing
My rate limit status keeps decreasing to 0 even though as far as I can
tell I am only making 24 requests per hour.
I have a simple PHP web page that calls this 24 times per hour using
CURL:
http://api.twitter.com/1/statuses/user_timeline.json?count=1screen_name={user_name_here}
Responses are cached and logged so a) I shouldn't go over the limit
and b) I can track exactly when the calls are made and confirm my PHP
script is only making 24 requests per hour.
For some reason the rate limit status decreases to 0 after about half
an hour.
Any ideas what I can be doing wrong or if the rate limit can be
decreased by something else other than my script. My script is on a
web site with a dedicated IP address.
--
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
[twitter-dev] Re: Ampersand
It appears to be a bug within Apple's -stringByAddingPercent EscapesUsingEncoding:NSUTF8StringEncoding... solution here: http://simonwoodside.com/weblog/2009/4/22/how_to_really_url_encode/ Now all working fine. Thanks for the responses. -- Ron On May 28, 7:24 am, Sean Heber s...@spiffytech.com wrote: This is OT for this list, but you need to use NSString's -stringByAddingPercentEscapesUsingEncoding: method (or similar) to encode characters correctly for URLs. l8r Sean On May 27, 2011, at 9:10 PM, R wrote: I'm using cocoa and NSUTF8StringEncoding. When I post a sentence that contains the ampersand (), all text that follows is removed from the resulting tweet. How should I deal with the within a sentence (not URL) of a post? Thanks -- Ron -- 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 -- 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
[twitter-dev] Re: Ampersand
Appears to be bug with Apple. Here is solution: http://simonwoodside.com/weblog/2009/4/22/how_to_really_url_encode/ On May 28, 7:24 am, Sean Heber s...@spiffytech.com wrote: This is OT for this list, but you need to use NSString's -stringByAddingPercentEscapesUsingEncoding: method (or similar) to encode characters correctly for URLs. l8r Sean On May 27, 2011, at 9:10 PM, R wrote: I'm using cocoa and NSUTF8StringEncoding. When I post a sentence that contains the ampersand (), all text that follows is removed from the resulting tweet. How should I deal with the within a sentence (not URL) of a post? Thanks -- Ron -- 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 -- 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
[twitter-dev] Some doubts about API
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
[twitter-dev] Tweet Href attribute [location.href]
Hello,
I'm trying to dynamically swap the url I want my users to tweet. I
have a video player with a url of www.domain.com/video. My tweet
button is located on this page. My videos each have their own url
which I use to view them in the player. Using javascript, as each
video is played I add the url of the video into the anchor tag with
docGetById('myID').setAttribute('data-url','MyVideoUrl'). Instead
twitter uses the current url with location.href if the data-url isn't
genuinely coded onto the page. (See my code sample below)
What seems to be happening is twitter doesn't see my changes with
javascript. The actual url needs to be physically coded into the
anchor tag rather than dynamically added by javascript. I've tried
having my javascript execute before after twitter.js, but no matter
what I do it only works when I have the url physically hardcoded into
the anchor tag. I've also tried writing the twitter anchor tag onto
the page, before widget.js with the desired url coded in. No luck.
Sample Code:
a id=myId href=http://twitter.com/share; data-text=
style=height:35 data-count=horizontal data-related=myRelated
class=twitter-share-buttonTweet/a ---Data-url to be added with
javascript
Problem:
If the url to be liked isn't coded into the html of the anchor tag
twitter uses the current browser location with location.href, rather
then my javascript which is swapping the url to be liked in the anchor
tag for the current video being played. (My Page will not refresh)
Questions:
While remaining on a single page, how can I swap the url to be
tweeted?
(I may need to make changes to twitter.js and host it on my server):
Is there an uncompressed, readable version of widget.js? Can I be
provided a link to it?
Is there any long-term negatives to hosting widget.js on my server
rather than have the.src point to platform.twitter.com?
--
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
[twitter-dev] Re: Twitter Search Widget on iPad
Not much help to you but I've noticed the same thing on IPad2, IPad1 and IPhone/IPod etc. Safari on a PC works fine, the same as other browsers, but on mobile devices it doesn't seem to show scrollbars. FYI there is a discussion about this problem Scrollbar missing on Safari Mobile which you can follow but there is no solution. One thing which they suggest which does work for me (IPad2) is to use the 2 finger resize gesture, within the list, which does allow you to scroll but it's not easy to find the sweet spot that scrolls the list as opposed to resizing. On May 18, 1:42 pm, Phil Johns p...@pjstudio.co.uk wrote: Hi All, I recently launched this website:http://makesmyjobeasy.com I have had a few people tell me that the scroll bar visible on the right of the twitter search widget used to move the tweets up and down so you can see the rest doesnt appear on the Safari iPad2 browser (unsure about ipad1). Anyone shed some light onto why or is this just standard?!?! Thanks, Phil -- 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
[twitter-dev] list/statuses
Now I have a public list that includes private accounts. I'm retrieving the result by calling statuses.json. The list is followed by a few people. I have a gadget on my site which retrieves the latest statuses. The private tweets are left out, which is fine by me, but they're taking the place of the public tweets. Which means if for example the 20 latest tweets on the first page of the results contain 19 private tweets you get only one tweet back. I do not want to remove the private accounts from the list because the people following the list can see this private tweets on twitter.com. How can I exclude the private tweets from the query so that my results of the latest 20 tweets contain 20 public statuses? -- 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
Re: [twitter-dev] problem in Posting a tweet using OAuth from IOS app
I assume that your URL encoding is wrong in the OAuth code. Make sure
that you use %20 for a space and not +. The standard NSString URLencode
function won't really work.
Code that has always worked for me to URLencode (got it from the web
somewhere, sorry for not mentioning the original author) :
+(NSString*)urlEncode:(NSString*)str {
return [(NSString *)CFURLCreateStringByAddingPercentEscapes(
NULL,
(CFStringRef)str,
NULL,
(CFStringRef)@!*'();:@=+$,/?%#[],
kCFStringEncodingUTF8 ) autorelease];
}
Tom
On 5/28/11 1:25 PM, Ayman Adel wrote:
I am building a twitter client for the IPhone and I'm using OAuth to
authenticate my requests to twitter,
Right now I am able to get the home time line and even post tweets
( that do not contain any spaces or symbols) the problem starts when I
try to post a tweet that contains spaces for example it gives me :
{error:Incorrect signature,request:\/1\/statuses\/update.json}
For example the tweet : ThisIsATweet works, but the tweet : this is
a tweet doesn't work here's my http request body code:
code
NSData* body =[NSString stringWithFormat:@status=%@,[self
percentageEncoding:tweet]];
[request setValue:@application/x-www-form-urlencoded
forHTTPHeaderField:@Content-Type];
[request setValue:[NSString stringWithFormat:@%d,[body length]]
forHTTPHeaderField:@Content-Length];
[request setHTTPBody:[body
dataUsingEncoding:NSISOLatin1StringEncoding]];
/code
--
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
Re: [twitter-dev] list/statuses
You can't. The 20 is the number of tweets received from Twitter's database. It will then simply not send the ones which come from private users, deleted ones (?), retweets, etc. If you want 20, ask for 50 and limit it yourself. Tom On 5/29/11 11:20 AM, ogierepier wrote: Now I have a public list that includes private accounts. I'm retrieving the result by calling statuses.json. The list is followed by a few people. I have a gadget on my site which retrieves the latest statuses. The private tweets are left out, which is fine by me, but they're taking the place of the public tweets. Which means if for example the 20 latest tweets on the first page of the results contain 19 private tweets you get only one tweet back. I do not want to remove the private accounts from the list because the people following the list can see this private tweets on twitter.com. How can I exclude the private tweets from the query so that my results of the latest 20 tweets contain 20 public statuses? -- 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
[twitter-dev] Limit on sending DMs to opt-in users
I have a client who needs the following scenario: - Many users, potentially thousands or tens of thousands, will sign up to receive a daily DM from the client's site. With a limit of 250 DMs per day, the client wants to use each user's account to send a DM to that user. - These users will give the app permission to send DMs to their account through OAuth. - The app will use each user's OAuth credentials to send 1 DM to that user each day. So, John signs up and allows DMs with OAuth. John's OAuth tokens are used to have John's account send a DM to John. Question 1: Is it technically possible to send a DM to @john using the OAuth tokens for @john. Question 2: Is this model limited to 250 DMs per day? If the answer to question 1 is yes, it seems that this is really just 1 DM per account per day. Is this true, or is the app's account used to total up the DMs for the limit. Answer to expected comments: yes, I know the client could use email. They want to use DMs. They want this to be a Twitter system and feel that DMs let them stay within Twitter. -- 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
[twitter-dev] Re: Will requesting DM access now disable xAuth for my app?
I poured a 4-shot breve latte just in case, flipped the switch at https://dev.twitter.com/apps, and was delighted when: - shipping Twittelators already deployed can use and continue to get valid RW XAUTH Tokens - those XAUTH tokens still work - New RWDM tokens are correctly given to new in-house builds of Twittelator So, I can totally relate to the feeling of Am I about to hose 1 million users? but, especially with the enhancements due this week from Twitter, I think we can all make a smooth transition to the new flow. On May 27, 11:31 pm, Ed Finkler funkat...@gmail.com wrote: Fellers, For testing as we prep our apps for the switch to PIN-based auth, I'd like to change the default access level to Read, Write, Private Message. However, I'm concerned this will disable xAuth for existing users immediately, rather than once we hit June 30. Can I do this, or should I register a new application? Or do I have other options? Thanks, -Ed -- 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
Re: [twitter-dev] Re: Will requesting DM access now disable xAuth for my app?
Thanks for being my guinea pig! 8D -- Ed Finkler http://funkatron.com @funkatron AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.com -- Ed Finkler http://funkatron.com @funkatron AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.com On Sunday, May 29, 2011 at 12:49 PM, twittelator wrote: I poured a 4-shot breve latte just in case, flipped the switch at https://dev.twitter.com/apps, and was delighted when: - shipping Twittelators already deployed can use and continue to get valid RW XAUTH Tokens - those XAUTH tokens still work - New RWDM tokens are correctly given to new in-house builds of Twittelator So, I can totally relate to the feeling of Am I about to hose 1 million users? but, especially with the enhancements due this week from Twitter, I think we can all make a smooth transition to the new flow. On May 27, 11:31 pm, Ed Finkler funkat...@gmail.com (http://gmail.com) wrote: Fellers, For testing as we prep our apps for the switch to PIN-based auth, I'd like to change the default access level to Read, Write, Private Message. However, I'm concerned this will disable xAuth for existing users immediately, rather than once we hit June 30. Can I do this, or should I register a new application? Or do I have other options? Thanks, -Ed -- 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 -- 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
[twitter-dev] Re: TweetDeck technical problem
I'm using 32-bit platform in this case; AIR seems to install fine. I will try @desktopdeck and see what they think. I have installed Tweetdeck/AIR on 64-bit Fedora before and used similar info as you provided to make it work. However, as noted, I'm only using a 32-bit platform. Thanks. On May 29, 3:24 am, Thomas Woolway priv...@tswoolway.co.uk wrote: Hi Patrick, You may find the answer here:http://support.tweetdeck.com/entries/181425-how-do-i-install-air-twee If not, I suggest asking @desktopdeck to see if they can help. Best, Tom On Sun, May 29, 2011 at 2:37 AM, Patrick Kennedy kenned...@gmail.comwrote: This is not strictly a dev question, but I was hoping others here may be able to suggest or redirect. I have recently started using Bodhi Linux, but I have not been able to get TweetDeck to work on it. Bodhi is based on the Ubuntu distro, but it's a minimalist version, and the user must use apt-get to pull down other software and components. TweetDeck works great on Ubuntu, but I have yet to make it work on Bodhi. I can install AIR and TweetDeck, but when launching TweetDeck the first time, it says: Oops, TweetDeck can't find your data TweetDeck is having trouble using some of your passwords that are stored securely on your machine. Clicking Submit will clear this data so that you continue to use TweetDeck. Please note that you will have to add your accounts to TweetDeck again. OK There is no submit button, per se, but clicking the OK button leads to second dialog box that says: Sorry, Adobe AIR has a problem running on this computer TweetDeck is having trouble storing your passwords securely. Please check the article athttp://kb2.adobe.com/cps/492/cpsid_49267.htmlfor information on what may be wrong and how to fix it. OK Clicking OK will only redisplay this second message repeatedly. Clicking the close control button will close the dialog, but it is impossible to subsequently add a user account. I plan to try to contact Adobe, but perhaps someone here may know the issue or can provide a solid reference for help. The question is what component needs to be installed to store passwords on Linux with Gnome? Kwallet is not the ticket (KDE). The gnome keyring service is running, but there appears to be a subsystem missing for the password storage for Gnome Desktop apps. Any ideas? -- 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 -- 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
Re: [twitter-dev] Some doubts about API
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
