Re: [twitter-dev] Facilitating one-click login with OAuth
Hi Biggs, I think what you're looking for is sign in with twitter. Check out this help doc: http://dev.twitter.com/pages/sign_in_with_twitter -- Thomas Mango On Dec 14, 2010, at 7:32 AM, BigglesZX biggle...@gmail.com wrote: Hi all, First off apologies if this has already been covered somewhere, but I've been struggling to find the correct nomenclature and therefore haven't been able to find anything relevant with a search. I'm using OAuth to connect Twitter users with my app and it's all working great. However I noticed this week that when I use my Twitter account to log in at (for example) TwitBlock (http:// www.twitblock.org/) I am instantly redirected back to the app because I have already approved access for this application. Conversely, when I log into my own application I get presented with the Authorize Access Twitter page regardless of whether or not I've already approved my app for access. Am I missing a setting somewhere? I've already selected use Twitter for login as suggested by a friend, but this doesn't seem to have changed anything (I made this change about ten minutes ago). This is a CakePHP app and the library I'm using for OAuth is this one (http://code.42dh.com/oauth/), FYI. Please let me know if I can help by providing any further info. Thanks for reading! Biggs -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] String IDs in keyless JSON arrays
The last mention of this I saw was here: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/92ff8f4b9eae5293/4d298d877ec5de3b I haven't used it, but the stringify_ids parameter looks like it will (already does?) convert the response to an array of strings. Tim wrote: I noticed a short while ago that keyless array responses, e.g. [182097517,183706717,...] were switched to string IDs, e.g. [182097517,183706717,...] Example method blocks/ids This appears to have reverted to integer IDs. I switched my code to take advantage of the change, and I have to switch back to fix my app. What's the official word on this, please? -- Thomas Mango tsma...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] URGENT: Advice on building the correct API stream
Just wanted to chime in quickly. I've been using Site Streams in production for over a month now and have found them to be absolutely fantastic. Really rock solid. If Site Streams are indeed what you're looking for, I wouldn't let the beta tag scare you away. Taylor Singletary wrote: Hi Neil, What are you particularly trying to accomplish with your Twitter Integration? How are tweets used in the application? What APIs were you leveraging when you were planning a REST-only solution? While Site Streams is officially beta right now, it's very reliable -- but whether it's the right solution for you really depends on what you're looking to accomplish. Thanks, Taylor On Tue, Nov 16, 2010 at 1:32 PM, Neil sheth.n...@gmail.com mailto:sheth.n...@gmail.com wrote: We have previously raised a request to obtain twitter whitelisting but have been told by Twitter (Brian) that we have built the wrong solution. Our developers are struggling to understand which solution they need to build for our site www.mystweet.com http://www.mystweet.com in order to get whitelisted. They have stated that they are unsure which one to choose: 1) http://dev.twitter.com/pages/site_streams - twitter recommend this for the kind of solution which we want to implement, but this is still in beta 2) http://dev.twitter.com/pages/user_streams_suggestions - but this is not what they would allow for our case. Can you please advise what solution needs to be built? We're hoping to correct this before they go on their holidays Thanks PREVIOUS EMAIL FROM BRIAN Hi Jessel, Sorry about this! There is currently an issue that removes the rejection reason from some whitelist emails. Your requests have rejected because we encourage you to use our Streaming API instead to accomplish your purposes. As described onhttp://dev.twitter.com/pages/streaming_api_methods http://dev.twitter.com/pages/streaming_api_methods , you may use the statuses/filter method with the follow parameter to receive a real-time stream of tweets from all the users you're interested in. I apologize for any inconvenience this causes to your project. Thanks for your understanding, Brian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Thomas Mango tsma...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Response format details?
Hey, Colin. An easy way to test API calls and see their response is by using the console (you need an app registered): http://dev.twitter.com/console Or by getting a copy of twurl to use locally: http://github.com/marcel/twurl Colin Howe wrote: Hi, I can't find any documentation on the response format for anything that returns tweets. E.g. http://dev.twitter.com/doc/get/statuses/mentions Is there any documentation of what the response looks like and what each field means? Specifically, I'm looking for information on when in_reply_to_[status| user]_id are populated and what they are populated with. Thanks, Colin -- Thomas Mango tsma...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Search Home Time Line
The home_timeline API method returns up to 800 statuses: http://dev.twitter.com/doc/get/statuses/home_timeline João Paulo Sabino de Moraes wrote: Thanks for replying So, is there a limit of home time line tweets that can be got ? thanks -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Thomas Mango tsma...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: User Streaming API and use of OAuth from web browser
xAuth is actually for exchanging usernames and passwords for OAuth keys. In the end, all of your requests are still using OAuth. More about xAuth: http://dev.twitter.com/pages/xauth Jonathon Hill wrote: Have you looked at xAuth? It was designed for desktop clients but it may work well with Javascript clients. Jonathon Hill On Oct 6, 4:54 pm, Tim Bulltim.b...@binaryplex.com wrote: Hi, We are building an application client that is browser based. We're very comfortable with using OAuth from our server side code and are using it fine with the REST API (users sign in, authenticate with Twitter, we store their access tokens and reuse as requested - at the moment we mimic the required Twitter API on our server and when a user does something like a POST, we call our stub, use their token to then make the call via OAuth to Twitter). So far so good, but we'd like to implement User Streaming directly into the client side application. I've been browsing the Twitter Development documentation and there's a couple of points I'd like clarification on: *http://dev.twitter.com/pages/auth_overviewsays Streaming supports Basic and OAuth. *http://dev.twitter.com/pages/user_streamssays that the user streams supports OAuth only HTTPS, OAuth and JSON only. No problems here, I just raise it to point out the auth_overview doco is slightly out of date. *http://dev.twitter.com/pages/oauth_librariestalks about a JS library but says Javascript really shouldn't be used for OAuth 1.0A with respect to websites in web browsers. Ideally, you'll only use Javascript to perform OAuth operations when using server-side. The points I'd like some clarification on: 1. Given user_streams API is the intended way for clients to access Twitter going forwards, I presume it's intended not just for desktop, but also web clients too? 2. If 1 is correct, then is it OK to use JavaScript for the OAuth? If it's not, what is the recommended approach for a client side web application to connect and authenticate to the user_stream? Thanks, Tim -- Thomas Mango tsma...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Use twitterapi.update method to my own account via .net web app without human intervention
You should save the oauth access key/secret you get for the account you want to post to (if it's your application's account, you can get the access keys from the application's page on dev.twitter.com). You can then use your client key/secret and user access key/secret to make calls to the API on that user's behalf without them logging into an actual session of your application. This page is a good overview of OAuth: http://dev.twitter.com/pages/auth bob wrote: I have an application that maintains sport fields playing status. When it rains, I'd like to update my account to show the closures via my .net application. Problem is when using oAuth, I must sign in to allow the app access to my Twitter account. Is there any way that oAuth can do this without needing this step. -- Thomas Mango tsma...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: How to test for one user following another
I apologize, I was actually saying that you should specify both the source and the target. It was my understanding you needed both, but it looks like when you make an authenticated request (like you do with twurl), you can specify just the target. With that said, I was able to use twurl and specify only the target and get it to work: twurl /friendships/show.xml?target_screen_name=Alternate1985 This used my authenticated user, @tsmango, as the source and gave me the proper response. Is that what your twurl call looked like? Also, if you don't quote the query, you'll have problems with multiple parameters: This one works: twurl /friendships/show.xml?source_screen_name=samvermettetarget_screen_name=Alternate1985 But this one fails with the error you were receiving: twurl /friendships/show.xml?source_screen_name=samvermettetarget_screen_name=Alternate1985 Hope that helps and sorry again for the confusion about needed to specify the source. Joe Rattz wrote: That doesn't work either: hash request/1/friendships/show.xml/request errorTarget user not specified./error /hash That's right from Twurl despite the fact that I provided both the source_screen_name and target_screen_name. Besides, why shouldn't the other two methods work? They are documented methods. On Oct 7, 7:09 pm, Thomas Mangotsma...@gmail.com wrote: You should be providing both the source and a target user to the /friendships/show method. You can use source_id target_id or source_screen_name target_screen_name with /friendships/show. Here's the API documentation:http://dev.twitter.com/doc/get/friendships/show Joe Rattz wrote: I would like to determine if my registered application's user is following another user. First I tried friendships/show with a target_screen_name = someuser and get this error: hash request/1/friendships/show.xml/request errorTarget user not specified./error /hash Then I tried friendships/show with user_a = myusername and user_b = someuser and get this error: hash request/1/friendships/exists.xml/request errorTwo user ids or screen_names must be supplied./error /hash I would prefer to use the show method and without having to specify my application's user's username. These are both using the Twulr Console. What am I missing? Thanks. -- Thomas Mango tsma...@gmail.com- Hide quoted text - - Show quoted text - -- Thomas Mango tsma...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] [SiteStreams] can't follow more than one user
Hey, Ruben. That's the correct URL format. Are you sure your account was approved for Site Stream access? Ruben Fonseca wrote: Hi @all! Not sure if I'm posting to the correct list, but here it goes. I'm currently trying to migrate a website service that uses UserStreams to SiteStreams, as the documentation tells me to do. However I'm finding a difficult problem that I've been able to reproduce: If I try to follow 1 user_id, it works ok. If I try to follow 2 or more, SiteStreams always answers 401 Unauthorized. Example: (Host: betastream.twitter.com) - this works GET /2b/site.json?with=followingsfollow=11528912 HTTP/1.1 - this works too GET /2b/site.json?with=followingsfollow=9512582 HTTP/1.1 - this always returns 401 UNAUTHORIZED GET /2b/site.json?with=followingsfollow=11528912,9512582 HTTP/1.1 Any thing I'm missing here? Thank you! -- Thomas Mango tsma...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Hotlinking images
I believe it's okay to directly use the URLs given in responses (like the user's profile image url), but you'll quickly run into issues where those URLs will stop working when someone changes their profile image. I suggest keeping a copy of the image cached yourself and updating it every so often to avoid issues like this. However, a better alternative may be to use @joestump's http://tweetimag.es service. Christian Fazzini wrote: Creating a new Twitter app. I am thinking whether I should save the users images (profile and background) on the local server or hotlink it instead? Whats the e-etiquette for this? Does Twitter encourage us to hotlink images? -- Thomas Mango tsma...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Is the authorized user count for apps still available?
Hey, Jon. This was actually just answered recently: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/979d3d5bdfa06083 Basically, no it isn't readily available anymore and it would be better to track it yourself. Jon Colverson wrote: Hello. I remember seeing somewhere a stat showing how many users had authorized API access for my app, but I can't seem to find it anymore. Is this number no longer available, or is it still there and I'm a dunce for not being able to find it? Thanks. -- Jon -- Thomas Mango tsma...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] bidirectional relationship
Ashwin, As far as I know, you can't do this in a single API call. You can, however, call /friends/ids and /followers/ids and use the intersection of the two arrays to find what you're looking for. Relevant API documentation: http://dev.twitter.com/doc/get/friends/ids http://dev.twitter.com/doc/get/followers/ids ashy wrote: Hi All, As we can retrieve friends and followers of the user using the twitter rest api, can we also retrieve users who are both friends and followers of the user at the same time (bidirectional relationship) using the twitter rest api? Any ideas? thanks ashwin -- Thomas Mango tsma...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] ways to authorize users other then oAuth and xAuth?
OAuth will work fine for this. Once a user authorizes your application, you store their access key/secret. Using your client's key/secret and the user's key/secret, you can sign a request to Twitter on behalf of that user. Twitter's OAuth documentation: http://dev.twitter.com/pages/auth sir pelidor wrote: Greeting, I have an app that needs to update its' member's twitter status as well as status for other social-network sites in a scheduled manner. For which I found it very difficult to implement it using oAuth or xAuth, therefore I seek for advise from fellow developers. Detail of the workflow: -End users sign up my service, and will be given to opportunity to store their twitter's access credentials. -End users update status at my service and schedule when it will be deliver -End users are limited to update their status once every 6 days. -To avoid spams, If the end user do not renewal their status after it has been sent by my service, it will not schedule for the next delivery (it does not allow end users to sent the same tweet as the previous one) -In a daily basis, the scheduler of my service will query each members in the system who are qualified to deliver tweet in that given day. Then it will mass update all qualifier's twitter status. Due to how my scheduler works in the background, I believe oAuth or xAuth may not be a proper solution to my problem. Since Twitter API no longer support Basic Auth, what other manners can I utilize so I can send tweet on behave of my members? Thank you. -- Thomas Mango tsma...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Ultimately send my twitter followers direct messages from my application
I think what you described is exactly right. You're looking for an app that users can authorize with using OAuth. Once they're redirected back to your site (part of the OAuth process), you can create a user account for them locally and ask them to follow your Twitter account. Because they've authorized your application, when they agree to follow you, you can use the /friendships/create API method on their behalf. Relevant API documentation: http://dev.twitter.com/pages/auth http://dev.twitter.com/doc/post/friendships/create Dialflow wrote: Hi: I was wondering if any one could suggest an elegant approach to ultimately sending direct messages to my Twitter followers from my application. I'd like people that join web site to do the following: From their member page on my site, I'd like for them to click a Twitter follow button, go to Twitter, follow me, then return to their member page on my site. After they do this, I want capture their twitter ID and associate it with their user account on my site so I can send them direct messages from my application. I'd really appreciate an elegant approach to solving this. I guess I'm looking for an answer like: Use oAuth to have the user authorize your app on Twitter, then redirect redirect back to your app, click a twittter follow button, and extract their Twitter ID from x_file and then My days of programming are way behind me so I hope that makes some sense. Thanks so much. Curtis -- Thomas Mango tsma...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Ultimately send my twitter followers direct messages from my application
Yes, there's a limit of 250 direct messages per day according to: http://support.twitter.com/forums/10711/entries/15364 I'm not sure if there are any policies against automatically direct messaging someone when they follow you, but a 250/day would certainly prevent that at some point. I don't know the details of your application, but if you were only planning to send new followers a direct message, perhaps you can avoid asking them to follow you and sending them a direct message by just showing them what you wanted to message them when they come back from the OAuth authorization. -- Thomas Mango On Oct 2, 2010, at 1:12 PM, Dean Collins d...@cognation.net wrote: Thomas are there restrictions on what/how many direct messages can be sent? I haven't been paying attention with twitter for a while but I thought twitter banned automatic direct messages. Thanks in advance, Dean I think what you described is exactly right. You're looking for an app that users can authorize with using OAuth. Once they're redirected back to your site (part of the OAuth process), you can create a user account for them locally and ask them to follow your Twitter account. Because they've authorized your application, when they agree to follow you, you can use the /friendships/create API method on their behalf. Relevant API documentation: http://dev.twitter.com/pages/auth http://dev.twitter.com/doc/post/friendships/create Dialflow wrote: Hi: I was wondering if any one could suggest an elegant approach to ultimately sending direct messages to my Twitter followers from my application. I'd like people that join web site to do the following: From their member page on my site, I'd like for them to click a Twitter follow button, go to Twitter, follow me, then return to their member page on my site. After they do this, I want capture their twitter ID and associate it with their user account on my site so I can send them direct messages from my application. I'd really appreciate an elegant approach to solving this. I guess I'm looking for an answer like: Use oAuth to have the user authorize your app on Twitter, then redirect redirect back to your app, click a twittter follow button, and extract their Twitter ID from x_file and then My days of programming are way behind me so I hope that makes some sense. Thanks so much. Curtis -- Thomas Mango tsma...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] add list members
Are you sure you're requesting the correct format? I was able to POST to /:user/:list_id/members.xml with an id of a user and it correctly added the user to my list and responded with XML: POST: /14338478/23124429/members.xml?id=14477861 Response: http://gist.github.com/607880 On Sat, Oct 2, 2010 at 2:16 PM, Damon Clinkscales sca...@pobox.com wrote: I've tried both create_all.xml and members.xml to add multiple or just one member to a list. The list is owned by me and exists. http://dev.twitter.com/doc/post/:user/:list_id/create_all or http://dev.twitter.com/doc/post/:user/:list_id/members When the call goes through, the response is a normal #newtwitter web page instead of an API response. Is this a known issue? thanks, /damon -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Thomas Mango tsma...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] about image-size in newtwitter
If you're using the profile_image_url from the API, you can remove the _normal from the suffix to get the original size, although you have to make sure the user doesn't have a default image. You can also use this API method: http://dev.twitter.com/doc/get/users/profile_image/:screen_name The response from that API method shouldn't be used directly as an image source, though. On Fri, Oct 1, 2010 at 9:43 AM, Rushikesh Bhanage rishibhan...@gmail.com wrote: Hi there, I got the new look of new twitter, and liked it a lot. The profile-image size in newtwitter has been increased from previous(48*48). When I increase the profile image size of the user(the image i get from api right now), it looks unclear, blur type. I just need to know that, will I get a big image from twitter API, once new twitter will come in service completely? or can I do it from my side? Thank you in Advance. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Thomas Mango tsma...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Site Streams - Unfollow Events?
I'm seeing list modification events in my Site Streams. The list events I've seen are are list_member_added, list_member_removed and list_created. Tom van der Woerdt wrote: I tried, but I didn't see anything. Adding a new user to one of my lists didn't send anything, and removing didn't either. Haven't been able to test this outside my app, although I doubt that it's my code (it simply outputs all incoming data to debug). Tried with cURL but got an error about Basic Auth. Can anyone verify that there are no list events in the streams, or am I simply going blind? Tom On 10/1/10 10:57 PM, John Kalucki wrote: List modifications are streamed as social events. The lists themselves are not streamed. -John On Fri, Oct 1, 2010 at 11:01 AM, Tom van der Woerdti...@tvdw.eu wrote: Correct. I'd like to add an additional question to this thread: what about list events? The docs say that they get sent, but they don't. http://dev.twitter.com/pages/user_streams Tom On 10/1/10 7:46 PM, Justin wrote: It sounds like it's the same (NO) for both: Friendship Events Created - To you, from you Deleted - From you So, unfollow events from you not to you as the target. There doesn't seem to be any way to tell when someone stops following other than using the rest API to check followers and compare it to the list of following. Same with blocks: Created - From you (source) Deleted - From you (source) On Sep 30, 12:05 pm, M. Edward (Ed) Boraskyzn...@borasky- research.net wrote: Site Streams only or User Streams? I'm developing around User Streams. -- M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting tsmangotsma...@gmail.com: Hi, Ed. Block and unblock events are already being delivered in the Site Stream. Very useful! On Sep 30, 12:30 pm, M. Edward (Ed) Boraskyzn...@borasky- research.net wrote: As long as we're wishing, I'd like to get a notification when someone blocks me. ;-) -- M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos - Thomas Mango @tsmango -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Thomas Mango tsma...@gmail.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Are there ANY advantage of using OAuth with client softwares?
Another advantage is that if a third party application's database is breached, all of the stored usernames and passwords would be exposed. If the third party application was using oauth, the access token and secret pairs are only useable if the consumer key/secret pair are found and these can be easily reset. On May 18, 2:56 pm, Adam Ness adam.n...@gmail.com wrote: The advantage to the end user of oAuth is that the client application doesn't need the user's password anymore, the user's passwords are exchanged ONLY with twitter, and cannot be sniffed/stored/whatever by the client application. There is a very strong security advantage. On Mon, May 18, 2009 at 7:30 AM, H.Hiro(Maraigue) marai...@mail.goo.ne.jpwrote: Hello, I COULD NOT UNDERSTAND why Twitter so much encourages OAuth, in spite of costing API users. I read the section What Does OAuth Give Me? (a.k.a. Why Bother?) of this article: http://apiwiki.twitter.com/OAuth+Example+-+Ruby, but I could not find what is the advantage of using OAuth *for client- software makers* . Client softwares must know end-users'(i.e. account holders') login names and passwords, so I think there aren't more advantage of using OAuth than basic-auth.
