Re: [twitter-dev] oauth API and application name
On 8/13/10 2:46 AM, Stan Miasnikov wrote:
Hi,
I have implemented the oauth for a desktop application. The
application has been approved and I get the token back and also can
make HTTP requests using the token. However, when I post an update
using the app, it shows ...via API instead of the application name.
I thought the approved application's name suppose to appear instead. I
made sure that the post has oauth header instead of basic auth.
header. Do I need to do something else to ensure that the app name
appears instead of the API?
POST header:
Twitter request header: {
Authorization = OAuth realm=\\, oauth_consumer_key=\\,
oauth_token=\X\, oauth_signature_method=\HMAC-SHA1\,
oauth_signature=\lAx4jFI%2FeXaFv4aBxEYg2n3kkSo%3D\, oauth_timestamp=
\1281566038\, oauth_nonce=\F0999B0E-66FC-4CFE-AED7-4D87064A92A9\,
oauth_version=\1.0\;
Content-Type = application/x-www-form-urlencoded;
X-Twitter-Client = WritePad;
X-Twitter-Client-Url = http://www.phatware.com/writepad;;
X-Twitter-Client-Version = 4.1;
}
Thanks,
Stan
Hi Stan,
As far as I know, all registered OAuth applications show via
Application - no exceptions. If you get via API, then make sure that
you are not also sending basic credentials. Your application may be
caching credentials, which could be the issue.
Also, I don't think that you should send the X-Twitter headers. As far
as I know, Twitter prefers having these in your user agent.
Tom
[twitter-dev] Re: OAuth and Hardware
I'd like to learn more about how to use OAuth on hardware without a browser or UI. Currently Java is being supported. What if I design a hardware chip that must be written in C or C++, what are the options to get hardware to post tweet On Aug 11, 6:13 pm, Tom van der Woerdt i...@tvdw.eu wrote: On 8/12/10 3:10 AM, ERenken wrote: I thought about doing the proxy, but I liked having the device do it itself and alot less code just having the device do it. I will just hard code it. I would assume we can invalidate a token if for some reason it is comprimised. Like managing applications in FaceBook. Eric On Aug 11, 9:36 am, Tom van der Woerdt i...@tvdw.eu wrote: On 8/11/10 6:30 PM, ERenken wrote: So how can I use OAuth on a hardware device we are creating that doesn't have a UI? Can I share the key between all the devices? This is only twittering to 1 account that we have created. Seems like OAuth is going to make stuff like this harder for people to develope. Seems like it would have just bee easier for security if you would have added HTTPS and left basic auth. At least for embedded devices so they could send tweets. If there's no chance of the key leaking to people outside of your company (or whoever uses your application) then I don't see why not. It's always better than sharing username/password like with Basic Auth, and if they all use the same account, it's no problem at all. Of course, a better solution would be to create a simple proxy, but that may take some more programming and money if you don't have a server for it. Tom Yes, you can. Athttp://dev.twitter.com/appsyou can simply click Reset. Tom
[twitter-dev] Re: statuses/friends_timeline doesn't return replies
I've done some further testing and found that when the
'in_reply_to_screen_name' is filled I do get replies to users that I
follow. But when that field isn't set I don't get them.
And I found that the replies with in_reply_to_screen_name empty also
are not displayed on my twitter homepage
So user1 replies to user2 with in_reply_to_screen_name filled
Tweet is shown on my twitter homepage and in the result of the
friends_timeline (or home_timeline, both tested) request.
But when user2 replies to user1 with in_reply_to_screen_name empty
Tweet isn't shown on my twitter homepage and not in the
friends_timeline request (or home_timeline)
oberver user id: 161263875
user1: 14741760
user2: 6028822
observer user is following both user1 and user2
object(stdClass)#36 (14) {
[in_reply_to_screen_name]=
string(6) Domien
[in_reply_to_user_id]=
int(6028822)
[geo]=
NULL
[place]=
NULL
[coordinates]=
NULL
[favorited]=
bool(false)
[in_reply_to_status_id]=
int(20979439727)
[source]=
string(67) a href=http://twitter.com/; rel=nofollowTwitter
for iPhone/a
[contributors]=
NULL
[truncated]=
bool(false)
[user]=
object(stdClass)#37 (1) {
[id]=
int(14741760)
}
[created_at]=
string(30) Thu Aug 12 23:03:29 + 2010
[id]=
int(21013121914)
[text]=
string(52) @Domien Haha, direct al ruzie. Met een bot. Classic!
}
'Missing' tweet id: 21045034430
Thanks,
Patrick
On Aug 11, 4:58 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Can you provide links to the users or specific status ids, along with a
sample of your home_timeline API response where the replies should be
located?
Thanks,
Taylor
On Wed, Aug 11, 2010 at 7:36 AM, PBro brouwe...@gmail.com wrote:
Hi Taylor,
I'm requesting friends_timeline for user pbro and user pbro is
following both user1 and 2.
So yes the observer user is following both users.
On Aug 11, 4:13 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi PBro,
This typically works pretty well though there is the odd case of a
missing
@mention here and there.
Could you verify that both user1 and user2 are being followed by the
observer user?
Thanks,
Taylor
On Wed, Aug 11, 2010 at 6:55 AM, PBro brouwe...@gmail.com wrote:
Hi,
I want to get all the tweets from people I follow, therefore is use
statuses/friends_timeline.
But in the results I get I see no replies.
For example:
I'm following user1. User1 tweets a standard message like: I'm washing
the dishes
This tweet is returned in my statuses/friends_timeline request.
In the next tweet user1 replies to user2 (@user2 ...)
This tweet is not returned in my statuses/friends_timeline request.
Even when I am following user2 also, still no sign of the reply tweet.
Is this expected behaviour, or am I missing something(a parameter I
could add or something)
your sincerely,
Patrick
[twitter-dev] Re: Introducing the Tweet Button
Anyone else getting the count to work? Had several people press the button and it still shows zero, and when clicking on the zero it takes me to the search page containing their tweet, plus our autotweet everytime we do a blog post. Also will you be counting all tweets containing the URL, or only those via the button? Cheers Ryan On Aug 12, 4:28 pm, themattharris thematthar...@twitter.com wrote: Hey everyone, Today we’re launching the Tweet Button to make it easy for your users to share your website with their followers. When they click on the Tweet Button, a Tweet box will appear pre-populated with a message and link chosen by you. Once they have sent a Tweet they can choose to follow accounts recommended by you. All of this happens on your website, so the user never has to leave. You have complete control over the suggested text of the Tweet Button, who the Tweet should be attributed to and recommendations of who to follow. All of this is possible through a line of javascript and a few URL parameters or data attributes of a link. To add this to your own site grab it fromhttp://twitter.com/tweetbutton, or create your own using our developer documentation,http://dev.twitter.com/pages/tweet_button Read more about the Tweet Button on our blog,http://blog.twitter.com/2010/08/pushing-our-tweet-button.html Best Matt -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris
Re: [twitter-dev] Re: Introducing the Tweet Button
getting cert errors now On 13/08/10 9:12 AM, artesea wrote: Anyone else getting the count to work? Had several people press the button and it still shows zero, and when clicking on the zero it takes me to the search page containing their tweet, plus our autotweet everytime we do a blog post. Also will you be counting all tweets containing the URL, or only those via the button? Cheers Ryan On Aug 12, 4:28 pm, themattharristhematthar...@twitter.com wrote: Hey everyone, Today we’re launching the Tweet Button to make it easy for your users to share your website with their followers. When they click on the Tweet Button, a Tweet box will appear pre-populated with a message and link chosen by you. Once they have sent a Tweet they can choose to follow accounts recommended by you. All of this happens on your website, so the user never has to leave. You have complete control over the suggested text of the Tweet Button, who the Tweet should be attributed to and recommendations of who to follow. All of this is possible through a line of javascript and a few URL parameters or data attributes of a link. To add this to your own site grab it fromhttp://twitter.com/tweetbutton, or create your own using our developer documentation,http://dev.twitter.com/pages/tweet_button Read more about the Tweet Button on our blog,http://blog.twitter.com/2010/08/pushing-our-tweet-button.html Best Matt -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris
[twitter-dev] Is Twitter misusing their own t.co url shortener?
How long has it been since Twitter started their own t.com url shortener? Not sure, but I don't think it's been long enough to shorten over 3.5 trillion urls. Well, I just noticed that the the url shortened by t.com was this:http://t.co/5ywZYau So the value is 5ywZYau From what I understand the shorteners work this way (at least this is the most effecient way in order to create as short a url as possible): First you create a new record for url and get the next available numeric id, usually auto increment. Then you use base62 encoding to convert this integer into a string. The result is that you get the shortest possible value consisting of lower and upper case english letters plus 10 numbers, thus a total of 62 chars are used. The number of chars needed to represent a value is 62 x 62 x 62, etc... so the 7 chars-long base 62 string can represent a number over 13 digits long. Ok, so is it really possible for this service to already shorten over a trillion urls? I don't think so. which only means that you are not doing your best to make the shortest possible url. What's the point of registering a one-letter top level domain, going through all the trouble of creating your own service and then not really doing your absolute best to make sure urls are as short as possible. I mean, you could have probably still be using 4, maybe 5 - chars long codes instead of 7, saving potential customers 2 or 3 valuable characters
[twitter-dev] Re: New tweet button - is t.co mandatory?
I read in the techcrunch article, that the posting url is wrapped in t.co, but then when displayed in the stream, the url gets unwrapped again, so you should see the moxs.ie url (in my case). This doesn't happen for me. I only see the t.co url. Is there a whitelist of URLs that are accepted by twitter for 'unwrapping-in-the-stream'? If so, how do I get on that list? Thanks, Per
[twitter-dev] Re: Any way to turn off 'user-scalable' meta tag in OAuth authorization form?
For me the issue is usability. When I render the page on the iPhone in a webview that takes up most of the screen LCD, the size of the letters for the username and password input fields are tiny. I showed my dad who is an older guy, but still likes Twitter, and he said he couldn't read the letters while he typed because they were so small. On Aug 12, 2:59 pm, Zac Bowling zbowl...@gmail.com wrote: The only issue with that is that you can't return the user to the app after the oath flow (unless you implement a protocol handler on your platform and Twitter supported calling back to it). I'm back and forth on this myself. The security advocate in me agrees with you Taylor, but the UX guy in me causes me to strive to find a way to guide the user through the process so that my users don't have follow too many instructions or do to many steps get up and going. Zac Sent from my iPad On Aug 12, 2010, at 2:35 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: There's no known way to do this today, Tony. While it's obviously not a policy at Twitter, I thought I'd just take the time to share my personal opinion on embedded web views and the OAuth flow: - Not into it. Why? somewhat-related-opinion By redirecting to a standard web browser on the device where your application resides, your users can better understand the security scenario being presented to them while they are approving access for your application. Using an embedded webview subverts this trust, as you're basically providing them with a web browser of your application's design. Obviously, the majority of developers who implement things this way are not doing so with ill intent, but the opportunity for funny business increases when using a custom web view. There are other API providers out there who forbid the use of embedded browsers during OAuth flows for this reason. /somewhat-related-opinion Taylor On Thu, Aug 12, 2010 at 2:31 PM, Tony.In.Portland tony.in.portl...@gmail.com wrote: Bad choice of words on my part. I want to be able to set the value to yes, I want the page that comes back to be scalable. On Aug 12, 2:09 pm, Tony.In.Portland tony.in.portl...@gmail.com wrote: Is there any way to turn off the user-scalable meta tag in the page that comes back during the oAuth authorization process? I want to render the page in my own webview, but I want to allow the person to zoom/pinch so they can expand the page so the input fields and buttons are not so small. This is for a mobile device. Thanks, Tony
[twitter-dev] OAuth and impact on Twitter userbase / volume
I'm curious to post this question to see if Twitter has fully thought out the impact of forcing OAuth onto their API applications. While it may appear to be a more secure method preferred in principle by users, the fact of the matter is that one of the main benefits of the API, is the ability for third party twitter alternatives to be created, thus allowing people to tweet during business hours, when they normally could not due to firewall / web sense restrictions, etc, that prevent them from accessing the twitter.com domain. Via basic authentication, users would never have to visit twitter.com to login and gain access to twitter functionality via api clients. By shutting this down, you are now forcing ALL potential users to login via twitter.com, many of which do not have access to this domain in their workplace environment, thus excluding them from easily using your service wholesale. This can / will, I suspect, have significant impact on twitter usage / volume, unless I am missing something and there is an alternative the does not require them to directly access the twitter.com domain to grant access.
[twitter-dev] Re: search for hashtags
Thank you guys for your insight. I was in a rush so I picked simple search but I'll revert it to stream. Not quite clear what do you mean by saying to revert stream every hour but I guess it's in the docs. On Aug 13, 1:58 am, Mark McBride mmcbr...@twitter.com wrote: In both cases it's still probably best to use streaming. You don't want to connect to often, but once an hour should be totally fine. ---Mark http://twitter.com/mccv On Tue, Aug 10, 2010 at 6:34 AM, Tom van der Woerdt i...@tvdw.eu wrote: On 8/10/10 12:58 PM, bitstream wrote: Hi all, I've been reading api docs lately but still can't figure it out what will be the best approach when searching for hashtags. streaming I know that streaming api support statuses/filter where I can declare 'track'. It's possible to use statuses/filter and add a track on '%23hashtag' ? search Or use a simple approach by calling search api and parse response from something like this:http://search.twitter.com/search.json?q=%23hashtag My opinion: It depends. If you want to track a lot of keywords, you should use streaming. If you track only one keyword, then both are an option, depending on the amount of tweets for the hashtag. If you have a lot of keywords but they vary (for example, when users can add/remove hashtags) then you should consider a combination of both, where you reset the stream every hour and update it with new hashtags, and use the REST API for the hashtags that get added in the hour. After all, you don't want to reconnect too often. Tom
[twitter-dev] Total number of tweets containing a word
Hi All, What is the best way of counting the number of tweets containing a phrase The Lost World 1. Is there an API call, I can make to retrieve this information or 2. Should I make an Search API call for the keyword at regular interval and store the tweets in my database and analyze this data. (although this might be affected by the rate limit of the API usage)
[twitter-dev] Searching for a phrase and multiple keyword as OR
Hi I was wondering what is the best way of searching for a phrase and a KW Example The Lost World and book and what if I wanted to try different combinations where The Lost world is mandatory however other keywords read, reading, book are or The Lost world and read OR The Lost world and reading OR The Lost world and book
Re: [twitter-dev] OAuth and impact on Twitter userbase / volume
On 8/13/10 4:31 AM, TheGuru wrote: I'm curious to post this question to see if Twitter has fully thought out the impact of forcing OAuth onto their API applications. While it may appear to be a more secure method preferred in principle by users, the fact of the matter is that one of the main benefits of the API, is the ability for third party twitter alternatives to be created, thus allowing people to tweet during business hours, when they normally could not due to firewall / web sense restrictions, etc, that prevent them from accessing the twitter.com domain. Via basic authentication, users would never have to visit twitter.com to login and gain access to twitter functionality via api clients. By shutting this down, you are now forcing ALL potential users to login via twitter.com, many of which do not have access to this domain in their workplace environment, thus excluding them from easily using your service wholesale. This can / will, I suspect, have significant impact on twitter usage / volume, unless I am missing something and there is an alternative the does not require them to directly access the twitter.com domain to grant access. My opinion: if your boss does not allow twitter, then don't do it. Although I have to admit that your point is valid, except for one major flaw: if twitter.com was really blocked, then the API would be blocked as well ;-) Also, some (most) desktop clients do not require you to login via OAuth, but instead they use xAuth. I'm sorry that you will no longer be able to play the silly quizzes etc, but you'll just have to live with that :-) Tom
[twitter-dev] OAuth and immediate redirect back to my site without questions
Hello, all! I am a newbie to twitter api, so i have a simple question. I'm making single sign on with twitter on my site. Everything works fine, but one thing reallly annoyes me! If the client is signed in twitter and has already granted access to my application twitter asks him again after redirect during request authorization phase. Can I eliminate it somehow? Can twitter just immediately redirect user back with auth_token and verifier without asking questions? Perhapse I'm doing something completely wrong?
[twitter-dev] Re: Is Twitter misusing their own t.co url shortener?
I don't know how Twitter are shortening the URLs. However. IIRC Twitter's shortener is designed to always use 20 characters (I believe) so that as developers we can pass in full URLs knowing how much space each URL will take up in a tweet and show the character count accordingly. Matt / Taylor might be able to comment further though. -N -- Nik Fletcher @nikf On Aug 13, 2:17 am, D. Smith emai...@sharedlog.com wrote: How long has it been since Twitter started their own t.com url shortener? Not sure, but I don't think it's been long enough to shorten over 3.5 trillion urls. Well, I just noticed that the the url shortened by t.com was this:http://t.co/5ywZYau So the value is 5ywZYau From what I understand the shorteners work this way (at least this is the most effecient way in order to create as short a url as possible): First you create a new record for url and get the next available numeric id, usually auto increment. Then you use base62 encoding to convert this integer into a string. The result is that you get the shortest possible value consisting of lower and upper case english letters plus 10 numbers, thus a total of 62 chars are used. The number of chars needed to represent a value is 62 x 62 x 62, etc... so the 7 chars-long base 62 string can represent a number over 13 digits long. Ok, so is it really possible for this service to already shorten over a trillion urls? I don't think so. which only means that you are not doing your best to make the shortest possible url. What's the point of registering a one-letter top level domain, going through all the trouble of creating your own service and then not really doing your absolute best to make sure urls are as short as possible. I mean, you could have probably still be using 4, maybe 5 - chars long codes instead of 7, saving potential customers 2 or 3 valuable characters
Re: [twitter-dev] Total number of tweets containing a word
On 8/13/10 10:34 AM, Abhi wrote: Hi All, What is the best way of counting the number of tweets containing a phrase The Lost World 1. Is there an API call, I can make to retrieve this information or 2. Should I make an Search API call for the keyword at regular interval and store the tweets in my database and analyze this data. (although this might be affected by the rate limit of the API usage) I would say that using the Streams is best for this - option 3. http://dev.twitter.com/doc/post/statuses/filter Tom
[twitter-dev] Send Custom Header
Accept: */* Connection: close User-Agent: OAuth gem v0.3.4.1 Authorization: abcdefgh Host: api.twitter.com how to send the above header to api.twitter.com through PHP ?
Re: [twitter-dev] OAuth and immediate redirect back to my site without questions
On 8/13/10 12:15 PM, Krot Vyacheslav wrote: Hello, all! I am a newbie to twitter api, so i have a simple question. I'm making single sign on with twitter on my site. Everything works fine, but one thing reallly annoyes me! If the client is signed in twitter and has already granted access to my application twitter asks him again after redirect during request authorization phase. Can I eliminate it somehow? Can twitter just immediately redirect user back with auth_token and verifier without asking questions? Perhapse I'm doing something completely wrong? No, you can't. An alternative would be to store the oauth data *encrypted* in a cookie, and check whether the cookie is valid. However, this may be a security threat: cookies can be stolen, so they should only work on one computer. I wouldn't recommend limiting it to one IP, but it is an option. Tom
Re: [twitter-dev] Send Custom Header
On 8/13/10 12:41 PM, alex wrote: Accept: */* Connection: close User-Agent: OAuth gem v0.3.4.1 Authorization: abcdefgh Host: api.twitter.com how to send the above header to api.twitter.com through PHP ? I do not know the exact code, but you will most likely want to use cURL. http://php.net/curl_init http://php.net/curl_setopt http://php.net/curl_exec Tom
Re: [twitter-dev] Cannot get the access token,
Hi OLiE,
I'm not too experienced with Android programming, so am unsure whether your
code is correct or not. But there's something you might want to check on
dev.twitter.com/apps and that's whether your application is set as browser
and with a default callback URL set. This is a quirk in our system, such
that if you aren't providing a default callback URL (regardless if it has
anything to do with the actual callback you will use), it will put you into
out of band mode. I think that might be what is happening.
If not, we'll move on to some other possibilities.
Taylor
On Thu, Aug 12, 2010 at 5:22 PM, OLiE ali.hafi...@gmail.com wrote:
Hey guys,
I am trying to make an android app for twitter. The
code that i am using for the login is given below :
package com.twitter;
import org.apache.http.HttpVersion;
import org.apache.http.client.HttpClient;
import org.apache.http.conn.ClientConnectionManager;
import org.apache.http.conn.scheme.PlainSocketFactory;
import org.apache.http.conn.scheme.Scheme;
import org.apache.http.conn.scheme.SchemeRegistry;
import org.apache.http.impl.client.DefaultHttpClient;
import org.apache.http.impl.conn.tsccm.ThreadSafeClientConnManager;
import org.apache.http.params.BasicHttpParams;
import org.apache.http.params.HttpConnectionParams;
import org.apache.http.params.HttpParams;
import org.apache.http.params.HttpProtocolParams;
import org.apache.http.protocol.HTTP;
import com.twitter.twitterEngine.TimeLine;
import oauth.signpost.OAuthProvider;
import oauth.signpost.basic.DefaultOAuthProvider;
import oauth.signpost.commonshttp.CommonsHttpOAuthConsumer;
import oauth.signpost.http.HttpParameters;
import android.app.Activity;
import android.content.Intent;
import android.content.SharedPreferences;
import android.content.SharedPreferences.Editor;
import android.net.Uri;
import android.os.Bundle;
import android.provider.UserDictionary.Words;
import android.util.Log;
import android.view.Gravity;
import android.view.View;
import android.view.View.OnClickListener;
import android.widget.Button;
import android.widget.EditText;
import android.widget.Toast;
public class Twitter extends Activity implements OnClickListener{
/** Called when the activity is first created. */
private Button Login;
private SharedPreferences prefs;
private String prefFile = twitter_prefs;
private final String CALLBACKURL = myapp://mainactivity;
private CommonsHttpOAuthConsumer httpOauthConsumer;
private OAuthProvider httpOauthprovider;
public final static String consumerKey =mykey;
public final static String consumerSecret = mysecret;
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
initViews();
}
public void initViews()
{
//initializing the consumer and the provider
httpOauthConsumer = new
CommonsHttpOAuthConsumer(consumerKey,
consumerSecret);
httpOauthprovider = new DefaultOAuthProvider(https://
api.twitter.com/oauth/request_token,
https://api.twitter.com/oauth/access_token
,
https://api.twitter.com/oauth/authorize;);
Login=(Button)findViewById(R.login.LoginButton);
Login.setOnClickListener(this);
}
private void doOauth() {
try {
String authUrl =
httpOauthprovider.retrieveRequestToken(httpOauthConsumer,
CALLBACKURL);
this.startActivity(new Intent(Intent.ACTION_VIEW,
Uri.parse(authUrl)));
} catch (Exception e) {
Toast.makeText(this, e.getMessage(),
Toast.LENGTH_LONG).show();
}
}
public void onClick(View arg0) {
// TODO Auto-generated method stub
doOauth();
}
@Override
protected void onNewIntent(Intent intent) {
// TODO Auto-generated method stub
super.onNewIntent(intent);
Uri uri = intent.getData();
//Check if you got NewIntent event due to Twitter Call back
only
if (uri != null uri.toString().startsWith(CALLBACKURL)) {
String verifier =
uri.getQueryParameter(oauth.signpost.OAuth.OAUTH_VERIFIER);
prefs = getSharedPreferences(prefFile, 0);
try {
// this will populate token and token_secret
in consumer
httpOauthprovider.retrieveAccessToken(httpOauthConsumer,
verifier);
String userKey =
httpOauthConsumer.getToken();
String userSecret =
httpOauthConsumer.getConsumerSecret();
Re: [twitter-dev] Re: Is Twitter misusing their own t.co url shortener?
If you used a Base62 algorithm, then you can simply increase the value by one for the next url. I assume that Twitter did this for security reasons, just like bit.ly. Tom On 8/13/10 3:55 PM, Nik Fletcher wrote: I don't know how Twitter are shortening the URLs. However. IIRC Twitter's shortener is designed to always use 20 characters (I believe) so that as developers we can pass in full URLs knowing how much space each URL will take up in a tweet and show the character count accordingly. Matt / Taylor might be able to comment further though. -N -- Nik Fletcher @nikf On Aug 13, 2:17 am, D. Smith emai...@sharedlog.com wrote: How long has it been since Twitter started their own t.com url shortener? Not sure, but I don't think it's been long enough to shorten over 3.5 trillion urls. Well, I just noticed that the the url shortened by t.com was this:http://t.co/5ywZYau So the value is 5ywZYau From what I understand the shorteners work this way (at least this is the most effecient way in order to create as short a url as possible): First you create a new record for url and get the next available numeric id, usually auto increment. Then you use base62 encoding to convert this integer into a string. The result is that you get the shortest possible value consisting of lower and upper case english letters plus 10 numbers, thus a total of 62 chars are used. The number of chars needed to represent a value is 62 x 62 x 62, etc... so the 7 chars-long base 62 string can represent a number over 13 digits long. Ok, so is it really possible for this service to already shorten over a trillion urls? I don't think so. which only means that you are not doing your best to make the shortest possible url. What's the point of registering a one-letter top level domain, going through all the trouble of creating your own service and then not really doing your absolute best to make sure urls are as short as possible. I mean, you could have probably still be using 4, maybe 5 - chars long codes instead of 7, saving potential customers 2 or 3 valuable characters
Re: [twitter-dev] Re: New tweet button - is t.co mandatory?
On 8/13/10 5:04 AM, pthomsen wrote: I read in the techcrunch article, that the posting url is wrapped in t.co, but then when displayed in the stream, the url gets unwrapped again, so you should see the moxs.ie url (in my case). This doesn't happen for me. I only see the t.co url. Is there a whitelist of URLs that are accepted by twitter for 'unwrapping-in-the-stream'? If so, how do I get on that list? Thanks, Per Yesterday I noticed that t.co links were unwrapped in the search, but it looks like that is no longer the case at the moment. Probably taken offline for a few hours to perfect the algorithm, like Twitter usually does after implementing something new (happened to Lists too). It looked like all t.co links are unwrapped, so don't worry ;-) Tom
Re: [twitter-dev] Re: Introducing the Tweet Button
We had some caching/rate limiting issues related to tweet counts for a portion of yesterday but these should be relieved now. Please let us know if you continue seeing the zero counts after a reasonable amount of time (they won't update instantaneously). On Fri, Aug 13, 2010 at 6:12 AM, artesea ryancul...@gmail.com wrote: Anyone else getting the count to work? Had several people press the button and it still shows zero, and when clicking on the zero it takes me to the search page containing their tweet, plus our autotweet everytime we do a blog post. Also will you be counting all tweets containing the URL, or only those via the button? Cheers Ryan
Re: [twitter-dev] Re: Introducing the Tweet Button
Hi James, Can you share more about your certificate issues? Can you share some URLs where we can investigate or if you're implementing it yourself, the particulars of your configuration? Thanks, Taylor On Fri, Aug 13, 2010 at 6:30 AM, James Jones ja...@freedomnet.co.nz wrote: getting cert errors now On 13/08/10 9:12 AM, artesea wrote: Anyone else getting the count to work? Had several people press the button and it still shows zero, and when clicking on the zero it takes me to the search page containing their tweet, plus our autotweet everytime we do a blog post. Also will you be counting all tweets containing the URL, or only those via the button? Cheers Ryan On Aug 12, 4:28 pm, themattharristhematthar...@twitter.com wrote: Hey everyone, Today we’re launching the Tweet Button to make it easy for your users to share your website with their followers. When they click on the Tweet Button, a Tweet box will appear pre-populated with a message and link chosen by you. Once they have sent a Tweet they can choose to follow accounts recommended by you. All of this happens on your website, so the user never has to leave. You have complete control over the suggested text of the Tweet Button, who the Tweet should be attributed to and recommendations of who to follow. All of this is possible through a line of javascript and a few URL parameters or data attributes of a link. To add this to your own site grab it fromhttp://twitter.com/tweetbutton, or create your own using our developer documentation, http://dev.twitter.com/pages/tweet_button Read more about the Tweet Button on our blog, http://blog.twitter.com/2010/08/pushing-our-tweet-button.html Best Matt -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris
[twitter-dev] Re: OAuth and impact on Twitter userbase / volume
And, just to clarify, I am referring to web based api applications, where are many, all if which are affected, as xAuth is NOT, apparently, and option in this type of setup. On Aug 13, 8:54 am, Tom van der Woerdt i...@tvdw.eu wrote: On 8/13/10 4:31 AM, TheGuru wrote: I'm curious to post this question to see if Twitter has fully thought out the impact of forcing OAuth onto their API applications. While it may appear to be a more secure method preferred in principle by users, the fact of the matter is that one of the main benefits of the API, is the ability for third party twitter alternatives to be created, thus allowing people to tweet during business hours, when they normally could not due to firewall / web sense restrictions, etc, that prevent them from accessing the twitter.com domain. Via basic authentication, users would never have to visit twitter.com to login and gain access to twitter functionality via api clients. By shutting this down, you are now forcing ALL potential users to login via twitter.com, many of which do not have access to this domain in their workplace environment, thus excluding them from easily using your service wholesale. This can / will, I suspect, have significant impact on twitter usage / volume, unless I am missing something and there is an alternative the does not require them to directly access the twitter.com domain to grant access. My opinion: if your boss does not allow twitter, then don't do it. Although I have to admit that your point is valid, except for one major flaw: if twitter.com was really blocked, then the API would be blocked as well ;-) Also, some (most) desktop clients do not require you to login via OAuth, but instead they use xAuth. I'm sorry that you will no longer be able to play the silly quizzes etc, but you'll just have to live with that :-) Tom
[twitter-dev] Re: OAuth and impact on Twitter userbase / volume
API is not blocked if the twitter client (web app), is making api calls on your behalf (curl call behind the scenes). That is the crux of the problem. On Aug 13, 8:54 am, Tom van der Woerdt i...@tvdw.eu wrote: On 8/13/10 4:31 AM, TheGuru wrote: I'm curious to post this question to see if Twitter has fully thought out the impact of forcing OAuth onto their API applications. While it may appear to be a more secure method preferred in principle by users, the fact of the matter is that one of the main benefits of the API, is the ability for third party twitter alternatives to be created, thus allowing people to tweet during business hours, when they normally could not due to firewall / web sense restrictions, etc, that prevent them from accessing the twitter.com domain. Via basic authentication, users would never have to visit twitter.com to login and gain access to twitter functionality via api clients. By shutting this down, you are now forcing ALL potential users to login via twitter.com, many of which do not have access to this domain in their workplace environment, thus excluding them from easily using your service wholesale. This can / will, I suspect, have significant impact on twitter usage / volume, unless I am missing something and there is an alternative the does not require them to directly access the twitter.com domain to grant access. My opinion: if your boss does not allow twitter, then don't do it. Although I have to admit that your point is valid, except for one major flaw: if twitter.com was really blocked, then the API would be blocked as well ;-) Also, some (most) desktop clients do not require you to login via OAuth, but instead they use xAuth. I'm sorry that you will no longer be able to play the silly quizzes etc, but you'll just have to live with that :-) Tom
Re: [twitter-dev] Re: OAuth and impact on Twitter userbase / volume
In that case, just get back to work and stop tweeting :-) Tom On 8/13/10 4:15 PM, TheGuru wrote: And, just to clarify, I am referring to web based api applications, where are many, all if which are affected, as xAuth is NOT, apparently, and option in this type of setup. On Aug 13, 8:54 am, Tom van der Woerdt i...@tvdw.eu wrote: On 8/13/10 4:31 AM, TheGuru wrote: I'm curious to post this question to see if Twitter has fully thought out the impact of forcing OAuth onto their API applications. While it may appear to be a more secure method preferred in principle by users, the fact of the matter is that one of the main benefits of the API, is the ability for third party twitter alternatives to be created, thus allowing people to tweet during business hours, when they normally could not due to firewall / web sense restrictions, etc, that prevent them from accessing the twitter.com domain. Via basic authentication, users would never have to visit twitter.com to login and gain access to twitter functionality via api clients. By shutting this down, you are now forcing ALL potential users to login via twitter.com, many of which do not have access to this domain in their workplace environment, thus excluding them from easily using your service wholesale. This can / will, I suspect, have significant impact on twitter usage / volume, unless I am missing something and there is an alternative the does not require them to directly access the twitter.com domain to grant access. My opinion: if your boss does not allow twitter, then don't do it. Although I have to admit that your point is valid, except for one major flaw: if twitter.com was really blocked, then the API would be blocked as well ;-) Also, some (most) desktop clients do not require you to login via OAuth, but instead they use xAuth. I'm sorry that you will no longer be able to play the silly quizzes etc, but you'll just have to live with that :-) Tom
[twitter-dev] Re: OAuth and impact on Twitter userbase / volume
Ha, well, I'm not the one circumventing this issue at work, I'm the one who has an application with hundreds of thousands of users, many of which are now affected... On Aug 13, 9:21 am, Tom van der Woerdt i...@tvdw.eu wrote: In that case, just get back to work and stop tweeting :-) Tom On 8/13/10 4:15 PM, TheGuru wrote: And, just to clarify, I am referring to web based api applications, where are many, all if which are affected, as xAuth is NOT, apparently, and option in this type of setup. On Aug 13, 8:54 am, Tom van der Woerdt i...@tvdw.eu wrote: On 8/13/10 4:31 AM, TheGuru wrote: I'm curious to post this question to see if Twitter has fully thought out the impact of forcing OAuth onto their API applications. While it may appear to be a more secure method preferred in principle by users, the fact of the matter is that one of the main benefits of the API, is the ability for third party twitter alternatives to be created, thus allowing people to tweet during business hours, when they normally could not due to firewall / web sense restrictions, etc, that prevent them from accessing the twitter.com domain. Via basic authentication, users would never have to visit twitter.com to login and gain access to twitter functionality via api clients. By shutting this down, you are now forcing ALL potential users to login via twitter.com, many of which do not have access to this domain in their workplace environment, thus excluding them from easily using your service wholesale. This can / will, I suspect, have significant impact on twitter usage / volume, unless I am missing something and there is an alternative the does not require them to directly access the twitter.com domain to grant access. My opinion: if your boss does not allow twitter, then don't do it. Although I have to admit that your point is valid, except for one major flaw: if twitter.com was really blocked, then the API would be blocked as well ;-) Also, some (most) desktop clients do not require you to login via OAuth, but instead they use xAuth. I'm sorry that you will no longer be able to play the silly quizzes etc, but you'll just have to live with that :-) Tom
Re: [twitter-dev] Re: OAuth and impact on Twitter userbase / volume
And you have a valid point, but you can't expect Twitter to build their stuff so that people can tweet while their boss does not want them to. ;-) Tom On 8/13/10 4:26 PM, TheGuru wrote: Ha, well, I'm not the one circumventing this issue at work, I'm the one who has an application with hundreds of thousands of users, many of which are now affected... On Aug 13, 9:21 am, Tom van der Woerdt i...@tvdw.eu wrote: In that case, just get back to work and stop tweeting :-) Tom On 8/13/10 4:15 PM, TheGuru wrote: And, just to clarify, I am referring to web based api applications, where are many, all if which are affected, as xAuth is NOT, apparently, and option in this type of setup. On Aug 13, 8:54 am, Tom van der Woerdt i...@tvdw.eu wrote: On 8/13/10 4:31 AM, TheGuru wrote: I'm curious to post this question to see if Twitter has fully thought out the impact of forcing OAuth onto their API applications. While it may appear to be a more secure method preferred in principle by users, the fact of the matter is that one of the main benefits of the API, is the ability for third party twitter alternatives to be created, thus allowing people to tweet during business hours, when they normally could not due to firewall / web sense restrictions, etc, that prevent them from accessing the twitter.com domain. Via basic authentication, users would never have to visit twitter.com to login and gain access to twitter functionality via api clients. By shutting this down, you are now forcing ALL potential users to login via twitter.com, many of which do not have access to this domain in their workplace environment, thus excluding them from easily using your service wholesale. This can / will, I suspect, have significant impact on twitter usage / volume, unless I am missing something and there is an alternative the does not require them to directly access the twitter.com domain to grant access. My opinion: if your boss does not allow twitter, then don't do it. Although I have to admit that your point is valid, except for one major flaw: if twitter.com was really blocked, then the API would be blocked as well ;-) Also, some (most) desktop clients do not require you to login via OAuth, but instead they use xAuth. I'm sorry that you will no longer be able to play the silly quizzes etc, but you'll just have to live with that :-) Tom
[twitter-dev] Re: OAuth and immediate redirect back to my site without questions
On Aug 13, 8:58 am, Tom van der Woerdt i...@tvdw.eu wrote: On 8/13/10 12:15 PM, Krot Vyacheslav wrote: Hello, all! I am a newbie to twitter api, so i have a simple question. I'm making single sign on with twitter on my site. Everything works fine, but one thing reallly annoyes me! If the client is signed in twitter and has already granted access to my application twitter asks him again after redirect during request authorization phase. Can I eliminate it somehow? Can twitter just immediately redirect user back with auth_token and verifier without asking questions? Perhapse I'm doing something completely wrong? No, you can't. What? Sure you can. Instead of using the oauth/authorize call, use oauth/authenticate. Caveat: Your Twitter application must have authentication enabled. You can flip this switch yourself in the app settings page. Details on authentication: http://dev.twitter.com/pages/sign_in_with_twitter -Otto
Re: [twitter-dev] Re: Is Twitter misusing their own t.co url shortener?
Nik's analysis here is correct -- t.co links will always be 20 characters. When building a character counter in an application, you'll know that any pasted URL comprises exactly 20 characters. Taylor On Fri, Aug 13, 2010 at 6:55 AM, Nik Fletcher nik.fletc...@gmail.comwrote: I don't know how Twitter are shortening the URLs. However. IIRC Twitter's shortener is designed to always use 20 characters (I believe) so that as developers we can pass in full URLs knowing how much space each URL will take up in a tweet and show the character count accordingly. Matt / Taylor might be able to comment further though. -N -- Nik Fletcher @nikf On Aug 13, 2:17 am, D. Smith emai...@sharedlog.com wrote: How long has it been since Twitter started their own t.com url shortener? Not sure, but I don't think it's been long enough to shorten over 3.5 trillion urls. Well, I just noticed that the the url shortened by t.com was this:http://t.co/5ywZYau So the value is 5ywZYau From what I understand the shorteners work this way (at least this is the most effecient way in order to create as short a url as possible): First you create a new record for url and get the next available numeric id, usually auto increment. Then you use base62 encoding to convert this integer into a string. The result is that you get the shortest possible value consisting of lower and upper case english letters plus 10 numbers, thus a total of 62 chars are used. The number of chars needed to represent a value is 62 x 62 x 62, etc... so the 7 chars-long base 62 string can represent a number over 13 digits long. Ok, so is it really possible for this service to already shorten over a trillion urls? I don't think so. which only means that you are not doing your best to make the shortest possible url. What's the point of registering a one-letter top level domain, going through all the trouble of creating your own service and then not really doing your absolute best to make sure urls are as short as possible. I mean, you could have probably still be using 4, maybe 5 - chars long codes instead of 7, saving potential customers 2 or 3 valuable characters
Re: [twitter-dev] Re: OAuth and immediate redirect back to my site without questions
Oops, sorry, my bad. I guess you're right :-) Tom On 8/13/10 4:32 PM, Otto wrote: On Aug 13, 8:58 am, Tom van der Woerdt i...@tvdw.eu wrote: On 8/13/10 12:15 PM, Krot Vyacheslav wrote: Hello, all! I am a newbie to twitter api, so i have a simple question. I'm making single sign on with twitter on my site. Everything works fine, but one thing reallly annoyes me! If the client is signed in twitter and has already granted access to my application twitter asks him again after redirect during request authorization phase. Can I eliminate it somehow? Can twitter just immediately redirect user back with auth_token and verifier without asking questions? Perhapse I'm doing something completely wrong? No, you can't. What? Sure you can. Instead of using the oauth/authorize call, use oauth/authenticate. Caveat: Your Twitter application must have authentication enabled. You can flip this switch yourself in the app settings page. Details on authentication: http://dev.twitter.com/pages/sign_in_with_twitter -Otto
[twitter-dev] Re: OAuth and impact on Twitter userbase / volume
Yes, I understand that, and this wasn't the point for the development of the app, but it was a bonus (unintended) side affect, that, quite frankly, Twitter benefits from, in terms of usage statistics, volume, etc. And, as mentioned, I'm willing to bet this wasn't thought about during the conversion to OAuth by twitter. By cutting this collective group of users off (unintentionally), I just think it is going to have more of an impact (at least short term), than realized. On Aug 13, 9:28 am, Tom van der Woerdt i...@tvdw.eu wrote: And you have a valid point, but you can't expect Twitter to build their stuff so that people can tweet while their boss does not want them to. ;-) Tom On 8/13/10 4:26 PM, TheGuru wrote: Ha, well, I'm not the one circumventing this issue at work, I'm the one who has an application with hundreds of thousands of users, many of which are now affected... On Aug 13, 9:21 am, Tom van der Woerdt i...@tvdw.eu wrote: In that case, just get back to work and stop tweeting :-) Tom On 8/13/10 4:15 PM, TheGuru wrote: And, just to clarify, I am referring to web based api applications, where are many, all if which are affected, as xAuth is NOT, apparently, and option in this type of setup. On Aug 13, 8:54 am, Tom van der Woerdt i...@tvdw.eu wrote: On 8/13/10 4:31 AM, TheGuru wrote: I'm curious to post this question to see if Twitter has fully thought out the impact of forcing OAuth onto their API applications. While it may appear to be a more secure method preferred in principle by users, the fact of the matter is that one of the main benefits of the API, is the ability for third party twitter alternatives to be created, thus allowing people to tweet during business hours, when they normally could not due to firewall / web sense restrictions, etc, that prevent them from accessing the twitter.com domain. Via basic authentication, users would never have to visit twitter.com to login and gain access to twitter functionality via api clients. By shutting this down, you are now forcing ALL potential users to login via twitter.com, many of which do not have access to this domain in their workplace environment, thus excluding them from easily using your service wholesale. This can / will, I suspect, have significant impact on twitter usage / volume, unless I am missing something and there is an alternative the does not require them to directly access the twitter.com domain to grant access. My opinion: if your boss does not allow twitter, then don't do it. Although I have to admit that your point is valid, except for one major flaw: if twitter.com was really blocked, then the API would be blocked as well ;-) Also, some (most) desktop clients do not require you to login via OAuth, but instead they use xAuth. I'm sorry that you will no longer be able to play the silly quizzes etc, but you'll just have to live with that :-) Tom
[twitter-dev] Re: OAuth and impact on Twitter userbase / volume and freedom of speech
At least people at work have the potential to use phones to access Twitter… I'm worried about users like those in China behind The Great Firewall. Currently, they can interact with Twitter by using proxies and http basic auth. But OAuth requires access to twitter.com (or some sort of mediation). xAuth could be a solution, but there is already a shortage of clients that support alternate endpoints, and some of those use OAuth instead of xAuth (or neither). When basic auth is shut off, who knows how many Chinese voices will fall silent… or in North Korea. Or in Iran. Or in …? I'm interested in hearing what others think about this. Marsh On Aug 12, 10:31 pm, TheGuru jsort...@gmail.com wrote: I'm curious to post this question to see if Twitter has fully thought out the impact of forcing OAuth onto their API applications. While it may appear to be a more secure method preferred in principle by users, the fact of the matter is that one of the main benefits of the API, is the ability for third party twitter alternatives to be created, thus allowing people to tweet during business hours, when they normally could not due to firewall / web sense restrictions, etc, that prevent them from accessing the twitter.com domain. Via basic authentication, users would never have to visit twitter.com to login and gain access to twitter functionality via api clients. By shutting this down, you are now forcing ALL potential users to login via twitter.com, many of which do not have access to this domain in their workplace environment, thus excluding them from easily using your service wholesale. This can / will, I suspect, have significant impact on twitter usage / volume, unless I am missing something and there is an alternative the does not require them to directly access the twitter.com domain to grant access.
[twitter-dev] Re: New tweet button - is t.co mandatory?
Hi, folks- Yes indeed, t.co links will be unwrapped in the stream, so bit.ly pro users will still be able to use custom domains, along with bit.ly's analytics features. We put a post up on our blog explaining how publishers can continue to use bit.ly pro domains with the Tweet Button: http://blog.bit.ly/post/945591208/using-bit-ly-with-twitters-tweet-button And we are working on some additional tools and resources for publishers. If you have any specific questions about implementation, do not hesitate to contact supp...@bit.ly, or to e-mail me directly! Thanks- Matt LeMay m...@bit.ly On Aug 13, 10:06 am, Tom van der Woerdt i...@tvdw.eu wrote: On 8/13/10 5:04 AM, pthomsen wrote: I read in the techcrunch article, that the posting url is wrapped in t.co, but then when displayed in the stream, the url gets unwrapped again, so you should see the moxs.ie url (in my case). This doesn't happen for me. I only see the t.co url. Is there a whitelist of URLs that are accepted by twitter for 'unwrapping-in-the-stream'? If so, how do I get on that list? Thanks, Per Yesterday I noticed that t.co links were unwrapped in the search, but it looks like that is no longer the case at the moment. Probably taken offline for a few hours to perfect the algorithm, like Twitter usually does after implementing something new (happened to Lists too). It looked like all t.co links are unwrapped, so don't worry ;-) Tom
[twitter-dev] Lat,long, vs long/lat
Why is it that in most of the API, geo-co-ordinates are represented as
lat,long?
e.g. http://api.twitter.com/1/statuses/show/21059379505.json
...geo:{type:Point,coordinates:[44.6994873,-73.4529124]}...
(like most of the world does it)
but in the places API it is long,lat?
e.g.
http://api.twitter.com/1/geo/id/881e03b2b43d3810.json
{geometry:{type:Point,coordinates:[-73.452852,44.698943]}...
This is very confusing!
Cheers
Dan
Re: [twitter-dev] Re: Introducing the Tweet Button
why when I click on the count it will send me to the search for both the url of the page and the base url? On 13/08/10 9:12 AM, artesea wrote: Anyone else getting the count to work? Had several people press the button and it still shows zero, and when clicking on the zero it takes me to the search page containing their tweet, plus our autotweet everytime we do a blog post. Also will you be counting all tweets containing the URL, or only those via the button? Cheers Ryan On Aug 12, 4:28 pm, themattharristhematthar...@twitter.com wrote: Hey everyone, Today we’re launching the Tweet Button to make it easy for your users to share your website with their followers. When they click on the Tweet Button, a Tweet box will appear pre-populated with a message and link chosen by you. Once they have sent a Tweet they can choose to follow accounts recommended by you. All of this happens on your website, so the user never has to leave. You have complete control over the suggested text of the Tweet Button, who the Tweet should be attributed to and recommendations of who to follow. All of this is possible through a line of javascript and a few URL parameters or data attributes of a link. To add this to your own site grab it fromhttp://twitter.com/tweetbutton, or create your own using our developer documentation,http://dev.twitter.com/pages/tweet_button Read more about the Tweet Button on our blog,http://blog.twitter.com/2010/08/pushing-our-tweet-button.html Best Matt -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris
[twitter-dev] Streaming API (filter) and retweets, JSON Output
If we are listening to the stream api/filter using track and getting JSON output, I cannot see anywhere that I can determine if something is a retweet except explicitly checking the text of the tweet. Am I missing something or should I simultansously be listing to the retweet stream and try to cross match the 2 (that seems like a waste of resources). Any advice?
[twitter-dev] Tweet Button - Need Success, Status Text Callbacks
Facebook's JS SDK allows us to do something like the Tweet Button... pre-populate the status message, use our Application Id, etc. We'd love to use the tweet button like this too but its missing some functionality that we need. The FB JS SDK gives us a javascript callback that let's us know that a status update was posted successfully *and* it gives us the text that was posted. It'd be great if we could get the same kind of functionality from the tweet button. Adam
[twitter-dev] Important: Basic Auth will be temporarily turned off for 10 minutes at 2pm Pacific TODAY
Hi Developers, Today we're going to do a brief exercise with turning basic authentication off for 5 to 10 minutes at 2pm Pacific / 5pm Eastern. This is to simulate the effect that the deprecation of basic auth will have -- both on applications and our own servers. This is the first of such tests we'll do. During this window, clients using basic authentication will not be able to send tweets or perform any operations with the API. We haven't yet finalized the specific HTTP response we will give in this case. Today, you will receive a 403 HTTP status code while the test is active. If you're worried about whether your favorite application or integration will stop functioning when basic auth is shut down, you'll want to test during this period. Follow @twitterapi at http://twitter.com/twitterapi to keep track of the progress of the basic auth blackout period today. We'll signal when the test has begun and when it is complete. Thanks, @twitterapi/team
Re: [twitter-dev] Re: Introducing the Tweet Button
sorry if this has been asked, and did not see on the documentation. Can we see a global views of shares from our account? i.e. if Ive set up the via paramter, can I then see counts for that account? On Fri, Aug 13, 2010 at 9:49 AM, James Jones ja...@freedomnet.co.nz wrote: why when I click on the count it will send me to the search for both the url of the page and the base url? On 13/08/10 9:12 AM, artesea wrote: Anyone else getting the count to work? Had several people press the button and it still shows zero, and when clicking on the zero it takes me to the search page containing their tweet, plus our autotweet everytime we do a blog post. Also will you be counting all tweets containing the URL, or only those via the button? Cheers Ryan On Aug 12, 4:28 pm, themattharristhematthar...@twitter.com wrote: Hey everyone, Today we’re launching the Tweet Button to make it easy for your users to share your website with their followers. When they click on the Tweet Button, a Tweet box will appear pre-populated with a message and link chosen by you. Once they have sent a Tweet they can choose to follow accounts recommended by you. All of this happens on your website, so the user never has to leave. You have complete control over the suggested text of the Tweet Button, who the Tweet should be attributed to and recommendations of who to follow. All of this is possible through a line of javascript and a few URL parameters or data attributes of a link. To add this to your own site grab it fromhttp://twitter.com/tweetbutton, or create your own using our developer documentation, http://dev.twitter.com/pages/tweet_button Read more about the Tweet Button on our blog, http://blog.twitter.com/2010/08/pushing-our-tweet-button.html Best Matt -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris -- Peter Denton Co-Founder, Product Marketing www.mombo.com cell: (206) 427-3866 twitter @Mombo_movies twitter - personal: @petermdenton
Re: [twitter-dev] Send Custom Header
On Fri, Aug 13, 2010 at 7:41 AM, alex aakba...@gmail.com wrote: Accept: */* Connection: close User-Agent: OAuth gem v0.3.4.1 Authorization: abcdefgh Host: api.twitter.com how to send the above header to api.twitter.com through PHP ? http://php.net/manual/en/function.header.php ? -- Julio Biason julio.bia...@gmail.com Twitter: http://twitter.com/juliobiason
[twitter-dev] Re: Introducing the Tweet Button
I'd like a way to add this to my google site(s), but google is trying to protect me from the referenced .js - any way around this? On Aug 12, 10:28 am, themattharris thematthar...@twitter.com wrote: Hey everyone, Today we’re launching the Tweet Button to make it easy for your users to share your website with their followers. When they click on the Tweet Button, a Tweet box will appear pre-populated with a message and link chosen by you. Once they have sent a Tweet they can choose to follow accounts recommended by you. All of this happens on your website, so the user never has to leave. You have complete control over the suggested text of the Tweet Button, who the Tweet should be attributed to and recommendations of who to follow. All of this is possible through a line of javascript and a few URL parameters or data attributes of a link. To add this to your own site grab it fromhttp://twitter.com/tweetbutton, or create your own using our developer documentation,http://dev.twitter.com/pages/tweet_button Read more about the Tweet Button on our blog,http://blog.twitter.com/2010/08/pushing-our-tweet-button.html Best Matt -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris
[twitter-dev] OAuth + Whitelisting, transition questions
Hello, I'm curious to understand how the transition to OAuth will take place for whitelisted accounts. Currently I have 2 streaming accounts, which if I understand correctly will not be impacted at all, and a whitelisted basic auth access (20k/hour) for a specific set of IPs. I've read that the Basic Auth rate limit will decrease by 10 calls a day for 15 days until it's finally turned off for good. Is this still true? If so, how the decrease apply to the extended 20k/hour rate limit? Will it see a corresponding 6.6% (1320 call) reduction every day during the same period? Also, in order to have the extended rate limit I currently have available to my new OAuth application, is there anything I need to do? Or does the fact that the new OAuth application was registered under the same username and requests originate from ip combination automatically transfer the limits? Thanks for any insight you can offer. Matt
Re: [twitter-dev] OAuth + Whitelisting, transition questions
On 8/13/10 8:08 PM, Matt Trinneer wrote: Hello, I'm curious to understand how the transition to OAuth will take place for whitelisted accounts. Currently I have 2 streaming accounts, which if I understand correctly will not be impacted at all, and a whitelisted basic auth access (20k/hour) for a specific set of IPs. I've read that the Basic Auth rate limit will decrease by 10 calls a day for 15 days until it's finally turned off for good. Is this still true? If so, how the decrease apply to the extended 20k/hour rate limit? Will it see a corresponding 6.6% (1320 call) reduction every day during the same period? Also, in order to have the extended rate limit I currently have available to my new OAuth application, is there anything I need to do? Or does the fact that the new OAuth application was registered under the same username and requests originate from ip combination automatically transfer the limits? Thanks for any insight you can offer. Matt Hi Matt, I would like to point out that I think that you should stop worrying about the Basic Auth rate limiting and simply implement OAuth. It's about time that you do so anyway. Your extended limit is IP-based and does not care about the type you use - basic or OAuth. Tom
[twitter-dev] Drop on Twitter from @Anywhere Follow Buttons
Do you know if there is a way to drop the on Twitter after the username in the @Anywhere Follow Buttons? I feel the leading Twitter t logo is sufficient for the targeted audience coming to my site. I would also like to set a standard width is possible.
Re: [twitter-dev] Re: OAuth and impact on Twitter userbase / volume and freedom of speech
IHMO the discussion of international politics and social media should take place in a wider forum, such as Twitter itself, and not be limited to oAuth vs. basic authentication. ;-) There was a keynote speech at Open Source Bridge 2010 by Danny O'Brien about this - see http://opensourcebridge.org/sessions/478 and http://www.cpj.org/ to get started. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting earth2marsh ma...@earth2marsh.com: At least people at work have the potential to use phones to access Twitter… I'm worried about users like those in China behind The Great Firewall. Currently, they can interact with Twitter by using proxies and http basic auth. But OAuth requires access to twitter.com (or some sort of mediation). xAuth could be a solution, but there is already a shortage of clients that support alternate endpoints, and some of those use OAuth instead of xAuth (or neither). When basic auth is shut off, who knows how many Chinese voices will fall silent… or in North Korea. Or in Iran. Or in …? I'm interested in hearing what others think about this. Marsh On Aug 12, 10:31 pm, TheGuru jsort...@gmail.com wrote: I'm curious to post this question to see if Twitter has fully thought out the impact of forcing OAuth onto their API applications. While it may appear to be a more secure method preferred in principle by users, the fact of the matter is that one of the main benefits of the API, is the ability for third party twitter alternatives to be created, thus allowing people to tweet during business hours, when they normally could not due to firewall / web sense restrictions, etc, that prevent them from accessing the twitter.com domain. Via basic authentication, users would never have to visit twitter.com to login and gain access to twitter functionality via api clients. By shutting this down, you are now forcing ALL potential users to login via twitter.com, many of which do not have access to this domain in their workplace environment, thus excluding them from easily using your service wholesale. This can / will, I suspect, have significant impact on twitter usage / volume, unless I am missing something and there is an alternative the does not require them to directly access the twitter.com domain to grant access.
[twitter-dev] geo/search international POIs
I am finding that POI level results are pretty good in the US but I usually cant get anything below the neighborhood level for POIs internationally, even in big cites such as Rome. Is there a place I can go to to understand what POI support is available from geo/search? http://ratecred.com Clay Graham
[twitter-dev] Re: OAuth and impact on Twitter userbase / volume and freedom of speech
Add that to the list of even more reasons why this is an issue. However, even stating oh well, tell them to use their cell phones, obviously isn't a solution of any degree. Smart Phone penetration in the US, for example, is still less than 20%... On Aug 13, 9:43 am, earth2marsh ma...@earth2marsh.com wrote: At least people at work have the potential to use phones to access Twitter… I'm worried about users like those in China behind The Great Firewall. Currently, they can interact with Twitter by using proxies and http basic auth. But OAuth requires access to twitter.com (or some sort of mediation). xAuth could be a solution, but there is already a shortage of clients that support alternate endpoints, and some of those use OAuth instead of xAuth (or neither). When basic auth is shut off, who knows how many Chinese voices will fall silent… or in North Korea. Or in Iran. Or in …? I'm interested in hearing what others think about this. Marsh On Aug 12, 10:31 pm, TheGuru jsort...@gmail.com wrote: I'm curious to post this question to see if Twitter has fully thought out the impact of forcing OAuth onto their API applications. While it may appear to be a more secure method preferred in principle by users, the fact of the matter is that one of the main benefits of the API, is the ability for third party twitter alternatives to be created, thus allowing people to tweet during business hours, when they normally could not due to firewall / web sense restrictions, etc, that prevent them from accessing the twitter.com domain. Via basic authentication, users would never have to visit twitter.com to login and gain access to twitter functionality via api clients. By shutting this down, you are now forcing ALL potential users to login via twitter.com, many of which do not have access to this domain in their workplace environment, thus excluding them from easily using your service wholesale. This can / will, I suspect, have significant impact on twitter usage / volume, unless I am missing something and there is an alternative the does not require them to directly access the twitter.com domain to grant access.
[twitter-dev] alerts on share button alerts
Hello, seeing tons of reports about alerts happening because of the share button. i.e. it alerts every variable. Anyone else seeing this?
[twitter-dev] anywhere back button bug in IE
As early as Monday, I'm getting reports of extra history states logged in IE from my users. I've run my code that uses @anywhere with and without anywhere.js on the page and have confirmed that 2 extra history entries are being created by including the platform, and then one new state is being logged for each twttr.anywhere call I make. Could something have changed with the platform js recently that might explain this?
[twitter-dev] Re: alerts on share button alerts
Would be great if there was an official response from Twitter on this. If the problem is fixed and its a user cache problem persisting the error, could a simple fix be to add a random number to the JS URL? On Aug 13, 3:32 pm, Clint Ecker clintec...@gmail.com wrote: I had some people reporting it on Ars Technica, but it appears to have been fixed now. If it's still happening its likely users have the JavaScript cached and they need to clear their browser's cache. That being said, we have a lot of very unhappy readers right now ;( Clint On Fri, Aug 13, 2010 at 2:26 PM, Tom van der Woerdt i...@tvdw.eu wrote: On 8/13/10 9:24 PM, Peter Denton wrote: Hello, seeing tons of reports about alerts happening because of the share button. i.e. it alerts every variable. Anyone else seeing this? Yes - I just noticed it at well. You are not the only one. Tom -- Clint Ecker --http://blog.clintecker.com c: 312.863.9323 --- twitter: clint skype: clintology AIM: clintecker Gtalk: clintec...@gmail.com
Re: [twitter-dev] Twitter dialog after adding official tweet buttons to site (FF/Win)
On 8/13/10 10:38 PM, Jerry Thompson wrote: Hi All, Getting a weird JS dialog box in Firefox/Win after adding the tweet buttons from Twitter today. Does the error code 1281727137826 mean anything in particular? I cannot reproduce this problem in FF/Mac, Safari/Mac. But I received a number of emails about it and they all seem to have FF/Win. Screenshot at: http://twitrpix.com/bk9h Best, Jerry Consider this your official reply : http://twitter.com/episod/status/21093220762 It was a temporary issue at Twitter's javascript but it is solved now :-) Tom
[twitter-dev] SMS Fast Follow Analytics
Currently you can see who is following you with a Twitter account. Is there going to be a way to see what people are following you via SMS Fast Follow. Any form of Analytics, whether it is the phone number, number of followers, mobile carrier, etc. etc.
[twitter-dev] Open Source Android/Twitter Application
When the Google/Twitter application for android came out last May it was widely announced that this application was going to be made open source as an example to developers how to use best practices and patterns when developing applications for android, as well as OAuth. http://android-developers.blogspot.com/2010/05/twitter-for-android-closer-look-at.html Don’t think we quite got something right? As many of you know, we’ll soon be open sourcing this application code under the Android Open Source Project. We look forward to seeing what you can build starting from this code these UI patterns. In the meantime, Happy Tweeting! --- Tim Bray, Google May, 2010 http://blog.twitter.com/2010/04/twitter-for-android-robots-like-to.html http://appmodo.com/18732/twitter-launches-open-source-app-for-android/ http://www.engadget.com/2010/04/30/official-twitter-for-android-app-goes-live-will-be-included-in/ I have asked a number of people at Google when and where this will be made available with no avail. I have searched google code, maybe some of you know something I dont. If anyone has a pointer to this code base it would be greatly appreciated. Clay http://ratecred.com
Re: [twitter-dev] Open Source Android/Twitter Application
Now that I finally have an Android handset, I'm interested in this as well. Clay Graham claytan...@sightlyinc.com wrote: When the Google/Twitter application for android came out last May it was widely announced that this application was going to be made open source as an example to developers how to use best practices and patterns when developing applications for android, as well as OAuth. http://android-developers.blogspot.com/2010/05/twitter-for-android-closer-look-at.html Don’t think we quite got something right? As many of you know, we’ll soon be open sourcing this application code under the Android Open Source Project. We look forward to seeing what you can build starting from this code these UI patterns. In the meantime, Happy Tweeting! --- Tim Bray, Google May, 2010 http://blog.twitter.com/2010/04/twitter-for-android-robots-like-to.html http://appmodo.com/18732/twitter-launches-open-source-app-for-android/ http://www.engadget.com/2010/04/30/official-twitter-for-android-app-goes-live-will-be-included-in/ I have asked a number of people at Google when and where this will be made available with no avail. I have searched google code, maybe some of you know something I dont. If anyone has a pointer to this code base it would be greatly appreciated. Clay http://ratecred.com -- Dossy Shiobara
Re: [twitter-dev] Open Source Android/Twitter Application
I suspect Google's priorities have changed, as have Twitter's. Tim Bray is very accessible in social media - I recommend talking directly to him. ;-) -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Dossy Shiobara do...@panoptic.com: Now that I finally have an Android handset, I'm interested in this as well. Clay Graham claytan...@sightlyinc.com wrote: When the Google/Twitter application for android came out last May it was widely announced that this application was going to be made open source as an example to developers how to use best practices and patterns when developing applications for android, as well as OAuth. http://android-developers.blogspot.com/2010/05/twitter-for-android-closer-look-at.html Don’t think we quite got something right? As many of you know, we’ll soon be open sourcing this application code under the Android Open Source Project. We look forward to seeing what you can build starting from this code these UI patterns. In the meantime, Happy Tweeting! --- Tim Bray, Google May, 2010 http://blog.twitter.com/2010/04/twitter-for-android-robots-like-to.html http://appmodo.com/18732/twitter-launches-open-source-app-for-android/ http://www.engadget.com/2010/04/30/official-twitter-for-android-app-goes-live-will-be-included-in/ I have asked a number of people at Google when and where this will be made available with no avail. I have searched google code, maybe some of you know something I dont. If anyone has a pointer to this code base it would be greatly appreciated. Clay http://ratecred.com -- Dossy Shiobara
Re: [twitter-dev] Twitter API keys fail to verify
On 8/13/10 11:58 PM, Gurpartap Singh wrote: Will talk in points: # An existing OAuth app which already has xAuth access, works perfectly in the implementation. # Created a new OAuth app with Twitter. Got xAuth access for it through email. # Replaced the implementation's API keys to the new OAuth app's API keys. # Getting 401 error on OAuth echo attempt with Twitpic. # If the original API key is used, it works fine. # Use Twitter for login is checked in new OAuth app's settings. # Requested Twitter to look if it really has access. They verified it to have xAuth access. Where's the catch? Yikes, points. I prefer numbers :-) 1. Don't use the same user keys for different consumer keys. 2. OAuth echo is not dependent on xAuth 3. If your application is a desktop application, you should not check Use Twitter for login. Tom
[twitter-dev] Twitter API the Basic Auth Shutdown: Everything you need to know.
Hi Developers, Basic authentication is being deprecated beginning on August 16th. After August 31st, API clients will no longer be able to identify themselves using only a login and password when accessing the Twitter REST API. For those that just like to skim, here are the basics: - Basic Auth will be completely shut off on August 30th. - Beginning Aug 17, basic auth rate limiting will decrease by 15 requests on each week day (10% drop per weekday) - Aug 16, 8am Pacific - we'll shut basic auth temporarily off for 10 minutes - Aug 31, 5pm Pacific - we'll shut basic auth temporarily for 10 minutes - On August 30th, all basic auth requests will be served with a 401 HTTP status code. We've discussed at length in the past why this transition is important. We recognize that it significantly increases the difficulty of working with the Twitter API. OAuth is not a silver bullet for security, but protects our users and the platform ecosystem notably better than basic authentication. Today, non-whitelisted basic authentication GET requests are limited to 150 calls per hour. POST operations, such as tweeting, are not effected by this limit. Basic auth apps can continue tweeting with impunity until the full turn off occurs on August 31st. Beginning August 17th, non-whitelisted basic authentication GET requests will be limited to 135 calls per hour. We will reduce the number of calls per hour by 15 each week day until August 31st. This means on August 18th Basic Authentication will be allowed 120 GET requests per hour, August 19th 105 GET requests per hour and so on. The decrement will happen on each Monday, Tuesday, Wednesday, Thursday, and Friday until August 31st. For whitelisted basic auth requests, the decrement will be comparative to the general ramp down levels -- about 10% of your total rate limit will decrement every day starting on August 16th. On August 31st, whitelisted basic auth requests will cease functioning as well. On August 31st, all basic auth requests will be serviced a 401 HTTP status code. You may have noticed that we temporarily shut basic authentication off today for 10 minutes. We gave minimal notice today, and recognize that more notice would have been optimal. We will be doing these integration tests a few more times before the total deprecation date. The next basic auth switch-off will occur on Monday, August 16th at 8am Pacific for 10 minutes. After that, we'll do another of these tests on Thursday, August 19th at 5pm Pacific for another 10 minutes. We'll do more of these after that, and we'll announce them closer to that time. As always, follow @twitterapi to keep track in real time. If you haven't started transitioning your application, we recommend reading our write up at http://dev.twitter.com/pages/basic_to_oauth and leveraging the Twitter Developer mailing list when you need assistance. As always, we're here to help. Let's walk into this new morning together. Thanks, Taylor Singletary Developer Advocate, Twitter Platform http://twitter.com/episod
[twitter-dev] OAuth with Rails help getting going
Hello,
I'm not having success with the following code, I get a Sorry, page
doesn't exist! webpage. I am using the OAuth v0.4.1 gem. Your help and
guidance is very appreciated, thanks!
If I type the following out in IRB, it seems to work, but of course I
can't redirect from the shell.
class HomeController ApplicationController
def index
@consumer = OAuth::Consumer.new( bLI9szbXTJQnXKA,
XXm41S6SYEy9uYR5oiAUxToPvQUlMd6g9A,
{ :site=https://api.twitter.com/oauth/request_token; } )
@request_tok...@consumer.get_request_token
session[:consumer] = @consumer
session[:request_token] = @request_token
redirect_to @request_token.authorize_url
end
end
--
Kind Regards,
Rajinder Yadav
[twitter-dev] Re: Open Source Android/Twitter Application
Ed, Thanks for the advice. I have emailed Tim directly, no reply. Will keep trying. Can I be the only one who is hungry for this? Clay On Aug 13, 2:35 pm, M. Edward (Ed) Borasky zn...@borasky- research.net wrote: I suspect Google's priorities have changed, as have Twitter's. Tim Bray is very accessible in social media - I recommend talking directly to him. ;-) -- M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Dossy Shiobara do...@panoptic.com: Now that I finally have an Android handset, I'm interested in this as well. Clay Graham claytan...@sightlyinc.com wrote: When the Google/Twitter application for android came out last May it was widely announced that this application was going to be made open source as an example to developers how to use best practices and patterns when developing applications for android, as well as OAuth. http://android-developers.blogspot.com/2010/05/twitter-for-android-cl... Don’t think we quite got something right? As many of you know, we’ll soon be open sourcing this application code under the Android Open Source Project. We look forward to seeing what you can build starting from this code these UI patterns. In the meantime, Happy Tweeting! --- Tim Bray, Google May, 2010 http://blog.twitter.com/2010/04/twitter-for-android-robots-like-to.html http://appmodo.com/18732/twitter-launches-open-source-app-for-android/ http://www.engadget.com/2010/04/30/official-twitter-for-android-app-g... I have asked a number of people at Google when and where this will be made available with no avail. I have searched google code, maybe some of you know something I dont. If anyone has a pointer to this code base it would be greatly appreciated. Clay http://ratecred.com -- Dossy Shiobara
Re: [twitter-dev] Re: Open Source Android/Twitter Application
On second thought, though, given the rapidity at which Twitter is deploying new features to twitter.com via standard Javascript libraries, maybe there's a future for a pure Javascript in-browser open source Twitter client, which I think could run in the Android browser. You really only need a server if you're going to do more sophisticated MVC stuff, and some of the Javascript frameworks, like Sproutcore, can even do that. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Clay Graham claytan...@sightlyinc.com: Ed, Thanks for the advice. I have emailed Tim directly, no reply. Will keep trying. Can I be the only one who is hungry for this? Clay On Aug 13, 2:35 pm, M. Edward (Ed) Borasky zn...@borasky- research.net wrote: I suspect Google's priorities have changed, as have Twitter's. Tim Bray is very accessible in social media - I recommend talking directly to him. ;-) -- M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Dossy Shiobara do...@panoptic.com: Now that I finally have an Android handset, I'm interested in this as well. Clay Graham claytan...@sightlyinc.com wrote: When the Google/Twitter application for android came out last May it was widely announced that this application was going to be made open source as an example to developers how to use best practices and patterns when developing applications for android, as well as OAuth. http://android-developers.blogspot.com/2010/05/twitter-for-android-cl... Don’t think we quite got something right? As many of you know, we’ll soon be open sourcing this application code under the Android Open Source Project. We look forward to seeing what you can build starting from this code these UI patterns. In the meantime, Happy Tweeting! --- Tim Bray, Google May, 2010 http://blog.twitter.com/2010/04/twitter-for-android-robots-like-to.html http://appmodo.com/18732/twitter-launches-open-source-app-for-android/ http://www.engadget.com/2010/04/30/official-twitter-for-android-app-g... I have asked a number of people at Google when and where this will be made available with no avail. I have searched google code, maybe some of you know something I dont. If anyone has a pointer to this code base it would be greatly appreciated. Clay http://ratecred.com -- Dossy Shiobara
Re: [twitter-dev] Re: Open Source Android/Twitter Application
Yeah - but I turn that off on my Verizon Droid Incredible (along with WiFi, Bluetooth and GPS) to conserve battery anyhow. ;-) -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Dossy Shiobara do...@panoptic.com: The one benefit to having an on-device application is for background polling and notifications. On 8/13/10 11:08 PM, M. Edward (Ed) Borasky wrote: On second thought, though, given the rapidity at which Twitter is deploying new features to twitter.com via standard Javascript libraries, maybe there's a future for a pure Javascript in-browser open source Twitter client, which I think could run in the Android browser. You really only need a server if you're going to do more sophisticated MVC stuff, and some of the Javascript frameworks, like Sproutcore, can even do that. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
Re: [twitter-dev] Re: Open Source Android/Twitter Application
Clay, I've been waiting for it too! Hopefully they don't back out of the promise. Regards, Brad Bosley On Fri, Aug 13, 2010 at 6:07 PM, Clay Graham claytan...@sightlyinc.com wrote: Ed, Thanks for the advice. I have emailed Tim directly, no reply. Will keep trying. Can I be the only one who is hungry for this? Clay
[twitter-dev] Re: OAuth with Rails help getting going
On 10-08-13 08:35 PM, Rajinder Yadav wrote:
Hello,
I'm not having success with the following code, I get a Sorry, page
doesn't exist! webpage. I am using the OAuth v0.4.1 gem. Your help
and guidance is very appreciated, thanks!
If I type the following out in IRB, it seems to work, but of course I
can't redirect from the shell.
class HomeController ApplicationController
def index
@consumer = OAuth::Consumer.new( bLI9szbXTJQnXKA,
XXm41S6SYEy9uYR5oiAUxToPvQUlMd6g9A,
{ :site=https://api.twitter.com/oauth/request_token; } )
@request_tok...@consumer.get_request_token
session[:consumer] = @consumer
session[:request_token] = @request_token
redirect_to @request_token.authorize_url
end
end
Hi I found by making the following change I now see the allow/deny page.
However when I click on allow, I do not get redirected back to my
callback page?
@consumer = OAuth::Consumer.new( bLI9szbXTJQnXKA,
XXm41S6SYEy9uYR5oiAUxToPvQUlMd6g9A,
:site=https://twitter.com;,
:request_token_path = /oauth/request_token,
:authorize_path = /oauth/authorize,
:access_token_path = /oauth/access_token,
:http_method = :get ) )
What I am seeing in the pin page, saying:
You've successfully granted access to _TestApp!
Simply return to _TestApp and enter the following PIN to complete
the process.
How do I get Twitter to return back to my callback page on my site? My
app type is correctly set to browser.
--
Kind Regards,
Rajinder Yadav
[twitter-dev] People randomly getting unfollowed?
I don't think this has happened to me, but a number of my friends and some well-known Twitter people have reported that Twitter is unfollowing people from their accounts on its own, apparently in some random fashion. I don't have any more detail than that, or I'd file an issue. But I've heard it from so many people that I wanted to bring it up here and see if this triggers any thoughts in the developer community or at Twitter. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos
