[twitter-dev] Re: BlackBerry, XAuth and twitterapime
It seems like everyone like having trouble moving from basic to Oauth
in mobile.
TwitterAPIME works on BB via J2ME Twitter lib from Kenai. This library
also supports Android. But this lib author develop this lib in his
spare time so he didn't include every Twitter API. It can only do a
few things.
http://kenai.com/projects/twitterapime/pages/Home
Any BB developer can tell me which JS lib BB would support on their
Javascript API?
On Aug 7, 4:33 am, kmba...@gmail.com wrote:
Yes BlackBerry is Java ME, but it also has it's own API quirks and I was
unable to get one of the existing libraries to work for me.
I am doing the communication on my own. May app have been working fine using
BASIC. I have just had a hard time moving it over to OAuth based.
Sent via BlackBerry by ATT
-Original Message-
From: Bess bess...@gmail.com
Sender: twitter-development-talk@googlegroups.com
Date: Fri, 6 Aug 2010 22:06:12
To: Twitter Development Talktwitter-development-talk@googlegroups.com
Reply-To: twitter-development-talk@googlegroups.com
Subject: [twitter-dev] Re: BlackBerry, XAuth and twitterapime
If Twitter4J do not run on BB, which OAuth or xAuth lib do you use in
BB?
There is no other Java option in BB? You have to use J2ME in BB?
What about webos BB has announced?
Can I port my Java code from Android straight to BB? How much code re
factoring or rewrite I have to do to move from Android to BB?
On Aug 6, 10:23 am, Ernandes Jr. ernan...@gmail.com wrote:
BB is powered by Java ME and some specific RIM Java APIs.
On Fri, Aug 6, 2010 at 8:26 AM, David Francisco Tavárez
davidftava...@gmail.com wrote:
Twitter4J do not run on BB.
2010/8/6, Bess bess...@gmail.com:
I am able to use Twitter4J Oauth in Android SDK 2.1. Can you do the
same on BB?
Does BB has the same JAVA environment similar to Android? I assume
J2SE is very different than Android Java?
On Aug 5, 4:52 pm, BBTweet Media Player bbtweetme...@gmail.com
wrote:
Ernandes,
Thanks for the response. I am sure there is something small I am
doing wrong. I did grab twitter4j and made a simple j2se app to make
sure I could use my consumer key and secret and XAuth worked. So I
know my account is good at least. I am now trying to hand code the
example onhttp://dev.twitter.com/pages/xauthtomakesure I can
properly encode a header. Everything worked fine using BASIC. I do
not see why they had to make it so hard.
I am using the BB 5 and 6 OSs.
On Aug 5, 2:39 pm, Ernandes Jr. ernan...@gmail.com wrote:
I do not have a BB to test the API. However, I have received some
e-mails
from people facing same problem as you. Some of them were making some
small
mistakes and then it worked, however, others did not have much
success.
At
this moment, I am trying to find the route cause of many problems
with
BB. I
hope to find it soon and then release a fix for release 1.4.
By the way. which is your BB's OS version?
Regards,
Ernandes
On Thu, Aug 5, 2010 at 4:56 AM, Bess bess...@gmail.com wrote:
Which OAuth library did you use on your BB? Did you use the Java
library?
On Aug 4, 7:42 am, Ernandes Jr. ernan...@gmail.com wrote:
Hi,
I suggest you to get in touch to Twitter API ME support before
replacing
codes. Send an e-mail to supp...@twapime.com or check project's
forum
page:http://kenai.com/projects/twitterapime/forums/forum
Maybe your issues are already discussed there.
Regards,
Ernandes
On Tue, Aug 3, 2010 at 9:21 PM, BBTweet Media Player
bbtweetme...@gmail.com
wrote:
I am having a very difficult time trying to get XAuth working
in
my
BlackBerry app. I have downloaded twitterapime the hmacsha
ecodingand
Base64Ecoder did not seem to work for me so I replaced the
getSignature method in XAuthSigner with...
/**
* p
* Generate a signature from the given base string.
* /p
* @param baseString Base string.
* @param consumerSecret Consumer secret.
* @param tokenSecret Token secret.
* @return Signature.
*/
private static String getSignature(String baseString,
String
consumerSecret,
String tokenSecret) {
// byte[] b = HMAC.getHmac(baseString,
consumerSecret
+
'' +
tokenSecret);
// //
// return Base64Encoder.encode(b);
String ret = null;
try {
ret = hmacsha1(baseString,
consumerSecret
+
''
+
tokenSecret);
} catch (Exception e) {
[twitter-dev] Re: OAuth singing on BlackBerry
Is twitterapime the only OAuth lib for BB?
Anyone is able to use Twitter4J / SignOAuth in BB J2ME?
On Aug 7, 5:13 am, David Francisco Tavárez davidftava...@gmail.com
wrote:
Why don't you use twitterapime?
2010/8/7, BBTweet Media Player bbtweetme...@gmail.com:
BB is J2ME but has some quirks that did not allow me to use the
library I tired. I am just handling the twitter communication on my
own.
On Aug 7, 1:01 am, Bess bess...@gmail.com wrote:
You need Twitter to approve before you can use xAuth. xAuth is
different than OAuth.
Can I ask which xAuth library did you use on BB? Is that Java? not
J2ME
On Aug 6, 1:03 pm, BBTweet Media Player bbtweetme...@gmail.com
wrote:
WHOOO! I got my first 200 getting an XAuth request token.
I think the answer to my question is no, I am not expected to get the
same signature the have in the XAuth example but it always the same on
my device. My final problem was I was not URL encoding the signature
before placing it into the Authorization header.
Thanks for all the help here hoping to things moving forward quicker.
I spent way to long trying to figure that out.
On Aug 6, 2:34 pm, BBTweet Media Player bbtweetme...@gmail.com
wrote:
Tom,
Thanks for the reply. That is what I tried to do here. I used the
exact same values presented on the XAuth
pagehttp://dev.twitter.com/pages/xauth.
Everything was exactly the same upto the point where I ran the HMAC-
SHA1 encoding
String signature = hmacsha1(signingSecret, baseString);
The signature was not the same as the signature the showed in the
example. My first question is should it be if I run SHA1 encoding
will with the same input should it always return the exact same string
(I just do not know much about the encoding)? If it should be the
exact same this means that my problem is definitively in the encoding
step. If so can anyone see what I might be doing wrong in the signing
step...
HMACKey k = new HMACKey(key.getBytes());
HMAC hmac = new HMAC(k, new SHA1Digest());
hmac.update(message.getBytes());
byte[] mac = hmac.getMAC();
return Base64OutputStream.encodeAsString(mac, 0, mac.length,
false, false);
Thanks,
Kevin
On Aug 6, 10:31 am, Tom allerleiga...@gmail.com wrote:
Hi,
I don't have a java compiler ready so I can't test your code.
The page about xAuth shows all steps between the start and the
actual
signature. Try reproducing every single one of these values.
(Usually
you can simply log all steps and then compare the results with the
xauth page.)
Tom
On Aug 6, 2:56 am, BBTweet Media Player bbtweetme...@gmail.com
wrote:
I am having a really tough time trying to figure out how to sign
my
OAuth request. I am trying to follow the example
athttp://dev.twitter.com/pages/xauth
and my signature does not come out the same as it does in the
example...
I am doing
public static void xauth(){
try {
String twitter_url=https://api.twitter.com/oauth/
access_token;
String oauth_consumer_key = sGNxxnqgZRHUt6NunK3uw;
String oauth_consumer_secret =
5kEQypKe7lFHnufLtsocB1vAzO07xLFgp2Pc4sp2vk;
String oauth_nonce =
WLxsobj4rhS2xmCbaAeT4aAkRfx4vSHX4OnYpTE77hA;
String oauth_signature_method = HMAC-SHA1;
String oauth_timestamp = 1276101652;
String oauth_version = 1.0;
String x_auth_mode = client_auth;
String x_auth_password = %123!aZ+()456242134;
String x_auth_username = tpFriendlyGiant;
String postBody = x_auth_mode=+x_auth_mode
+x_auth_password=+encodeUTF8(x_auth_password)+
x_auth_username=+encodeUTF8(x_auth_username);
String baseString = POST+encodeUTF8(twitter_url)+
oauth_consumer_key%3D+oauth_consumer_key +
%26oauth_nonce%3D+oauth_nonce+
%26oauth_signature_method%3D+oauth_signature_method+
%26oauth_timestamp%3D+oauth_timestamp+
%26oauth_version%3D+oauth_version+
%26+encodeUTF8(postBody);
String signingSecret =
encodeUTF8(oauth_consumer_secret)
+;
String signature = hmacsha1(signingSecret,
baseString);
String header = new StringBuffer(OAuth oauth_nonce=
\).append(oauth_nonce).append(\, oauth_signature_method=\)
.append(oauth_signature_method).append(\,
oauth_timestamp=\).append(oauth_timestamp).append(\,
oauth_consumer_key=\)
.append(oauth_consumer_key).append(\,
Re: [twitter-dev] OAuth singing on BlackBerry
Twittterapime is the only java me library for oauth
2010/8/9, Bess bess...@gmail.com:
Is twitterapime the only OAuth lib for BB?
Anyone is able to use Twitter4J / SignOAuth in BB J2ME?
On Aug 7, 5:13 am, David Francisco Tavárez davidftava...@gmail.com
wrote:
Why don't you use twitterapime?
2010/8/7, BBTweet Media Player bbtweetme...@gmail.com:
BB is J2ME but has some quirks that did not allow me to use the
library I tired. I am just handling the twitter communication on my
own.
On Aug 7, 1:01 am, Bess bess...@gmail.com wrote:
You need Twitter to approve before you can use xAuth. xAuth is
different than OAuth.
Can I ask which xAuth library did you use on BB? Is that Java? not
J2ME
On Aug 6, 1:03 pm, BBTweet Media Player bbtweetme...@gmail.com
wrote:
WHOOO! I got my first 200 getting an XAuth request token.
I think the answer to my question is no, I am not expected to get the
same signature the have in the XAuth example but it always the same
on
my device. My final problem was I was not URL encoding the signature
before placing it into the Authorization header.
Thanks for all the help here hoping to things moving forward quicker.
I spent way to long trying to figure that out.
On Aug 6, 2:34 pm, BBTweet Media Player bbtweetme...@gmail.com
wrote:
Tom,
Thanks for the reply. That is what I tried to do here. I used the
exact same values presented on the XAuth
pagehttp://dev.twitter.com/pages/xauth.
Everything was exactly the same upto the point where I ran the
HMAC-
SHA1 encoding
String signature = hmacsha1(signingSecret, baseString);
The signature was not the same as the signature the showed in the
example. My first question is should it be if I run SHA1 encoding
will with the same input should it always return the exact same
string
(I just do not know much about the encoding)? If it should be the
exact same this means that my problem is definitively in the
encoding
step. If so can anyone see what I might be doing wrong in the
signing
step...
HMACKey k = new HMACKey(key.getBytes());
HMAC hmac = new HMAC(k, new SHA1Digest());
hmac.update(message.getBytes());
byte[] mac = hmac.getMAC();
return Base64OutputStream.encodeAsString(mac, 0,
mac.length,
false, false);
Thanks,
Kevin
On Aug 6, 10:31 am, Tom allerleiga...@gmail.com wrote:
Hi,
I don't have a java compiler ready so I can't test your code.
The page about xAuth shows all steps between the start and the
actual
signature. Try reproducing every single one of these values.
(Usually
you can simply log all steps and then compare the results with
the
xauth page.)
Tom
On Aug 6, 2:56 am, BBTweet Media Player bbtweetme...@gmail.com
wrote:
I am having a really tough time trying to figure out how to
sign
my
OAuth request. I am trying to follow the example
athttp://dev.twitter.com/pages/xauth
and my signature does not come out the same as it does in the
example...
I am doing
public static void xauth(){
try {
String twitter_url=https://api.twitter.com/oauth/
access_token;
String oauth_consumer_key =
sGNxxnqgZRHUt6NunK3uw;
String oauth_consumer_secret =
5kEQypKe7lFHnufLtsocB1vAzO07xLFgp2Pc4sp2vk;
String oauth_nonce =
WLxsobj4rhS2xmCbaAeT4aAkRfx4vSHX4OnYpTE77hA;
String oauth_signature_method = HMAC-SHA1;
String oauth_timestamp = 1276101652;
String oauth_version = 1.0;
String x_auth_mode = client_auth;
String x_auth_password = %123!aZ+()456242134;
String x_auth_username = tpFriendlyGiant;
String postBody = x_auth_mode=+x_auth_mode
+x_auth_password=+encodeUTF8(x_auth_password)+
x_auth_username=+encodeUTF8(x_auth_username);
String baseString =
POST+encodeUTF8(twitter_url)+
oauth_consumer_key%3D+oauth_consumer_key +
%26oauth_nonce%3D+oauth_nonce+
%26oauth_signature_method%3D+oauth_signature_method+
%26oauth_timestamp%3D+oauth_timestamp+
%26oauth_version%3D+oauth_version+
%26+encodeUTF8(postBody);
String signingSecret =
encodeUTF8(oauth_consumer_secret)
+;
String signature = hmacsha1(signingSecret,
baseString);
String header = new StringBuffer(OAuth
oauth_nonce=
\).append(oauth_nonce).append(\,
oauth_signature_method=\)
.append(oauth_signature_method).append(\,
[twitter-dev] Re: Can we use localhost to tweet messages using oAuth authentication??
I also have a problem with this. I cannot use the twitter API login with OAuth when I am debugging on localhost. I tought that it is not possible to use Twitter authentication on localhost because of the callback url. So I tought that I have to upload my site somewhere before. Sincerely, Jure On 8 avg., 07:30, punit khaire punit.kha...@gmail.com wrote: Thanks Tom, I am using localhost to tweet messages but it is giving error message as Failed to authenticate with oauthe signature and token.Is this happening because I had given callback URL.I am generating proper signature and sending all parameters. I am not getting where I am going wrong . Punit. On Sun, Aug 8, 2010 at 5:13 AM, Tom allerleiga...@gmail.com wrote: Yes, you can. Any application that can sign oAuth requests can send tweets. Tom On Aug 7, 2:44 pm, Punit.khaire punit.kha...@gmail.com wrote: Can we use localhost to tweet messages using oAuth authentication??
[twitter-dev] Some twitterapi updates unavailable
I tried to 'favorite' an update by twitterapi over the weekend in
twitter, nothing happened, so I tried to read that update in my own
application -- and I then tried to read a few other updates from
twitterapi. I get back a statuses list in home timeline, then I try to
read more information about the updates in question, and I always get
an error. I think twitter must also get an error, since those updates
seem to be unavailable there too. Here is what I see in my debug
output for one of these updates, any ideas?
{request:/1/statuses/show/20499308096.json,error:No status
found with that ID.}
I get the ID from the updates listed in a getstatusesHometimeline. I
would suspect my application, but it does this for everything else
fine, and only a subset of updates/statuses from twitterapi seem to be
failing, and twitter itself is failing to allow a favorite (for
instance) on these. Are these just 'lost' statuses/updates which I
should not worry about?
thanks,
Mark
Re: [twitter-dev] Some twitterapi updates unavailable
Hi Mark,
We're looking into this and are not quite sure what's going on with these
particular statuses. If you come across any other status ids that can't be
fetched via statuses/show, cannot be favorited, or retweeted (all three
actions fail with these particular tweets), please let us know the status id
so we're aware.
Thanks,
Taylor
On Mon, Aug 9, 2010 at 3:48 AM, Mark Krieger markskrie...@gmail.com wrote:
I tried to 'favorite' an update by twitterapi over the weekend in
twitter, nothing happened, so I tried to read that update in my own
application -- and I then tried to read a few other updates from
twitterapi. I get back a statuses list in home timeline, then I try to
read more information about the updates in question, and I always get
an error. I think twitter must also get an error, since those updates
seem to be unavailable there too. Here is what I see in my debug
output for one of these updates, any ideas?
{request:/1/statuses/show/20499308096.json,error:No status
found with that ID.}
I get the ID from the updates listed in a getstatusesHometimeline. I
would suspect my application, but it does this for everything else
fine, and only a subset of updates/statuses from twitterapi seem to be
failing, and twitter itself is failing to allow a favorite (for
instance) on these. Are these just 'lost' statuses/updates which I
should not worry about?
thanks,
Mark
Re: [twitter-dev] Re: Can we use localhost to tweet messages using oAuth authentication??
For clarity: There is nothing stopping you from using localhost as your oauth_callback during testing for OAuth 1.0a. While the form for your application on dev.twitter.com will not allow you to store a localhost domain as your pre-registered callback URL, our OAuth sub-system has no trouble using localhost for redirects when explicitly declared on the request token step. If you want to use localhost as your domain, just set the callback URL within your application record to something else. As a reminder, it's proper OAuth to always send an oauth_callback on the request token step of OAuth negotiation -- even if you've preregistered a callback or are using the PIN code/out-of-band flow (in which case you would send oauth_callback=oob). Taylor On Mon, Aug 9, 2010 at 5:53 AM, Lumpizaver demsarj...@gmail.com wrote: I also have a problem with this. I cannot use the twitter API login with OAuth when I am debugging on localhost. I tought that it is not possible to use Twitter authentication on localhost because of the callback url. So I tought that I have to upload my site somewhere before. Sincerely, Jure On 8 avg., 07:30, punit khaire punit.kha...@gmail.com wrote: Thanks Tom, I am using localhost to tweet messages but it is giving error message as Failed to authenticate with oauthe signature and token.Is this happening because I had given callback URL.I am generating proper signature and sending all parameters. I am not getting where I am going wrong . Punit. On Sun, Aug 8, 2010 at 5:13 AM, Tom allerleiga...@gmail.com wrote: Yes, you can. Any application that can sign oAuth requests can send tweets. Tom On Aug 7, 2:44 pm, Punit.khaire punit.kha...@gmail.com wrote: Can we use localhost to tweet messages using oAuth authentication??
Re: [twitter-dev] what's wrong with the search API?
Hi Bruce, I can't help you without a bit more information -- this looks like debug output but I need more identifying information about the specific query you were executing, the URL you were executing it against, and if possible, the actual JSON or XML response from the server. Also helpful: what programming language/libraries you are using to access. Thanks! Taylor On Sat, Aug 7, 2010 at 12:52 AM, bruce zhang brucezhan...@gmail.com wrote: Hi,guys before I can get the target tweets from search API.but now it returns results as follow: what's wrong with the search API? stdClass Object ( [statuses] = Array ( [0] = 41071345445 [1] = 41071345451 [2] = 41071345461 [3] = 41071345481 [4] = 41071345487 [5] = 41071345539 [6] = 41071345567 [7] = 41071345585 [8] = 41071345623 [9] = 41071345633 [10] = 41071345647 [11] = 41071345663 [12] = 41071345697 [13] = 41071345701 [14] = 41071345715 [15] = 41071345781 ) [created_in] = 0.009274 ) -- Best regards, Bruce E-Mail:brucezhan...@gmail.com e-mail%3abrucezhan...@gmail.com
Re: [twitter-dev] Using @anywhere session credentials for REST API
We'll have a solution for this announced soon that will allow you to move more seamlessly between the (non-OAuth 1.0a) access tokens that make up @Anywhere requests and server-side REST requests using OAuth 1.0a access tokens. There are also other things you can do with @Anywhere using advanced portions of the @Anywhere API -- including, for instance, retrieving a list of the user's follower IDs. You can read a bit about this here: http://groups.google.com/group/twitter-dev-anywhere/browse_thread/thread/a66128188a24acdd/ee8bc9e68b8d8efc?lnk=gstq=js+api#ee8bc9e68b8d8efc Taylor On Sat, Aug 7, 2010 at 12:25 AM, knc kishor...@gmail.com wrote: Hi, I am a little confused here. I am using @anywhere's (with the JS file include) to authenticate a user into my application. After this, let's say I would like to retrieve a list of the user's follower IDs - how do I do that? I'm guessing I need to use the REST API for this, but since the user is already authenticated, how will the new flow be? How do I get the Oauth token and secret to make the calls with?
Re: [twitter-dev] List names - allowed characters
At this time: - List names can have up to 20 characters. - Slugs are automatically created based off of list names - All slugs are downcased and stripped at time of creation, most non-alphanumeric characters will be converted to dashses. - When comparing existing list slugs for the current user, the list slug being created is also put through the same normalization routine - If the list slug would have nothing but non-ASCII characters (for instance, in Japanese), we simply use the phrase list followed by a dash and a number depending on how many lists of this type they had - If at any time the comparison of existing lists to the current candidate slug for creation match, the new list will be created with a dash and incremental number. So all those verbose bits to say: If the User has 1 list called Awesome! it would have a slug of awesome If the User then created a new list called Awesome!! it would have a slug of awesome-2 If the User then created a new list called 東京都民 it would have a slug of list If the User then created a new list called 東京都民!! it would have a slug of list-2 If the User then created a new list called AwesomE it would have a slug of awesome-3 Hope this helps. Taylor On Sat, Aug 7, 2010 at 3:39 AM, Ken k...@cimas.ch wrote: Can someone please confirm the allowed characters (and transforms) when creating new list names? We need to check whether a user already has a list with the proposed name. Unfortunately, the API doesn't return an error if the name already exists, instead naming the list, 'new-list-2', which our user must then delete.
Re: [twitter-dev] Re: The remote server returned an error: (401) Unauthorized
Hi Punit, First, some advice: I recommend using HTTP header-based OAuth rather than putting your OAuth parameters directly in the query string. It separates concerns and makes your debugging ultimately easier. That said, the first issue you're probably running into is that you aren't URL-encoding your OAuth Callback properly. In fact, when you're presenting any of these OAuth parameters, whether it was via HTTP header or query string, you need to do some more escaping. For our servers to properly interpret the URL you are sending, your request would need to look a bit more like (noting that the signature would be significantly different as a result): http://api.twitter.com/oauth/request_token?oauth_callback=http%3A%2F%2F203.78.217.115%2FIssueManager%2FLogin.aspoauth_consumer_key=ilmsYrfa0XjtsqJXCB6HcQoauth_nonce=821b87d0-2022-4f50-adcd-76ddae52c5dboauth_signature=Q01ZADdBJNh5dbltMMQXP37EkVg%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1281177991oauth_version=1.0 Are you using an OAuth library for this? Taylor On Sat, Aug 7, 2010 at 5:32 PM, execut...@gmail.com execut...@gmail.comwrote: the link below is broken,, On Sat, Aug 7, 2010 at 4:44 PM, Tom allerleiga...@gmail.com wrote: How are you generating the signature? Tom On Aug 7, 2:43 pm, Punit.khaire punit.kha...@gmail.com wrote: Hi guys, I started to work on the twitter application .Our main task is to tweet messages using oAuth authentication. I am sending below request using GET method, http://api.twitter.com/oauth/request_token?oauth_callback=http://203.. .. When I manually hit the above URl I get following error message, Failed to validate oauth signature and token I dont understand y I get this message,as I am sending everything in my parameter list. Am I missing something here,thanks in advance for any help. -- -- Michael J.D Saguri 1-250-999-0890 http://www.tweep.net Skype: marketingmaniac
Re: [twitter-dev] Re: BlackBerry, XAuth and twitterapime
Hi,
This issue of TwAPIme on BB will be investigated as soon as possible.
Unfortunately, I do not have a BB device to test on a real environment.
Nevertheless, I will perform some tests on BB emulator.
I will keep you guys posted on any news on this matter.
Regards,
Ernandes
On Mon, Aug 9, 2010 at 3:06 AM, Bess bess...@gmail.com wrote:
It seems like everyone like having trouble moving from basic to Oauth
in mobile.
TwitterAPIME works on BB via J2ME Twitter lib from Kenai. This library
also supports Android. But this lib author develop this lib in his
spare time so he didn't include every Twitter API. It can only do a
few things.
http://kenai.com/projects/twitterapime/pages/Home
Any BB developer can tell me which JS lib BB would support on their
Javascript API?
On Aug 7, 4:33 am, kmba...@gmail.com wrote:
Yes BlackBerry is Java ME, but it also has it's own API quirks and I was
unable to get one of the existing libraries to work for me.
I am doing the communication on my own. May app have been working fine
using BASIC. I have just had a hard time moving it over to OAuth based.
Sent via BlackBerry by ATT
-Original Message-
From: Bess bess...@gmail.com
Sender: twitter-development-talk@googlegroups.com
Date: Fri, 6 Aug 2010 22:06:12
To: Twitter Development Talktwitter-development-talk@googlegroups.com
Reply-To: twitter-development-talk@googlegroups.com
Subject: [twitter-dev] Re: BlackBerry, XAuth and twitterapime
If Twitter4J do not run on BB, which OAuth or xAuth lib do you use in
BB?
There is no other Java option in BB? You have to use J2ME in BB?
What about webos BB has announced?
Can I port my Java code from Android straight to BB? How much code re
factoring or rewrite I have to do to move from Android to BB?
On Aug 6, 10:23 am, Ernandes Jr. ernan...@gmail.com wrote:
BB is powered by Java ME and some specific RIM Java APIs.
On Fri, Aug 6, 2010 at 8:26 AM, David Francisco Tavárez
davidftava...@gmail.com wrote:
Twitter4J do not run on BB.
2010/8/6, Bess bess...@gmail.com:
I am able to use Twitter4J Oauth in Android SDK 2.1. Can you do the
same on BB?
Does BB has the same JAVA environment similar to Android? I assume
J2SE is very different than Android Java?
On Aug 5, 4:52 pm, BBTweet Media Player bbtweetme...@gmail.com
wrote:
Ernandes,
Thanks for the response. I am sure there is something small I am
doing wrong. I did grab twitter4j and made a simple j2se app to
make
sure I could use my consumer key and secret and XAuth worked. So
I
know my account is good at least. I am now trying to hand code
the
example onhttp://dev.twitter.com/pages/xauthtomakesure I can
properly encode a header. Everything worked fine using BASIC. I
do
not see why they had to make it so hard.
I am using the BB 5 and 6 OSs.
On Aug 5, 2:39 pm, Ernandes Jr. ernan...@gmail.com wrote:
I do not have a BB to test the API. However, I have received
some
e-mails
from people facing same problem as you. Some of them were making
some
small
mistakes and then it worked, however, others did not have much
success.
At
this moment, I am trying to find the route cause of many
problems with
BB. I
hope to find it soon and then release a fix for release 1.4.
By the way. which is your BB's OS version?
Regards,
Ernandes
On Thu, Aug 5, 2010 at 4:56 AM, Bess bess...@gmail.com wrote:
Which OAuth library did you use on your BB? Did you use the
Java
library?
On Aug 4, 7:42 am, Ernandes Jr. ernan...@gmail.com wrote:
Hi,
I suggest you to get in touch to Twitter API ME support
before
replacing
codes. Send an e-mail to supp...@twapime.com or check
project's
forum
page:http://kenai.com/projects/twitterapime/forums/forum
Maybe your issues are already discussed there.
Regards,
Ernandes
On Tue, Aug 3, 2010 at 9:21 PM, BBTweet Media Player
bbtweetme...@gmail.com
wrote:
I am having a very difficult time trying to get XAuth
working in
my
BlackBerry app. I have downloaded twitterapime the
hmacsha
ecodingand
Base64Ecoder did not seem to work for me so I replaced the
getSignature method in XAuthSigner with...
/**
* p
* Generate a signature from the given base string.
* /p
* @param baseString Base string.
* @param consumerSecret Consumer secret.
* @param tokenSecret Token secret.
* @return Signature.
*/
private static String getSignature(String
baseString,
String
consumerSecret,
String tokenSecret) {
[twitter-dev] Re: what's wrong with the search API?
I think that Bruce means that he only gets tweet IDs, and not the actual tweets. Make sure to use http://search.twitter.com/search.format and not any other endpoint (except for https://, of course). Tom On Aug 9, 3:45 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Bruce, I can't help you without a bit more information -- this looks like debug output but I need more identifying information about the specific query you were executing, the URL you were executing it against, and if possible, the actual JSON or XML response from the server. Also helpful: what programming language/libraries you are using to access. Thanks! Taylor On Sat, Aug 7, 2010 at 12:52 AM, bruce zhang brucezhan...@gmail.com wrote: Hi,guys before I can get the target tweets from search API.but now it returns results as follow: what's wrong with the search API? stdClass Object ( [statuses] = Array ( [0] = 41071345445 [1] = 41071345451 [2] = 41071345461 [3] = 41071345481 [4] = 41071345487 [5] = 41071345539 [6] = 41071345567 [7] = 41071345585 [8] = 41071345623 [9] = 41071345633 [10] = 41071345647 [11] = 41071345663 [12] = 41071345697 [13] = 41071345701 [14] = 41071345715 [15] = 41071345781 ) [created_in] = 0.009274 ) -- Best regards, Bruce E-Mail:brucezhan...@gmail.com e-mail%3abrucezhan...@gmail.com
[twitter-dev] Re: Can we use localhost to tweet messages using oAuth authentication??
If you are generating the right signature (which is quite a large assumption) and sending the right parameters, then make sure you aren't sending too much. Signature + parameters are, as far as I know, the only things that can cause a 401 error - assuming that the keys are right. Just make sure to do proper URLencoding on the callback. Tom On Aug 8, 7:30 am, punit khaire punit.kha...@gmail.com wrote: Thanks Tom, I am using localhost to tweet messages but it is giving error message as Failed to authenticate with oauthe signature and token.Is this happening because I had given callback URL.I am generating proper signature and sending all parameters. I am not getting where I am going wrong . Punit. On Sun, Aug 8, 2010 at 5:13 AM, Tom allerleiga...@gmail.com wrote: Yes, you can. Any application that can sign oAuth requests can send tweets. Tom On Aug 7, 2:44 pm, Punit.khaire punit.kha...@gmail.com wrote: Can we use localhost to tweet messages using oAuth authentication??
[twitter-dev] since - until
Hi, Is there a minimum date that can be used for since or until params in a Search API? It seems limited only to the current month? Thanks
[twitter-dev] Re: How is this a solution?
OAuth is a web authentication protocol. It was not designed to authenticate desktop and mobile apps, and should not be used for that. I have to disagree. I can't think of a single protocol that allows the identification of applications without the possibility of leaking keys - if you have to use a key, it can be stolen, and if you don't have to use a key, you can't identify (or anyone can). If you use some kind of server-side proxy, you still have the same issue, because you also have to identify your application to your own server - which anyone can do, no matter how good the encryption is. Tom On Aug 9, 4:50 am, Jef Poskanzer jef.poskan...@gmail.com wrote: On Aug 7, 10:52 am, @epc epcoste...@gmail.com wrote: What's the approved open source solution to this problem? You don't have to make it a full-fledged web app as Ed Borasky says. You can also use a server-side proxy that holds your API keysecret and signs API calls. Of course this means all of your application's traffic will funnel through your server instead of going direct to twitter, which is obviously not good. And I'll also repeat what Julio Biason said, that this is not actually an open source vs. closed source issue. Closed source desktop mobile applications also have their app keysecret built into the app. Anyone with a debugger can extract them. OAuth is a web authentication protocol. It was not designed to authenticate desktop and mobile apps, and should not be used for that.
Re: [twitter-dev] Can we automate the user login process on twitter...
Hi Punit, The OAuth sequence cannot be automated. For web-based applications, you will have to do the entire OAuth sequence, utilizing either a callback or the PIN-code/out-of-band flow. Desktop and native mobile applications that demonstrate a need and adhere to our policies can request permission for the xAuth variation of OAuth, where you need only exchange a login and password for an access token, by sending a detailed request to a...@twitter.com Taylor On Sun, Aug 8, 2010 at 8:02 AM, Punit.khaire punit.kha...@gmail.com wrote: Hi, I am develop[eing one web application to tweet posts on twitter, 1. Request token 2.Authorize user on twitter 3.Get access token from twitter 4.Post on tweitter. When I authorize user on twitter(2nd step) ,I am redirected to twitter.com to allow user to enter the Username and Password.Can we automate this process.Can I send username and password of user from my application?
[twitter-dev] Re: streaming API help (regular API works)
You can't re-use signatures. Signatures use a nonce which is unique, a timestamp that will invalidate the request after about 5 minutes, and a signature that is based on the request you do (including URL). Tom On Aug 9, 4:22 am, ianrose ianros...@gmail.com wrote: Hi - I hope I am not posting a question that has previously been answered - I tried searching the archives but to no avail. I am trying to get the 'sample' stream API working but am getting 401 Unathorized errors. For debugging purposes, I am using curl for now. The following command fails (401): curl 'http://stream.twitter.com/1/statuses/sample.json? delimited=length' -H 'Authorization: OAuth realm=Twitter API, oauth_nonce=24599946, oauth_timestamp=1281319798, oauth_consumer_key=, oauth_signature_method=HMAC-SHA1, oauth_version=1.0, oauth_token=175905996- JkrGAl8ZXCgIjeZl3o7fMCD8HbyfVeDbkP9Y13mX, oauth_signature=i %2BVzWX23sp5t8%2Fz0swJl%2FDHloOo%3D' However, I believe that my OAuth stuff is (hopefully) correct because the following command works, where I have reused the exact same OAuth header (all I changed was the URL): curl 'http://api.twitter.com/1/statuses/user_timeline.json'-H 'Authorization: OAuth realm=Twitter API, oauth_nonce=24599946, oauth_timestamp=1281319798, oauth_consumer_key=, oauth_signature_method=HMAC-SHA1, oauth_version=1.0, oauth_token=175905996-JkrGAl8ZXCgIjeZl3o7fMCD8HbyfVeDbkP9Y13mX, oauth_signature=i%2BVzWX23sp5t8%2Fz0swJl%2FDHloOo%3D' So what does this mean? Are the authentication requirements at all different for these two API calls? In case its relevant, note that I am using my account's single access token to create these OAuth signatures as opposed to a real customer key/secret pair. Any suggestions on what else I can do to try and debug this? Many thanks! - Ian
Re: [twitter-dev] Re: Can we use localhost to tweet messages using oAuth authentication??
On Aug 9, 2010, at 08:37 , Taylor Singletary wrote: As a reminder, it's proper OAuth to always send an oauth_callback on the request token step of OAuth negotiation -- even if you've preregistered a callback or are using the PIN code/out-of-band flow (in which case you would send oauth_callback=oob). Taylor, As a user of xauth, I do not currently send oauth_callback=oob. I think this is because xauth does not participate in the negotiation for a temporary credential. (See: http://tools.ietf.org/html/rfc5849 section 2.1.). Is this your understanding? Or do xauth users need to include this callback in our request for our permanent access token? Anon, Andrew Andrew W. Donoho Donoho Design Group, L.L.C. a...@ddg.com, +1 (512) 750-7596 We did not come to fear the future. We came here to shape it. -- President Barack Obama, Sept. 2009
[twitter-dev] Re: Best method of displaying a list of friends
I don't think that there is an API which allows you to do this. Caching is important here. What you can do, for example, is simply get the home timeline (which also contains user objects) and store these users in your cache - possibly a few (max. 32) pages. Tom On Aug 9, 1:03 am, Alex Chang changcommaa...@gmail.com wrote: What's the best method for display a list of friends to a twitter user? In most other oauth / social network apis - they usually return an id as well as a name. What's the best way to go about showing a list of friends without getting killed by the api limit? Right now I'm using /friends/ids.json. Then looping on it for /users/ show.json in order to get the screennames. This will kill the api limit. Any suggestions?
Re: [twitter-dev] Re: Can we use localhost to tweet messages using oAuth authentication??
xAuth would not require this as no callback is utilized. In the case of actually executing API resource actions (like sending a tweet), your callback (and effectively OAuth itself) has nothing to do with the request -- it's only a means of identifying the two parties involved in the request (the user and the application). On Mon, Aug 9, 2010 at 7:51 AM, Andrew W. Donoho andrew.don...@gmail.comwrote: On Aug 9, 2010, at 08:37 , Taylor Singletary wrote: As a reminder, it's proper OAuth to always send an oauth_callback on the request token step of OAuth negotiation -- even if you've preregistered a callback or are using the PIN code/out-of-band flow (in which case you would send oauth_callback=oob). Taylor, As a user of xauth, I do not currently send oauth_callback=oob. I think this is because xauth does not participate in the negotiation for a temporary credential. (See: http://tools.ietf.org/html/rfc5849 section 2.1.). Is this your understanding? Or do xauth users need to include this callback in our request for our permanent access token? Anon, Andrew Andrew W. Donoho Donoho Design Group, L.L.C. a...@ddg.com, +1 (512) 750-7596 We did not come to fear the future. We came here to shape it. -- President Barack Obama, Sept. 2009
[twitter-dev] Re: what's wrong with the search API?
I had this same problem, and I discovered I was using api.twitter.com/ 1/search instead of search.twitter.com/search. So yeah, switching the endpoint fixed it. Good luck, Ryan On Aug 7, 3:52 am, bruce zhang brucezhan...@gmail.com wrote: Hi,guys before I can get the target tweets from search API.but now it returns results as follow: what's wrong with the search API? stdClass Object ( [statuses] = Array ( [0] = 41071345445 [1] = 41071345451 [2] = 41071345461 [3] = 41071345481 [4] = 41071345487 [5] = 41071345539 [6] = 41071345567 [7] = 41071345585 [8] = 41071345623 [9] = 41071345633 [10] = 41071345647 [11] = 41071345663 [12] = 41071345697 [13] = 41071345701 [14] = 41071345715 [15] = 41071345781 ) [created_in] = 0.009274 ) -- Best regards, Bruce E-Mail:brucezhan...@gmail.com e-mail%3abrucezhan...@gmail.com
Re: [twitter-dev] Re: Best method of displaying a list of friends
The friends/ids method has a friend of its own: users/lookup -- which allows you to bulk your users/show calls by about 100 users at a time. So you would perform the sequence of using friends/ids and then for each set of 100 ids you get back, you'd send them to users/lookup to get the detailed information back. http://dev.twitter.com/doc/get/users/lookup Taylor On Mon, Aug 9, 2010 at 7:53 AM, Tom allerleiga...@gmail.com wrote: I don't think that there is an API which allows you to do this. Caching is important here. What you can do, for example, is simply get the home timeline (which also contains user objects) and store these users in your cache - possibly a few (max. 32) pages. Tom On Aug 9, 1:03 am, Alex Chang changcommaa...@gmail.com wrote: What's the best method for display a list of friends to a twitter user? In most other oauth / social network apis - they usually return an id as well as a name. What's the best way to go about showing a list of friends without getting killed by the api limit? Right now I'm using /friends/ids.json. Then looping on it for /users/ show.json in order to get the screennames. This will kill the api limit. Any suggestions?
Re: [twitter-dev] Uploading a Profile Image help
Also a reminder: the Twitter API is at the http://api.twitter.com subdomain. Twitter API has version numbers in the URL as well. The original poster in this thread is using http://twitter.com/account/update_profile_image.xml when they should be using http://api.twitter.com/1/account/update_profile_image.xml And I'll echo what Tom has said: you should switch to using OAuth very soon or you'll find your script doesn't work at all in about 2 weeks. Taylor On Sun, Aug 8, 2010 at 10:28 PM, Raghu Prasad prasad.ragh...@gmail.comwrote: On Sun, Aug 8, 2010 at 5:58 AM, marketingmaniac execut...@gmail.com wrote: i use to have this app that suddenly doesn't work anymore,, it use to work perfectly and now ,, hmm,, any help would be appreciated,, Though I don't know a bit about VB, I can safely say that profile image functionality of Twitter has been broken for many weeks. Updating profile image has not been working via API. If you check the past threads, you'd find that one of the Twitter developer is assigned the task of streamlining the image upload functionality. I am also waiting for that to happen. Raghu here is the code that update my users profile written in vb 2008/10 that worked flawlessly 'THE BUTTON I MADE TO INITIATE THE SUB CALLED UPLOADPROFILEIMAGE Private Sub Button37_Click_1(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button37.Click
[twitter-dev] archive search
Hi, Is it possible to search for older tweets, since search api seems to return only tweets from last week?
Re: [twitter-dev] archive search
Hi Ilija, You're right, the Search API and search.twitter.com does not go very far back in time. Twitter does not offer an API that can retrieve or search against historical tweets at this time. Taylor On Mon, Aug 9, 2010 at 8:06 AM, Ilija subasic.il...@gmail.com wrote: Hi, Is it possible to search for older tweets, since search api seems to return only tweets from last week?
[twitter-dev] Re: Uploading a Profile Image help
I too am waiting for the profile image API call to be fixed. I have checked the request and even dove into HTTP_Request2's internal code just to verify that the request is correct. The only error I get back is 500 Internal Server Error. No other hints or suggestions are present in the response header. The images I am using are small and well within the limits. Any update on when this may be working again? Thanks, Ryan On Aug 9, 11:07 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Also a reminder: the Twitter API is at thehttp://api.twitter.comsubdomain. Twitter API has version numbers in the URL as well. The original poster in this thread is usinghttp://twitter.com/account/update_profile_image.xmlwhen they should be usinghttp://api.twitter.com/1/account/update_profile_image.xml And I'll echo what Tom has said: you should switch to using OAuth very soon or you'll find your script doesn't work at all in about 2 weeks. Taylor On Sun, Aug 8, 2010 at 10:28 PM, Raghu Prasad prasad.ragh...@gmail.comwrote: On Sun, Aug 8, 2010 at 5:58 AM, marketingmaniac execut...@gmail.com wrote: i use to have this app that suddenly doesn't work anymore,, it use to work perfectly and now ,, hmm,, any help would be appreciated,, Though I don't know a bit about VB, I can safely say that profile image functionality of Twitter has been broken for many weeks. Updating profile image has not been working via API. If you check the past threads, you'd find that one of the Twitter developer is assigned the task of streamlining the image upload functionality. I am also waiting for that to happen. Raghu here is the code that update my users profile written in vb 2008/10 that worked flawlessly 'THE BUTTON I MADE TO INITIATE THE SUB CALLED UPLOADPROFILEIMAGE Private Sub Button37_Click_1(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button37.Click
[twitter-dev] Re: Get resolved URLs?
Gnip's beta testing URL unwinding in all of its streams. All short URLs that move through Gnip get unwound (one level), in real-time, when we transform to Activity Streams. We're representing the unwinding as follows (as an example). If you're interested in trying this out, you can sign up for a trial at http://try.gnip.com . We have to manually toggle the feature on for you (as it's in beta), so be sure to email us (i...@gnip.com) w/ said request after signing up for the trial. gnip:urls gnip:url gnip:short_urlhttp://bit.ly/aC7YVr/gnip:short_url gnip:long_urlhttp://www.twitlonger.com/show/ 1e65c74b49302a0afd8580561e63456a/gnip:long_url /gnip:url /gnip:urls On Aug 6, 10:35 am, Brian Medendorp brian.medend...@gmail.com wrote: I can see that twitter itself must be resolving any shortenedURLs somewhere, because if you search for a domain name (such as amazon.com), you get a bunch of results that don't seem to match until you resolve the shortened URL in the tweet and see that it points to the domain you searched for, which is fantastic! However, I am wondering if there is any way to get thoseresolvedURLs from the API, or (better yet) if there is anyway that thoseURLscould be exposed in the search results themselves. Currently, I am resolving theURLsmyself by requesting the URL and saving the resulting location, but that starts to take a while when there are a lot of results returned.
[twitter-dev] Re: How is this a solution?
On Aug 9, 7:44 am, Tom allerleiga...@gmail.com wrote: If you use some kind of server-side proxy, you still have the same issue, because you also have to identify your application to your own server - which anyone can do, no matter how good the encryption is. Yes, anyone who uses your application gets identified as using your application. This is not a problem.
[twitter-dev] Re: Coming soon: a solution for Open Source applications using OAuth with the Twitter API
Has this solution for Open Source applications using OAuth with the Twitter API been implemented yet? As the deadline for Basic authentication removal is looming very close; 16th August, end of this week.
Re: [twitter-dev] Re: Coming soon: a solution for Open Source applications using OAuth with the Twitter API
On Mon, Aug 9, 2010 at 1:50 PM, Meepnix moonix...@gmail.com wrote: Has this solution for Open Source applications using OAuth with the Twitter API been implemented yet? As the deadline for Basic authentication removal is looming very close; 16th August, end of this week. On another thread, Taylor said No. So, basically, you will have to let your secret leak so your users can use your app. -- Julio Biason julio.bia...@gmail.com Twitter: http://twitter.com/juliobiason
[twitter-dev] Re: How is this a solution?
And anyone who manages to find out how your client-server connection works, can act as if they are using your application - exactly the same issue as the one which Twitter currently has, except that it may be a bit easier or harder, depending on the used protocol. Tom On Aug 9, 6:50 pm, Jef Poskanzer jef.poskan...@gmail.com wrote: On Aug 9, 7:44 am, Tom allerleiga...@gmail.com wrote: If you use some kind of server-side proxy, you still have the same issue, because you also have to identify your application to your own server - which anyone can do, no matter how good the encryption is. Yes, anyone who uses your application gets identified as using your application. This is not a problem.
[twitter-dev] Re: Best method of displaying a list of friends
I just ran into this one in an old application of mine (List 'em All, http://quonos.nl/list-em-all/): https://api.twitter.com/statuses/friends.json Seems to show 100 users as well, without having to send IDs (which saves another API call). However, I'm only mentioning it to correct my last post - it's a non-documented API endpoint and as far as I know, they should not be used. Tom On Aug 9, 4:58 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: The friends/ids method has a friend of its own: users/lookup -- which allows you to bulk your users/show calls by about 100 users at a time. So you would perform the sequence of using friends/ids and then for each set of 100 ids you get back, you'd send them to users/lookup to get the detailed information back. http://dev.twitter.com/doc/get/users/lookup Taylor On Mon, Aug 9, 2010 at 7:53 AM, Tom allerleiga...@gmail.com wrote: I don't think that there is an API which allows you to do this. Caching is important here. What you can do, for example, is simply get the home timeline (which also contains user objects) and store these users in your cache - possibly a few (max. 32) pages. Tom On Aug 9, 1:03 am, Alex Chang changcommaa...@gmail.com wrote: What's the best method for display a list of friends to a twitter user? In most other oauth / social network apis - they usually return an id as well as a name. What's the best way to go about showing a list of friends without getting killed by the api limit? Right now I'm using /friends/ids.json. Then looping on it for /users/ show.json in order to get the screennames. This will kill the api limit. Any suggestions?
[twitter-dev] Re: Some twitterapi updates unavailable
Taylor,
I found one other in my debug logs: 20486403894, also from twitterapi.
None others yet. Hope this helps you.
Mark
On Aug 9, 9:29 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Mark,
We're looking into this and are not quite sure what's going on with these
particular statuses. If you come across any other status ids that can't be
fetched via statuses/show, cannot be favorited, or retweeted (all three
actions fail with these particular tweets), please let us know the status id
so we're aware.
Thanks,
Taylor
On Mon, Aug 9, 2010 at 3:48 AM, Mark Krieger markskrie...@gmail.com wrote:
I tried to 'favorite' an update by twitterapi over the weekend in
twitter, nothing happened, so I tried to read that update in my own
application -- and I then tried to read a few other updates from
twitterapi. I get back a statuses list in home timeline, then I try to
read more information about the updates in question, and I always get
an error. I think twitter must also get an error, since those updates
seem to be unavailable there too. Here is what I see in my debug
output for one of these updates, any ideas?
{request:/1/statuses/show/20499308096.json,error:No status
found with that ID.}
I get the ID from the updates listed in a getstatusesHometimeline. I
would suspect my application, but it does this for everything else
fine, and only a subset of updates/statuses from twitterapi seem to be
failing, and twitter itself is failing to allow a favorite (for
instance) on these. Are these just 'lost' statuses/updates which I
should not worry about?
thanks,
Mark
[twitter-dev] Promoted Content: API Changes
Hey Developers, As you might know, this year Twitter launched a suite of Twitter Promoted Products, including Promoted Tweets (http://blog.twitter.com/ 2010/04/hello-world.html) and Promoted Trends, which advertisers can use to deepen their engagement with Twitter users. To date, these products have been shown to users on Twitter.com. Over time, we plan to extend the products to ecosystem partners. Today, we made an update to one of our APIs that gets us closer to that objective. Clients using the API will see new fields related to promoted content in the response they get back from the /1/trends/current.json request and any local trends requests. These two new data points will show in the json response as events and promoted_content. We are still building the data points out and have more updates to make. Whilst that is happening, the two data points won't be able to return any useful content, and instead will have a value of 'null'. Over the next few months, we will begin beta testing with a handful of desktop applications. During this period, we aim to learn a lot, and we will apply those lessons when we expand distribution of Twitter Promoted Products to the broader ecosystem. We'll continue to keep you posted on other developments and changes as they happen. Best, Matt -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris
Re: [twitter-dev] Re: Best method of displaying a list of friends
Hey,
So /statuses/friends.json is documented here:
http://dev.twitter.com/doc/get/statuses/friends
but as Taylor said we recommend you use /friends/ids.{format} in combination
with /users/lookup.{format}.
Matt
On Mon, Aug 9, 2010 at 10:52 AM, Tom allerleiga...@gmail.com wrote:
I just ran into this one in an old application of mine (List 'em All,
http://quonos.nl/list-em-all/):
https://api.twitter.com/statuses/friends.json
Seems to show 100 users as well, without having to send IDs (which
saves another API call). However, I'm only mentioning it to correct my
last post - it's a non-documented API endpoint and as far as I know,
they should not be used.
Tom
On Aug 9, 4:58 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
The friends/ids method has a friend of its own: users/lookup -- which
allows
you to bulk your users/show calls by about 100 users at a time.
So you would perform the sequence of using friends/ids and then for each
set
of 100 ids you get back, you'd send them to users/lookup to get the
detailed
information back.
http://dev.twitter.com/doc/get/users/lookup
Taylor
On Mon, Aug 9, 2010 at 7:53 AM, Tom allerleiga...@gmail.com wrote:
I don't think that there is an API which allows you to do this.
Caching is important here. What you can do, for example, is simply get
the home timeline (which also contains user objects) and store these
users in your cache - possibly a few (max. 32) pages.
Tom
On Aug 9, 1:03 am, Alex Chang changcommaa...@gmail.com wrote:
What's the best method for display a list of friends to a twitter
user? In most other oauth / social network apis - they usually return
an id as well as a name.
What's the best way to go about showing a list of friends without
getting killed by the api limit?
Right now I'm using /friends/ids.json. Then looping on it for /users/
show.json in order to get the screennames. This will kill the api
limit.
Any suggestions?
--
Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris
Re: [twitter-dev] Promoted Content: API Changes
Hi Matt and other developers, If I understand correctly, Promoted Trends are advertisements, and they aren't necessarily trending topics. Basically what Twitter is trying to do here is let the desktop clients show Twitter's advertisements as well? Is there any benefit to the developers and/or the users for doing this? Correct me if I am completely wrong (wouldn't be the first time today) but Twitter is offering it's own advertisements to developers - I don't see why any developer would implement that. Tom On 8/9/10 9:36 PM, themattharris wrote: Hey Developers, As you might know, this year Twitter launched a suite of Twitter Promoted Products, including Promoted Tweets (http://blog.twitter.com/ 2010/04/hello-world.html) and Promoted Trends, which advertisers can use to deepen their engagement with Twitter users. To date, these products have been shown to users on Twitter.com. Over time, we plan to extend the products to ecosystem partners. Today, we made an update to one of our APIs that gets us closer to that objective. Clients using the API will see new fields related to promoted content in the response they get back from the /1/trends/current.json request and any local trends requests. These two new data points will show in the json response as events and promoted_content. We are still building the data points out and have more updates to make. Whilst that is happening, the two data points won't be able to return any useful content, and instead will have a value of 'null'. Over the next few months, we will begin beta testing with a handful of desktop applications. During this period, we aim to learn a lot, and we will apply those lessons when we expand distribution of Twitter Promoted Products to the broader ecosystem. We'll continue to keep you posted on other developments and changes as they happen. Best, Matt -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris
[twitter-dev] Re: Can we automate the user login process on twitter...
Punit, If you have regular users with accounts on your site, they only need to go through Oauth once - assuming you have a more convenient login process to offer them. The first time they authorize through Twitter, you need to capture the token and store it. Then they can log in using your less cumbersome process and, until such time as they deny access to your app - invalidating the token you have stored - they can use your app to interact with Twitter. Maybe that's what you had in mind? On Aug 8, 5:02 pm, Punit.khaire punit.kha...@gmail.com wrote: Hi, I am develop[eing one web application to tweet posts on twitter, 1. Request token 2.Authorize user on twitter 3.Get access token from twitter 4.Post on tweitter. When I authorize user on twitter(2nd step) ,I am redirected to twitter.com to allow user to enter the Username and Password.Can we automate this process.Can I send username and password of user from my application?
[twitter-dev] Re: OAuth page showing opening and ending tag mismatch
Good news: the user who originally said he was seeing the error under an english locale actually wasn't, and the error goes away when he sets his phone to English. Bad news: he's still seeing the error. I haven't been able to actually get the error text or a screenshot out of him yet, will carry on trying... On Aug 3, 8:19 am, Jonathan del Strother jdelstrot...@gmail.com wrote: Thanks for the update - I'll let our users know and get back to you if there's any further problems. On Aug 3, 7:05 am, Matt Harris thematthar...@twitter.com wrote: We found some escape markers in the language file used on the pages shown to be having issues and fixed them. Hopefully that's worked out the issues users were having. Mobile is very hard to debug and test as there are so many different handsets so if anybody does have issues again please take a screenshot and let us know. That will help us track down the source of the error. Thanks, Matt On Mon, Aug 2, 2010 at 3:23 PM, Jonathan del Strother jdelstrot...@gmail.com wrote: I'd assume the language depends on the http Accept-Language header, but just changing that doesn't seem sufficient to trigger the bug. On Jul 27, 3:21 am, Bess bess...@gmail.com wrote: I don't see that error on mobile Twitter page but I am testing it in US. Do you think it is related to callingURL IP Address? Would Twitter process it differently for non-US IP Address on callingURL? On Jul 26, 2:10 pm, Jonathan del Strother jdelstrot...@gmail.com wrote: Hi - thanks for the response. Both the users who have come to us with this problem are non-english speakers - one was definitely viewing it in French, the other claimed to be using English but I kinda suspect a communication problem there... I've not been able to reproduce it, even when setting my phone to different locales - do you have a guaranteed way of reproducing it yet? Any idea what percentage of users see the problem? I've been wondering about sticking a ?lang=en parameter in there till it gets fixed. -Jonathan On Jul 26, 6:49 pm, Matt Harris thematthar...@twitter.com wrote: Hi Jonathan, Our mobile team is aware of this issue and is looking into it. From my tests it looks like it only happens for users whose language is not English. Do you know if these users are viewing the site in anything other than English? Thanks Matt On Mon, Jul 26, 2010 at 12:06 AM, Jonathan del Strother jdelstrot...@gmail.com wrote: Any further progress on this? Is there anything I can get my users to try, to try diagnose the problem some more? -Jonathan On Jul 22, 3:10 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Jonathan, One conjecture I can think of based on the screenshot is that this may be due to the broken image upload issues we were having recently -- but the further reports on the original link you provided suggest otherwise. Looking into this. Taylor On Thu, Jul 22, 2010 at 3:11 AM, Jonathan del Strother jdelstrot...@gmail.com wrote: No takers? On Jul 15, 1:10 pm, Jonathan del Strother jdelstrot...@gmail.com wrote: Hi, We use Twitter Oauth for third party signin. I haven't been able to reproduce this myself, but one of our users is seeing an error page showing this page contains the following errors: error on line 397 column 156: opening and ending tag mismatch:divline 0 andstrong. Someone at Boxcar seems to be having similar problems - http://help.boxcar.io/discussions/problems/455-i-cant-sign-in-in-twitter Anyone else run into this? Any suggestions on fixing it? -Jonathan -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris
[twitter-dev] Re: Promoted Content: API Changes
I Agree with Tom. Please explain more on how this will benefit end- users and developers and not simply be a revenue stream for you. Thanks. On Aug 9, 8:50 pm, Tom van der Woerdt i...@tvdw.eu wrote: Hi Matt and other developers, If I understand correctly, Promoted Trends are advertisements, and they aren't necessarily trending topics. Basically what Twitter is trying to do here is let the desktop clients show Twitter's advertisements as well? Is there any benefit to the developers and/or the users for doing this? Correct me if I am completely wrong (wouldn't be the first time today) but Twitter is offering it's own advertisements to developers - I don't see why any developer would implement that. Tom On 8/9/10 9:36 PM, themattharris wrote: Hey Developers, As you might know, this year Twitter launched a suite of Twitter Promoted Products, including Promoted Tweets (http://blog.twitter.com/ 2010/04/hello-world.html) and Promoted Trends, which advertisers can use to deepen their engagement with Twitter users. To date, these products have been shown to users on Twitter.com. Over time, we plan to extend the products to ecosystem partners. Today, we made an update to one of our APIs that gets us closer to that objective. Clients using the API will see new fields related to promoted content in the response they get back from the /1/trends/current.json request and any local trends requests. These two new data points will show in the json response as events and promoted_content. We are still building the data points out and have more updates to make. Whilst that is happening, the two data points won't be able to return any useful content, and instead will have a value of 'null'. Over the next few months, we will begin beta testing with a handful of desktop applications. During this period, we aim to learn a lot, and we will apply those lessons when we expand distribution of Twitter Promoted Products to the broader ecosystem. We'll continue to keep you posted on other developments and changes as they happen. Best, Matt -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris
[twitter-dev] A total novice to both Twitter web development
Folks, as a total novice to Twitter web development altogether, I am relying on you goodwill and help: - I want to use HTTP only to post new (only) tweets from my personal webpage. After I have spent a fortune of time reading thru Twitter API and Wiki, I couldn't come to any conlcusion if this is all possible. So, may any one help me anwering the following: - is it possible to use only HTTP POST to send a new tweet to my twitter account? And, - how should such HTTP POST request look? Thanks in advance, Sashkoff :-)
[twitter-dev] Following protected users issue
I've been noticing something different in Twitter's behavior recently when following protected users. If I send a friendship request via API, it returns the user profile like it was successful. But the outgoing ids don't update nor am I now following the person. I also don't see the old error that you already requested to follow this person anymore. I'm also seeing this behavior via web. Clicking send request does nothing and doesn't show that I sent a request to follow when it finishes or I refresh. Is there something obvious I'm missing here or is this just an intermittent problem?
[twitter-dev] Re: Promoted Content: API Changes
Thanks for the replies, it’s really helpful to know what your thoughts and questions about the promoted products are. I’ve caught up with the team who are working on this and discussed your questions with them. Here's what I find out. We began testing Promoted Trends in June as an extension of our Promoted Tweets which were launched in April. So we all have the same understanding of what these products are i’ll explain them here. A Promoted Trend is one a topic which is already trending on Twitter but not popular enough to make it onto the Trending Topics list. A topic which isn’t popular on Twitter already cannot become a Promoted Trend. A Promoted Tweet is a Tweet which businesses and organisations want to highlight to a wide range of users. They have the same functionality as a regular Tweet except a Promoted Tweet will be highlighted at the top of some of our search results pages. Until today the Promoted Tweets and Trends were only shown to visitors on twitter.com. The API additions today take us closer to syndicating both those products to third parties. How this works out and ends up with everybody is one of the reasons we started the beta test with a handful of partners. As developers the benefit to you of displaying the Promoted Products is that Twitter will share revenue with you. We’re still working out the exact value and will keep you informed on developments. For users the benefit is that they will see time, context and event sensitive trends promoted by advertising partners. Only Tweets which users engage with will be kept. This means if users don’t interact with a Promoted Tweet it will disappear. Some more information is on our support site: http://support.twitter.com/articles/142161-advertisers http://support.twitter.com/groups/35-business/topics/127-frequently-asked-questions/articles/142101-promoted-tweets Best, Matt On Aug 9, 1:12 pm, scotth_uk satsc...@gmail.com wrote: I Agree with Tom. Please explain more on how this will benefit end- users and developers and not simply be a revenue stream for you. Thanks. On Aug 9, 8:50 pm, Tom van der Woerdt i...@tvdw.eu wrote: Hi Matt and other developers, If I understand correctly, Promoted Trends are advertisements, and they aren't necessarily trending topics. Basically what Twitter is trying to do here is let the desktop clients show Twitter's advertisements as well? Is there any benefit to the developers and/or the users for doing this? Correct me if I am completely wrong (wouldn't be the first time today) but Twitter is offering it's own advertisements to developers - I don't see why any developer would implement that. Tom On 8/9/10 9:36 PM, themattharris wrote: Hey Developers, As you might know, this year Twitter launched a suite of Twitter Promoted Products, including Promoted Tweets (http://blog.twitter.com/ 2010/04/hello-world.html) and Promoted Trends, which advertisers can use to deepen their engagement with Twitter users. To date, these products have been shown to users on Twitter.com. Over time, we plan to extend the products to ecosystem partners. Today, we made an update to one of our APIs that gets us closer to that objective. Clients using the API will see new fields related to promoted content in the response they get back from the /1/trends/current.json request and any local trends requests. These two new data points will show in the json response as events and promoted_content. We are still building the data points out and have more updates to make. Whilst that is happening, the two data points won't be able to return any useful content, and instead will have a value of 'null'. Over the next few months, we will begin beta testing with a handful of desktop applications. During this period, we aim to learn a lot, and we will apply those lessons when we expand distribution of Twitter Promoted Products to the broader ecosystem. We'll continue to keep you posted on other developments and changes as they happen. Best, Matt -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris
Re: [twitter-dev] Re: Promoted Content: API Changes
Hi Matt, Thanks for your reply :-) I just discussed it with a few of my users (gotta love the community). Replies in the mail below. On 8/10/10 12:18 AM, themattharris wrote: Thanks for the replies, it’s really helpful to know what your thoughts and questions about the promoted products are. I’ve caught up with the team who are working on this and discussed your questions with them. Here's what I find out. We began testing Promoted Trends in June as an extension of our Promoted Tweets which were launched in April. So we all have the same understanding of what these products are i’ll explain them here. A Promoted Trend is one a topic which is already trending on Twitter but not popular enough to make it onto the Trending Topics list. A topic which isn’t popular on Twitter already cannot become a Promoted Trend. Effectively an advertisement. If I wanted to push my application (about 1 tweet per day), I could simply contact Twitter and make my application a Promoted Trend, right? To me (and my users) that is an advertisement. A Promoted Tweet is a Tweet which businesses and organisations want to highlight to a wide range of users. They have the same functionality as a regular Tweet except a Promoted Tweet will be highlighted at the top of some of our search results pages. Easily compared to a Google advertisement - which is also just a message on the bottom of a page, except that in the case of Twitter it looks like a real Tweet. Until today the Promoted Tweets and Trends were only shown to visitors on twitter.com. The API additions today take us closer to syndicating both those products to third parties. How this works out and ends up with everybody is one of the reasons we started the beta test with a handful of partners. As developers the benefit to you of displaying the Promoted Products is that Twitter will share revenue with you. We’re still working out the exact value and will keep you informed on developments. This will either make the people of TweetDeck etc *very* rich, or it won't get the smaller developers (like myself) a thing. ;-) For users the benefit is that they will see time, context and event sensitive trends promoted by advertising partners. Only Tweets which users engage with will be kept. This means if users don’t interact with a Promoted Tweet it will disappear. Tell me: what's the actual gain for the user? When I started displaying a Google Ad on my first website (years ago), some people stopped visiting the site. How is this kind of advertisement different? Some more information is on our support site: http://support.twitter.com/articles/142161-advertisers http://support.twitter.com/groups/35-business/topics/127-frequently-asked-questions/articles/142101-promoted-tweets Best, Matt Tom PS: This is what my community thinks - Please don't consider it pointless bashing ;-) On Aug 9, 1:12 pm, scotth_uk satsc...@gmail.com wrote: I Agree with Tom. Please explain more on how this will benefit end- users and developers and not simply be a revenue stream for you. Thanks. On Aug 9, 8:50 pm, Tom van der Woerdt i...@tvdw.eu wrote: Hi Matt and other developers, If I understand correctly, Promoted Trends are advertisements, and they aren't necessarily trending topics. Basically what Twitter is trying to do here is let the desktop clients show Twitter's advertisements as well? Is there any benefit to the developers and/or the users for doing this? Correct me if I am completely wrong (wouldn't be the first time today) but Twitter is offering it's own advertisements to developers - I don't see why any developer would implement that. Tom On 8/9/10 9:36 PM, themattharris wrote: Hey Developers, As you might know, this year Twitter launched a suite of Twitter Promoted Products, including Promoted Tweets (http://blog.twitter.com/ 2010/04/hello-world.html) and Promoted Trends, which advertisers can use to deepen their engagement with Twitter users. To date, these products have been shown to users on Twitter.com. Over time, we plan to extend the products to ecosystem partners. Today, we made an update to one of our APIs that gets us closer to that objective. Clients using the API will see new fields related to promoted content in the response they get back from the /1/trends/current.json request and any local trends requests. These two new data points will show in the json response as events and promoted_content. We are still building the data points out and have more updates to make. Whilst that is happening, the two data points won't be able to return any useful content, and instead will have a value of 'null'. Over the next few months, we will begin beta testing with a handful of desktop applications. During this period, we aim to learn a lot, and we will apply those lessons when we expand distribution of Twitter Promoted Products to the broader ecosystem. We'll continue to keep you posted on other
Re: [twitter-dev] Re: OAuth page showing opening and ending tag mismatch
Thanks for the update Jonathan, when you get a screen shot let us know and we'll check it out. Matt On Mon, Aug 9, 2010 at 1:11 PM, Jonathan del Strother jdelstrot...@gmail.com wrote: Good news: the user who originally said he was seeing the error under an english locale actually wasn't, and the error goes away when he sets his phone to English. Bad news: he's still seeing the error. I haven't been able to actually get the error text or a screenshot out of him yet, will carry on trying... On Aug 3, 8:19 am, Jonathan del Strother jdelstrot...@gmail.com wrote: Thanks for the update - I'll let our users know and get back to you if there's any further problems. On Aug 3, 7:05 am, Matt Harris thematthar...@twitter.com wrote: We found some escape markers in the language file used on the pages shown to be having issues and fixed them. Hopefully that's worked out the issues users were having. Mobile is very hard to debug and test as there are so many different handsets so if anybody does have issues again please take a screenshot and let us know. That will help us track down the source of the error. Thanks, Matt On Mon, Aug 2, 2010 at 3:23 PM, Jonathan del Strother jdelstrot...@gmail.com wrote: I'd assume the language depends on the http Accept-Language header, but just changing that doesn't seem sufficient to trigger the bug. On Jul 27, 3:21 am, Bess bess...@gmail.com wrote: I don't see that error on mobile Twitter page but I am testing it in US. Do you think it is related to callingURL IP Address? Would Twitter process it differently for non-US IP Address on callingURL? On Jul 26, 2:10 pm, Jonathan del Strother jdelstrot...@gmail.com wrote: Hi - thanks for the response. Both the users who have come to us with this problem are non-english speakers - one was definitely viewing it in French, the other claimed to be using English but I kinda suspect a communication problem there... I've not been able to reproduce it, even when setting my phone to different locales - do you have a guaranteed way of reproducing it yet? Any idea what percentage of users see the problem? I've been wondering about sticking a ?lang=en parameter in there till it gets fixed. -Jonathan On Jul 26, 6:49 pm, Matt Harris thematthar...@twitter.com wrote: Hi Jonathan, Our mobile team is aware of this issue and is looking into it. From my tests it looks like it only happens for users whose language is not English. Do you know if these users are viewing the site in anything other than English? Thanks Matt On Mon, Jul 26, 2010 at 12:06 AM, Jonathan del Strother jdelstrot...@gmail.com wrote: Any further progress on this? Is there anything I can get my users to try, to try diagnose the problem some more? -Jonathan On Jul 22, 3:10 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Jonathan, One conjecture I can think of based on the screenshot is that this may be due to the broken image upload issues we were having recently -- but the further reports on the original link you provided suggest otherwise. Looking into this. Taylor On Thu, Jul 22, 2010 at 3:11 AM, Jonathan del Strother jdelstrot...@gmail.com wrote: No takers? On Jul 15, 1:10 pm, Jonathan del Strother jdelstrot...@gmail.com wrote: Hi, We use Twitter Oauth for third party signin. I haven't been able to reproduce this myself, but one of our users is seeing an error page showing this page contains the following errors: error on line 397 column 156: opening and ending tag mismatch:divline 0 andstrong. Someone at Boxcar seems to be having similar problems - http://help.boxcar.io/discussions/problems/455-i-cant-sign-in-in-twitter Anyone else run into this? Any suggestions on fixing it? -Jonathan -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris
Re: [twitter-dev] Re: Promoted Content: API Changes
Quoting themattharris thematthar...@twitter.com: A Promoted Trend is one a topic which is already trending on Twitter but not popular enough to make it onto the Trending Topics list. A topic which isn’t popular on Twitter already cannot become a Promoted Trend. Let's say I've produced a movie - I am a Villager - Diary of a Werewolf. I've promoted that movie lots of places, and people are starting to talk about it on Twitter. How do I know when it makes it into the already trending on Twitter but not popular enough position? Does Twitter's sales team call me up and say, We've noticed that 'I am a Villager' is an emerging trend - would you like to buy 'Promoted Tweets' and 'Promoted Trends'? Or does the studio or an agency come to Twitter at the beginning of the campaign and say, We've got a really great movie coming out and want to buy exposure on Twitter. How do we do that? I would hope and pray that it's the latter! I would hope it's something like the Old Spice campaign that some of my friends here in Portland helped to build. There *have* to be planning, coordination, partnerships, tools, design, metrics, analytics, key performance indicators, etc. to make this stuff work. As developers the benefit to you of displaying the Promoted Products is that Twitter will share revenue with you. We’re still working out the exact value and will keep you informed on developments. Is there a penalty attached to *not* displaying them? Is there a penalty attached to ignoring the whole API? ;-) For users the benefit is that they will see time, context and event sensitive trends promoted by advertising partners. Only Tweets which users engage with will be kept. This means if users don’t interact with a Promoted Tweet it will disappear. Like all of the other Twitter services, there's what the web application reads and writes and what third-party tools read and write on behalf of users via the API. Is there going to be a distinction in the metrics for resonance of a Promoted Tweet between interactions coming from the web application and interactions coming from other sources? Will the analytics be available to the third-party developers, or do we need to build those into our applications? -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos
[twitter-dev] Twitter Autoit port to oAuth
My 3 Twitter functions use basic Auth and I want to port them to oAuth ASAP I want to use PIN access for my app I'm not very good at HTTP programming, so any help is appreciated = #include-once #include Base64.au3 Func _TwitterPost($sTweet, $sTwitId, $sTwitPw, ByRef $LimitExceeded) Local $oTweet = _CreateMSXMLObj() If $oTweet = 0 Then SetError(1, 1, 0) Local $sTwitUrl = http://twitter.com/statuses/update.xml; Local $sLogin = _Base64Encode($sTwitId : $sTwitPw) Local $sUpdate = status= _UrlEncode(StringLeft($sTweet, 140)) $oTweet.Open(POST, $sTwitUrl, False) $oTweet.setRequestHeader(Content-Type, application/x-www-form- urlencoded) $oTweet.setRequestHeader(Authorization, Basic $sLogin) $oTweet.send($sUpdate) If $oTweet.status 200 Then SetError(2, 2, 0) if $oTweet.status =401 then MsgBox(0,Username/password,Check your Username or Password for user:$sTwitId,5); if $oTweet.status =403 then $LimitExceeded=True; If StringInStr($oTweet, created_at) = 0 Then SetError(3, 3, 0) Return 1 EndFunc Func _TwitterFollow($FollowID, $sTwitId, $sTwitPw, ByRef $LimitExceeded) Local $oTweet = _CreateMSXMLObj() If $oTweet = 0 Then SetError(1, 1, 0) Local $sTwitUrl = StringFormat(http://api.twitter.com/1/ friendships/create/%s.xml, $FollowID); Local $sLogin = _Base64Encode($sTwitId : $sTwitPw) Local $sUpdate = ; $oTweet.Open(POST, $sTwitUrl, False) $oTweet.setRequestHeader(Content-Type, application/x-www-form- urlencoded) $oTweet.setRequestHeader(Authorization, Basic $sLogin) $oTweet.send($sUpdate) If $oTweet.status 200 Then SetError(2, 2, 0) if $oTweet.status =401 then MsgBox(0,Username/password,Check your Username or Password for user:$sTwitId,5); if $oTweet.status =403 then $LimitExceeded=True; If StringInStr($oTweet, created_at) = 0 Then SetError(3, 3, 0) Return 1 EndFunc Func _TwitterUnFollow($UnFollowID, $sTwitId, $sTwitPw, ByRef $LimitExceeded) Local $oTweet = _CreateMSXMLObj() If $oTweet = 0 Then SetError(1, 1, 0) Local $sTwitUrl = StringFormat(http://api.twitter.com/1/ friendships/destroy/%s.xml, $UnFollowID); Local $sLogin = _Base64Encode($sTwitId : $sTwitPw) Local $sUpdate = ; $oTweet.Open(POST, $sTwitUrl, False) $oTweet.setRequestHeader(Content-Type, application/x-www-form- urlencoded) $oTweet.setRequestHeader(Authorization, Basic $sLogin) $oTweet.send($sUpdate) If $oTweet.status 200 Then SetError(2, 2, 0) if $oTweet.status =401 then MsgBox(0,Username/password,Check your Username or Password for user:$sTwitId,5); if $oTweet.status =403 then $LimitExceeded=True; If StringInStr($oTweet, created_at) = 0 Then SetError(3, 3, 0) Return 1 EndFunc ; Ganked and modified from: http://www.autoitscript.com/forum/index.php?showtopic=77155 Func _CreateMSXMLObj() Local $xmlObj = ObjCreate(Msxml2.XMLHTTP.6.0) If IsObj($xmlObj) Then Return $xmlObj $xmlObj = ObjCreate(Msxml2.XMLHTTP.3.0) If IsObj($xmlObj) Then Return $xmlObj $xmlObj = ObjCreate(Msxml2.XMLHTTP) If IsObj($xmlObj) Then Return $xmlObj $xmlObj = ObjCreate(Microsoft.XMLHTTP) If IsObj($xmlObj) Then Return $xmlObj Return 0 EndFunc Func _UrlEncode($sData) $sData = StringReplace($sData, %, %25) $sData = StringReplace($sData, , %26) $sData = StringReplace($sData, , %3C) $sData = StringReplace($sData, , %3E) $sData = StringReplace($sData, ~, %7E) $sData = StringReplace($sData, , %20) $sData = StringReplace($sData, @CRLF, \r\n) Return $sData EndFunc Func _UrlDecode($sData) $sData = StringReplace($sData, %3C, ) $sData = StringReplace($sData, %3E, ) $sData = StringReplace($sData, %7E, ~) $sData = StringReplace($sData, %20, ) $sData = StringReplace($sData, %26, ) $sData = StringReplace($sData, %25, %) $sData = StringReplace($sData, br, @CRLF) Return $sData EndFunc Attached File(s) TwitterAPI.au3 (3.84K) Number of downloads: 3 This post has been edited by tobject: 25 July 2010 - 02:54 PM Report Back to top of the page up there ^ MultiQuote Reply Edit
[twitter-dev] Seesmic Desktop joins the Twitter User Streams preview period
Hi Developers, We're happy to announce that Seesmic's preview release featuring the Twitter User Streams API is now available for testing. While Seesmic Desktop will eventually introduce User Streams to all supported platforms, this testing period is for users of Microsoft Windows only and you can find out all about it on Seesmic's blog post here: http://blog.seesmic.com/2010/08/seesmic-desktop-2-beta-with-twitter-user-streams.html. Seesmic Desktop 2 Beta streams your timeline, mentions, and direct messages in real-time while introducing a new column to capture social events as they happen, like the favoriting or retweeting of your tweets. Learn more about developing with User Streams at http://bit.ly/user_streamsand download the new Seesmic Desktop 2 beta with User Streams at http://d.seesmic.com/sdp/install.html?config=main . Keep on streaming, Taylor Singletary Developer Advocate, Twitter Platform http://twitter.com/episod
Re: [twitter-dev] Re: How is this a solution?
Quoting Jef Poskanzer jef.poskan...@gmail.com: On Aug 9, 10:48 am, Tom allerleiga...@gmail.com wrote: exactly the same issue as the one which Twitter currently has No. A malfeasor who gets your app key can make any API call pretending to be you, from any IP address, logged in as any user. A malfeasor who goes through your app's signing proxy can only do the calls that your app is willing to sign, which you can restrict by IP address, userid, calls/second throttle, or any way you like. Yep - sooner or later you have to build *some* kind of server to protect your business, even if the majority of your functionality is mobile or desktop. Given that, why not simply build as much of the functionality into the server as possible and make a browser-based app right from the start? ;-) This is that cloud computing stuff that they talk about in those expensive trade shows, right? ;-) -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos
Re: [twitter-dev] Re: How is this a solution?
On Mon, Aug 9, 2010 at 10:46 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: why not simply build as much of the functionality into the server as possible and make a browser-based app right from the start? 'Cause that's not what I want. If I wanted a browser based app, I'd write on from start and not start it as a desktop app that can run on 4 different operating systems including one mobile[1]. If I wanted a web app, I'd have to chose a hosting/provider to hold all users accounts deal with all the logistics of giving users all the data they want. Instead, I decided to write a desktop app, where the users have their data whenever they want. But you guys are taking this out of context: OSS apps _need_ a way to expose their keys (as they are part of the application itself) without having to worry about someone getting those keys and ruining the app image by posting trash or using those same keys to get the same rights a user gave to the app. [1] And no, I didn't had to add any hacks or a stupid sequence of #defines. I get all that for free. -- Julio Biason julio.bia...@gmail.com Twitter: http://twitter.com/juliobiason
[twitter-dev] Re: Promoted Content: API Changes
Hey Matt, I want to make sure I understand the comment you made about We’re still working out the exact value and will keep you informed on developments. Is that in reference to the rev share for Promoted Tweets? Dick C was really clear that it was 50/50 split at Chirp (http:// techcrunch.com/2010/04/14/twitter-execs-address-the-big-question- monetization/). That hasn't changed, right? Thanks, -mike On Aug 9, 7:10 pm, M. Edward (Ed) Borasky zn...@borasky- research.net wrote: Quoting themattharris thematthar...@twitter.com: A Promoted Trend is one a topic which is already trending on Twitter but not popular enough to make it onto the Trending Topics list. A topic which isn’t popular on Twitter already cannot become a Promoted Trend. Let's say I've produced a movie - I am a Villager - Diary of a Werewolf. I've promoted that movie lots of places, and people are starting to talk about it on Twitter. How do I know when it makes it into the already trending on Twitter but not popular enough position? Does Twitter's sales team call me up and say, We've noticed that 'I am a Villager' is an emerging trend - would you like to buy 'Promoted Tweets' and 'Promoted Trends'? Or does the studio or an agency come to Twitter at the beginning of the campaign and say, We've got a really great movie coming out and want to buy exposure on Twitter. How do we do that? I would hope and pray that it's the latter! I would hope it's something like the Old Spice campaign that some of my friends here in Portland helped to build. There *have* to be planning, coordination, partnerships, tools, design, metrics, analytics, key performance indicators, etc. to make this stuff work. As developers the benefit to you of displaying the Promoted Products is that Twitter will share revenue with you. We’re still working out the exact value and will keep you informed on developments. Is there a penalty attached to *not* displaying them? Is there a penalty attached to ignoring the whole API? ;-) For users the benefit is that they will see time, context and event sensitive trends promoted by advertising partners. Only Tweets which users engage with will be kept. This means if users don’t interact with a Promoted Tweet it will disappear. Like all of the other Twitter services, there's what the web application reads and writes and what third-party tools read and write on behalf of users via the API. Is there going to be a distinction in the metrics for resonance of a Promoted Tweet between interactions coming from the web application and interactions coming from other sources? Will the analytics be available to the third-party developers, or do we need to build those into our applications? -- M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos
[twitter-dev] Twitter Integration
Hi, We are developing an Android native application which has a feature for user to tweet his message on Twitter. For accessing Twitter we are using twitter4j library which has xAuth support. We have registered our application on Twitter with application type as Client. As per standard OAuth procedure we are redirecting user on http://twitter.com/oauth/authorize for authorizing our application to access his/her Twitter account. It shows authorization screen where user needs to enter his/her credentials and can allow or deny access permission. But our requirement is to first asks user to login to Twitter and once user logged in directly take user to tweet post screen. Can we suppress user permission screen that asks to allow or deny accessing user's Twitter account?.
[twitter-dev] OAuth and a readonly app
Hi all, Let's say I'm writing a read only app - you come to my website enter someones twitter name, and I give you some statistics about them. I can get all the stats I need by making anon calls to the REST api from my webserver. The API docs say Anonymous calls are based on the IP of the host and are permitted 150 requests per hour, where as OAuth calls are permitted 350 requests per hour. If my app gets popular enough I'd like to make as many calls as I can. What is the protocol here? Should I create a twitter account just for my app, take this account through the OAuth process, and use this account's access token for all my requests? Thanks, Russ
