Re: [twitter-dev] Question about User Vs Site Streams, and Moving away from REST calls.

[Tom van der Woerdt]

Hi John,

This seems like a rather strange policy. Is the cost of having one User
Streams connection not far lower than having a connection to Site
Streams? That's what Justin asked, just one connection.

Tom


On 9/16/10 6:22 AM, John Kalucki wrote:
> Our intention is that User Streams and Site Streams will, shortly, offer
> the same data and filtering options at a similar, if not identical, QoS.
> I'm sure some subtleties will creep in over time, as they always do, but
> this parity is our goal.
> 
> The major difference is that User Streams, given its higher per-user
> cost, is limited only to user-based applications that connect directly
> to the Twitter API. In this use case, we have no alternative but to
> service a connection from each user device. Site Streams, on the other
> hand, allows services, such as your website, to open many User Streams
> multiplexed over a smaller number of connections. This reduces per-user
> cost, and makes large scale integrations tractable. Several pretty large
> services have integrated with Site Streams in just a few days, so this
> multiplexing is unlikely to be an undue additional burden over a User
> Streams integration, and might even save a lot of work over time.
> 
> If you attempt to use User Streams from a service, we can trivially
> detect this situation, and we'll classify your usage as against the TOS.
> To put our current thinking as bluntly as possible: we intend to enforce
> the distinction between User Streams and Site Streams via revocation of
> access.
> 
> -John Kalucki
> http://twitter.com/jkalucki
> Twitter, Inc.
> 
> 
> 
> On Wed, Sep 15, 2010 at 12:24 PM, Justin  > wrote:
> 
> I've successfully migrated one of my sites away from making search and
> mention rest calls, switched over to the streaming API and I'm loving
> it. I still need to move it to OAuth but now that I have that in test
> I'm reading up on the User and Site streams and I have a question.
> 
> It seems the User stream states that websites should not use it, and
> should use the Site stream instead, but I don't consume or care about
> my user's activity, my site is centered around the messages and
> interactions with the application user not the users themselves.
> 
> Right now I track and evaluate followers and other bits using the rest
> calls but from what I see I could eliminate those rest calls and be
> off them (possibly) all together if I could use the User stream to
> accept information about new and broken friendships, favorites, dms,
> etc.
> 
> Is it acceptable to use the User stream in that manor since I would
> only need it for the app user account not my site user's accounts? If
> so, I can just maintain the two streams (filtered streaming api and
> user stream) and eliminate or cut back my rest calls dramatically?
> Please let me know so I can plan accordingly.
> 
> --
> Twitter developer documentation and resources:
> http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk?hl=en
> 
> 
> -- 
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk?hl=en

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Twitter xauth login for posting and receiving Tweets

[Zahid Naqvi]

did you get the xAuth permissions from the twitter?


--

*Thanks & Regards*

*Zahid Naqvi | Senior Software Engineer*
--
*
G1-11, I.T.Park, M.I.A. (Extn.) Udaipur - 313003 Rajasthan India
(M) *+91-9799966000* | (R) *+91-141-2608333*
*zahidalina...@gmail.com | za...@arcgate.com





On Thu, Sep 16, 2010 at 1:02 AM, Ernandes Jr.  wrote:

> Your code looks OK! Either your problem is related to your keys our your
> environment. Have you tryied to run you code on a real device?
>
>
> On Wed, Sep 15, 2010 at 6:30 AM, vinod  wrote:
>
>> Hi,
>> Hi,
>>
>> I imported the libraries:
>>
>> xauth-encoders.jar
>> kxml2-min-2.3.0.jar,
>> mobile-ju-framework-1.0.jar
>> twitter_api_me-1.3.jar
>>
>>
>> After using Ernandes library i am receiving errors as below
>> I used single access token here
>> verification of credentials are successfull. but failed to Tweet and
>> received below errors
>>
>> In WTK 3.0
>> javax.microedition.io.ConnectionNotFoundException: ConnectionNotFound
>> error in socket::open : error = 10060
>>
>> In WTK 2.5.2
>> java.lang.SecurityException: Invalid / expired Token
>>
>> Source is as follows:
>>
>> Token token = new Token("token_access", "token_secret");
>> Credential c = new Credential("rahulka...@gmail.com",
>> "8oHIBK7T90Ye7GjIF6SToA",
>> "4Ebm4f7bie2AAYyN75DxwSUYeg8x0SBlL0IyKIXzaw", token);
>> UserAccountManager m = UserAccountManager.getInstance(c);
>> try {
>> if (m.verifyCredential()) {
>> System.out.println("Consumer or token keys are success");
>> Tweet t = new Tweet("Hi!!! This is my first tweet via Twitter API
>> ME.");
>> TweetER ter = TweetER.getInstance(m);
>> t = ter.post(t);
>>
>> } else {
>> System.out.println("Consumer or token keys are invalid!");
>> }
>> } catch (Exception ex) {
>> System.out.println("Exception here1="+ex);
>> }
>>
>> If i use normal credentials my application is not able to validate
>> credentials itself
>>
>> In WTK 3.0
>>
>> javax.microedition.io.ConnectionNotFoundException: ConnectionNotFound
>> error in socket::open : error = 10060
>>
>> In WTK 2.5.2
>>
>> Credentials unsucessfull
>>
>> Also when i am not able to import Equifax cert
>> Please help to authentication, post and receive tweets using my
>> application.
>>
>> Regards,
>> Basu
>>
>> --
>> Twitter developer documentation and resources: http://dev.twitter.com/doc
>> API updates via Twitter: http://twitter.com/twitterapi
>> Issues/Enhancements Tracker:
>> http://code.google.com/p/twitter-api/issues/list
>> Change your membership to this group:
>> http://groups.google.com/group/twitter-development-talk?hl=en
>>
>
>
>
> --
> Ernandes Jr.
> -
> "ALL programs are poems. However,
> NOT all programmers are poets."
>
>  --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk?hl=en
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] twitter api oauth c++ demo source code

[yuzhujiutian]

twitter api oauth c++ demo source code

1.2 OAuth Authentication Flow
Figure 1-1 OAUTH AUTHENTICATION FLOW v1.0a
(Please refer to the attached
"gridtwit_client_oauth_demo_src_0.1.0.tar.gz" file
"Demo_Description.doc")


1.3 Token parameter
The following token parameter description is based on the program
“gridtwit_client_oauth_demo\liboauth-0.8.9\tests\gridtwit” test
results obtained.

Code revision
liboauth-0.8.9, add File " liboauth-0.8.9\tests\gridtwit.c", and hand-
modify the file "liboauth-0.8.9\tests\Makefile.am, liboauth-0.8.9\tests
\Makefile.in"

Test environment
Red Hat Enterprise Linux Server release 5.3, and free web proxy.

Test method
run the program “gridtwit_client_oauth_demo\liboauth-0.8.9\tests
\gridtwit”. If there is no the program file "gridtwit_client_oauth_demo
\liboauth-0.8.9\tests\gridtwit", can run the program files
"gridtwit_client_oauth_demo\liboauth-0.8.9\compile", then run "make
check". If there are other questions, please contact the author.

Application info
Application Name: gridtwit
Application Website: http://twitter.com/gridtwit
Application Type: Client
Default Access type: Read & Write

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Question about User Vs Site Streams, and Moving away from REST calls.

[John Kalucki]

Our intention is that User Streams and Site Streams will, shortly, offer the
same data and filtering options at a similar, if not identical, QoS. I'm
sure some subtleties will creep in over time, as they always do, but this
parity is our goal.

The major difference is that User Streams, given its higher per-user cost,
is limited only to user-based applications that connect directly to the
Twitter API. In this use case, we have no alternative but to service a
connection from each user device. Site Streams, on the other hand, allows
services, such as your website, to open many User Streams multiplexed over a
smaller number of connections. This reduces per-user cost, and makes large
scale integrations tractable. Several pretty large services have integrated
with Site Streams in just a few days, so this multiplexing is unlikely to be
an undue additional burden over a User Streams integration, and might even
save a lot of work over time.

If you attempt to use User Streams from a service, we can trivially detect
this situation, and we'll classify your usage as against the TOS. To put our
current thinking as bluntly as possible: we intend to enforce the
distinction between User Streams and Site Streams via revocation of access.

-John Kalucki
http://twitter.com/jkalucki
Twitter, Inc.



On Wed, Sep 15, 2010 at 12:24 PM, Justin  wrote:

> I've successfully migrated one of my sites away from making search and
> mention rest calls, switched over to the streaming API and I'm loving
> it. I still need to move it to OAuth but now that I have that in test
> I'm reading up on the User and Site streams and I have a question.
>
> It seems the User stream states that websites should not use it, and
> should use the Site stream instead, but I don't consume or care about
> my user's activity, my site is centered around the messages and
> interactions with the application user not the users themselves.
>
> Right now I track and evaluate followers and other bits using the rest
> calls but from what I see I could eliminate those rest calls and be
> off them (possibly) all together if I could use the User stream to
> accept information about new and broken friendships, favorites, dms,
> etc.
>
> Is it acceptable to use the User stream in that manor since I would
> only need it for the app user account not my site user's accounts? If
> so, I can just maintain the two streams (filtered streaming api and
> user stream) and eliminate or cut back my rest calls dramatically?
> Please let me know so I can plan accordingly.
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk?hl=en
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: Tweet button fails to parse URL

[Matt Harris]

Hey John,

There have been a number of threads on this so I apologies that yours
was not updated. We are tracking the defect on our issue tracker:
http://code.google.com/p/twitter-api/issues/detail?id=1818
http://code.google.com/p/twitter-api/issues/detail?id=1885

When we have a fix deployed the tickets will updated.
Best
Matt

On Wed, Sep 15, 2010 at 3:57 PM, John  wrote:
> No reply to this for a while, so asking again. Matt, your first
> response sounded like an acknowledgment that this is a bug. Is that
> so, and if so, can we expect to see it fixed?
>
> Best,
> John
>
> On Sep 6, 2:35 am, ecf  wrote:
>> Same behavior withurlcontaining "+" characters!
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> http://groups.google.com/group/twitter-development-talk?hl=en
>



-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: Twitter Search/Stream API

[Matt Harris]

Streaming gives you true geo-tagged results in that only Tweets which
have been geo-tagged are matches. Search does that but will also, if
no geo-tagged information is available, attempt to match Tweets based
on the value of the free text location field of the users profile.

For many applications the assumption that the location is accurate is
not suitable. The example being this:

My profile location says San Francisco. I go on holiday to England but
don't update my profile. I also don't have data roaming on my phone so
instead Tweet from twitter.com using the hotel. Every tweet I make
isn't geo-coded. According to search all my Tweets are from San
Francisco despite them being from England.

So it really depends on you usage. Completeness and accuracy is
available on the Streaming API whilst the Search API will give you
relevant Tweets from 1 up to ~5 days old, which may not be a complete
representation or entirely accurate (with relation to geo).

In addition search is rate limited and has limitations on the
complexity of your search query.

Hope that helps,
Matt

On Wed, Sep 15, 2010 at 6:50 PM, @IDisposable  wrote:
>> Also, all automated repetitive searching should be on the Streaming API.
>> Search is intended largely for ad-hoc queries.
>
> If Stream honored the location search (where the tweep's profile's
> location mattered), I would switch in seconds.  Sadly, they are NOT
> equivalent.
>
> Marc
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> http://groups.google.com/group/twitter-development-talk?hl=en
>



-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: iPhone::Incorrect oauth_signature for xAuth?

[Nikolay Klimchuk]

That's really puzzling for me. I've tried 5 different ways to get
oauth_signature, even extracted from libraries suggested by Twitter
All of them produce same result MUYmiobRdoK6s0ZVqo4xQNNO17w=
It's different from example http://dev.twitter.com/pages/xauth

I'm looking for any logical explanation for this

Nikolay Klimchuk

On Sep 15, 12:03 pm, Taylor Singletary 
wrote:
> Hi Everyone,
>
> I've revised the xAuth examples athttp://dev.twitter.com/pages/xauth--
> you'll find they should have signatures that are easier to reproduce and was
> confirmed functional at the time of execution.
>
> Thanks for the nudge, Tom.
>
> Thanks,
> Taylor
>
> On Mon, Sep 13, 2010 at 11:41 AM, Tom van der Woerdt  wrote:
>
>
>
> > 2010-09-13 20:39:11.190 Test[56513:207] NSData *HMAC: <3146268a 86d17682
> > bab34655 aa8e3140 d34ed7bc>
> > 2010-09-13 20:39:11.191 Test[56513:207] NSString *HMAC64:
> > MUYmiobRdoK6s0ZVqo4xQNNO17w=
>
> > Looks like you're right :-)
>
> > @episod: You should fix that! :-)
>
> > Tom
>
> > On 9/13/10 8:23 PM, Nikolay Klimchuk wrote:
> > > Still no luck
>
> > > With your code I'm gettings exactly the same result
> > > MUYmiobRdoK6s0ZVqo4xQNNO17w=
>
> > > Something really strange in example here
> >http://dev.twitter.com/pages/xauth
>
> > > Nikolay Klimchuk
>
> > > On Sep 13, 7:19 am, Tom van der Woerdt  wrote:
> > >> Oh, hehe, good point. That's because my Base String has one extra
> > >> urlencoded '&' on the end, and that shouldn't be there.
>
> > >> Tom
>
> > >> On Mon, 13 Sep 2010 04:18:06 -0700 (PDT), Nikolay Klimchuk
>
> > >>  wrote:
> > >>> Thank you Tom
>
> > >>> I will try your algorithm and compare results.
> > >>> Quick question: why you do this [str substringToIndex:[str
> > >>> length]-3] ?
>
> > >>> Nikolay Klimchuk
>
> > >>> On Sep 13, 2:46 am, Tom van der Woerdt  wrote:
> >  Hi Nikolay,
>
> >  The first part of your code looks fine. You may, however, like to do
> >  some debugging on the HMAC part - it looks a bit too simple to me.
>
> >  This works :
> >          NSString *compKey = [NSString stringWithFormat:@
> > "%@&%@",secret,userSecret];
> >          const char *cKey = [compKey
> > cStringUsingEncoding:NSUTF8StringEncoding];
> >          const char *cData = [[str substringToIndex:[str length]-3]
> >  cStringUsingEncoding:NSUTF8StringEncoding];
> >          unsigned char cHMAC[CC_SHA1_DIGEST_LENGTH];
> >          CCHmac(kCCHmacAlgSHA1, cKey, strlen(cKey), cData,
> > strlen(cData), cHMAC);
> >          NSData *HMAC = [[NSData alloc] initWithBytes:cHMAC
> > length:sizeof(cHMAC)];
> >  (str being the Base String)
>
> >  Hope it helps :-)
>
> >  Tom
>
> >  On 9/13/10 3:02 AM, Nikolay Klimchuk wrote:
>
> > > I'm trying to understand why algorithm for calculation of
> > > oauth_signature does not give me the same result as shown here:
> > >http://dev.twitter.com/pages/xauth
>
> > > In my case I'm getting signedSK = 'MUYmiobRdoK6s0ZVqo4xQNNO17w='
>
> > > If I URL encode such result it's still very different from
> > > yUDBrcMMm6ghqBEKCFKVoJPIacU%3D
>
> > > I've tried different implementations, all of them give the same
> > > result. After few hours of exercises with all this stuff I completely
> > > run out of ideas, please help
>
> > > // Test with input data taken from Twitter page
>
> > > NSString *s= @"POST&https%3A%2F%2Fapi.twitter.com%2Foauth
> > > %2Faccess_token&oauth_consumer_key%3DsGNxxnqgZRHUt6NunK3uw
> > > %26oauth_nonce%3DWLxsobj4rhS2xmCbaAeT4aAkRfx4vSHX4OnYpTE77hA
> > > %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
> > > %3D1276101652%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth
> > > %26x_auth_password%3D%2525%2526123%2521aZ%252B
> > > %2528%2529456242134%26x_auth_username%3DtpFriendlyGiant";
>
> > > NSString *k = @"5kEQypKe7lFHnufLtsocB1vAzO07xLFgp2Pc4sp2vk&";
>
> > > NSString *signedSK = [NetworkManager base64forData:[NetworkManager
> > > HMACSHA1withKey:k forString:s]];
>
> > > // Source code
>
> > > + (NSData *)HMACSHA1withKey:(NSString *)key forString:(NSString
> > > *)string
> > > {
> > >    NSData *clearTextData = [string
> > > dataUsingEncoding:NSUTF8StringEncoding];
> > >    NSData *keyData = [key dataUsingEncoding:NSUTF8StringEncoding];
>
> > >    uint8_t digest[CC_SHA1_DIGEST_LENGTH] = {0};
>
> > >    CCHmacContext hmacContext;
> > >    CCHmacInit(&hmacContext, kCCHmacAlgSHA1, keyData.bytes,
> > > keyData.length);
> > >    CCHmacUpdate(&hmacContext, clearTextData.bytes,
> > > clearTextData.length);
> > >    CCHmacFinal(&hmacContext, digest);
>
> > >    return [NSData dataWithBytes:digest length:CC_SHA1_DIGEST_LENGTH];
> > > }
>
> > > //Sourcehttp://www.cocoadev.com/index.pl?BaseSixtyFour
>
> > > + (NSString *)base64forData:(NSData *)data
> > > {
> > >     static const char encodingTable[] =
> > > "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdef

[twitter-dev] Re: Twitter Search/Stream API

[@IDisposable]

> Also, all automated repetitive searching should be on the Streaming API.
> Search is intended largely for ad-hoc queries.

If Stream honored the location search (where the tweep's profile's
location mattered), I would switch in seconds.  Sadly, they are NOT
equivalent.

Marc

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: list members cursor is wrong

[themattharris]

Hey Brad,

Your full request URL doesn't contain the cursor parameter. It looks
like when you add the OAuth parameters you are dropping the cursor
one.
We recommend, instead of using query string or the POST body for OAuth
paramters you instead use the authorisation header.

In your case this would mean your URL would be:

http://api.twitter.com/1/endlesscities/urban/members.json?cursor=1343981850785981701

and in your request headers you would have:

Authorization: OAuth oauth_consumer_key="MgdaAGLAt4VQzGKvoczhA",
oauth_nonce="68156293", oauth_signature="QkEP3%2BsCmz0C
%2FdjHJcdgUyTDbuI%3D", oauth_signature_method="HMAC-SHA1",
oauth_timestamp="1284515562", oauth_token="18904533-
Y1BfS5tRvV7FnrynYFIoLojrL4FjrS0CUCrZbyoNx", oauth_version="1.0"

Hope that helps,
Matt

On Sep 14, 7:09 pm, Brad  wrote:
> Thanks, Matt,
>
> This is the full 
> requesthttp://api.twitter.com/1/endlesscities/urban/members.json?oauth_nonce...
>
> doing a urllib.urlopen( ) on that.
>
> This is the Python request object {'http_url': 'http://api.twitter.com/
> 1/endlesscities/urban/members.json?cursor=1343981850785981701',
> 'http_method': 'GET', 'parameters': {'oauth_nonce': '68156293',
> 'oauth_timestamp': 1284515562, 'oauth_consumer_key':
> 'MgdaAGLAt4VQzGKvoczhA', 'oauth_signature_method': 'HMAC-SHA1',
> 'oauth_version': '1.0', 'oauth_token': '18904533-
> Y1BfS5tRvV7FnrynYFIoLojrL4FjrS0CUCrZbyoNx', 'oauth_signature':
> 'QkEP3+sCmz0C/djHJcdgUyTDbuI='}}
>
> I get results back, so the auth is working, but the cursor stays the
> same.
>
> thanks for whatever insight you can give.
>
> On Sep 14, 10:37 am, Matt Harris  wrote:
>
>
>
> > GET works fine for this method and when I test the cursors for your
> > list below everything works correctly. So we can work out what is
> > going on can you share the headers you are sending to the API.
>
> > Also, you will want to update your URLs to the correct host. The
> > correct URL to use ishttp://api.twitter.com/1/--making your
> > request:
> >    http://api.twitter.com/1/endlesscities/urban/members.json?cursor=-1
>
> > Best,
> > Matt
>
> > On Sun, Sep 12, 2010 at 6:44 PM, Brad  wrote:
> > > maybe I'm doing something wrong, but the cursor returned from the list
> > > members call seems to be misbehaving.
>
> > > if I hit:
> > >http://twitter.com/endlesscities/urban/members.json?cursor=-1
>
> > > it returns
> > > "next_cursor":1343981850785981701, "previous_cursor":0
>
> > > if I pass it that new cursor:
> > >http://twitter.com/endlesscities/urban/members.json?cursor=1343981850...
>
> > > it returns the same thing:
> > > "next_cursor":1343981850785981701, "previous_cursor":0
>
> > > What's up with that? This has cropped up thanks to switching from
> > > basic Auth to Oauth. I'm doing a GET because it won't allow me to do a
> > > POST.
>
> > > thanks in advance for any help.
>
> > > --
> > > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > > API updates via Twitter:http://twitter.com/twitterapi
> > > Issues/Enhancements 
> > > Tracker:http://code.google.com/p/twitter-api/issues/list
> > > Change your membership to this 
> > > group:http://groups.google.com/group/twitter-development-talk?hl=en
>
> > --
>
> > Matt Harris
> > Developer Advocate, Twitterhttp://twitter.com/themattharris

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: Auto tweet implementation

[Mike]

Hi Morris,

This is assuming you are using the "twitter-oauth" library on
http://github.com/abraham/twitteroauth

Add some fields to your member table, "oauth_token" and
"oauth_token_secret"..
So you're member table may look like this:
id, username, oauth_token, oauth_token_secret

When a user signs up for an event check if oauth_token and
oauth_token_secret is NULL or empty or whatever... if it is then:

On callback.php; when the $_SESSION['access_token'] is set, you can
store those keys ($_SESSION['access_token']['oauth_token'] and
$_SESSION['access_token']['oauth_token_secret']) in your database for
the specific user.

Now, when a user signs up for the event all you got to do is grab the
oauth_token and oauth_token_secret from the database and use those
when initiating the Twitter class.

Hope this helps!

On Sep 15, 5:30 am, Morris Li  wrote:
> Hi,
>
> My client requested a function to enable his club members to auto post
> tweets to twitter when they join any event on the website. When any
> member signs up for an event, we do something about updating the
> database, and at that point, we also want to post a tweet to twitter.
>
> Following the example I can work out how to post a message using PHP
> after getting authorization. But what I can do now is slight different
> from what I need to. i.e. we expect a member login once on our site
> then he / she doesn't need to login again every time he / she signs an
> event. Is it possible to achieve this by a PHP script?
>
> Many thanks for all of you.
> Morris Li

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: Tweet button fails to parse URL

[John]

No reply to this for a while, so asking again. Matt, your first
response sounded like an acknowledgment that this is a bug. Is that
so, and if so, can we expect to see it fixed?

Best,
John

On Sep 6, 2:35 am, ecf  wrote:
> Same behavior withurlcontaining "+" characters!

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Twitter Search/Stream API

[M. Edward (Ed) Borasky]

Search allows you to go back in history (about a week) and retrieve  
tweets that Twitter has indexed. It also allows you to track a search  
in real time. Finally, it uses location information from the tweeting  
user's profile to attempt to locate where a tweet was posted, if  
there's no geotagging on the tweet.


Streaming only lets you track in real time, and location information  
is only available for geotagged tweets.


--
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 Mike :


What is the difference between the "Search" and "Stream" API?  I can't
really tell.  Detail would be great, and how it can be applied in the
real world other then the "Search" one over the "Stream".

--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:   
http://groups.google.com/group/twitter-development-talk?hl=en






--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: historical tweets

[M. Edward (Ed) Borasky]

I think Topsy also has indexed all the public tweets and has a search engine.
--
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 AdamD :


You might check with the folks at http://infochimps.org/

On Sep 15, 6:47 am, Kam  wrote:

Hi,

We have been harvesting the sample feed (spritzer and gardenhose) for
over two years now as part of an academic sentiment analysis project.
As the volume of tweets has increased, we've had our share of hiccups
retrieving and storing them. In particular, there is a 6 month period
in 2009 in which we have inconsistent tweet volume, about 4 weeks of
which we don't have any tweets. We are getting close to publication of
an initial paper, but would like to fill in the gaps.

The API does not seem to be set up to allow the retrieval of
historical tweets. We are hoping that either Twitter or somebody in
the data mining community could help us with these missing data.

Best,

Kameron Decker Harris
University of Vermont


--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:   
http://groups.google.com/group/twitter-development-talk?hl=en






--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] tweets history

[calyps]

Hello,

I need to somehow get my tweet history and including all the Re
tweets. I am trying to use the search API but i believe the search API
is restricted for only last certain days. Hence, i believe the only
possibility is to store it somewhere but i have the following
questions:

1) If the search API is restricted for last certain days, can i still
collect how many retweets were made (using the new twitter.com
method)?

2) can you recommend when i should try storing the tweets to ensure I
dont store duplicate tweets or What is the limit of search API so i
know every time i execute it, i will get new set of searches. This may
be how the tweetmeme.com holds the count of tweet? right?

Thanks,

Ali

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: Twitter Search/Stream API

[John Kalucki]

Also, all automated repetitive searching should be on the Streaming API.
Search is intended largely for ad-hoc queries.

-John Kalucki
http://twitter.com/jkalucki
Twitter Inc.


On Wed, Sep 15, 2010 at 12:25 PM, Justin  wrote:

> Also, from what I understand, search may not include everything, it's
> filtered a bit, streaming is everything.
>
>
> On Sep 15, 11:29 am, Tom van der Woerdt  wrote:
> > The search gives you back a list of tweets from the past, the stream
> > will send tweets to your application the moment they are sent.
> >
> > Tom
> >
> > On 9/15/10 6:13 PM, Mike wrote:
> >
> > > What is the difference between the "Search" and "Stream" API?  I can't
> > > really tell.  Detail would be great, and how it can be applied in the
> > > real world other then the "Search" one over the "Stream".
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk?hl=en
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] New twitter interface

[Tom van der Woerdt]

There are no changes to the API so your project should not be broken
(unless you are breaking Twitter's TOS).

Tom


On 9/15/10 9:56 PM, bobrik wrote:
> http://twitter.com/newtwitter - that's what I plan to talk about.
> 
> I have a project that could be broken by this new feature, but may be
> not as well. Does there any way to test new interface outside common
> slow feature rollout? Maybe some form to request that for developers
> only?
> 
> I don't think that common help request could help.
> 
> What do you think in common about new interface and possibilities to
> get involved?
> 

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Searching for old tweets

[Scott Wilcox]

Not currently, no.

On 15 Sep 2010, at 21:15, Mauricio Aniche wrote:

> Hi,
> 
> I need to search for old tweets with some specific hashtag. I want to
> use it in my master thesis to illustrate how popular of the term got.
> Unfortunately, the API only returns tweets for the last 10 days or so.
> 
> Is there a way to get tweets for the last 2 years, for example?
> 
> Thanks in advance,
> Mauricio

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Searching for old tweets

[Mauricio Aniche]

Hi,

I need to search for old tweets with some specific hashtag. I want to
use it in my master thesis to illustrate how popular of the term got.
Unfortunately, the API only returns tweets for the last 10 days or so.

Is there a way to get tweets for the last 2 years, for example?

Thanks in advance,
Mauricio

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: historical tweets

[AdamD]

You might check with the folks at http://infochimps.org/

On Sep 15, 6:47 am, Kam  wrote:
> Hi,
>
> We have been harvesting the sample feed (spritzer and gardenhose) for
> over two years now as part of an academic sentiment analysis project.
> As the volume of tweets has increased, we've had our share of hiccups
> retrieving and storing them. In particular, there is a 6 month period
> in 2009 in which we have inconsistent tweet volume, about 4 weeks of
> which we don't have any tweets. We are getting close to publication of
> an initial paper, but would like to fill in the gaps.
>
> The API does not seem to be set up to allow the retrieval of
> historical tweets. We are hoping that either Twitter or somebody in
> the data mining community could help us with these missing data.
>
> Best,
>
> Kameron Decker Harris
> University of Vermont

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] New twitter interface

[bobrik]

http://twitter.com/newtwitter - that's what I plan to talk about.

I have a project that could be broken by this new feature, but may be
not as well. Does there any way to test new interface outside common
slow feature rollout? Maybe some form to request that for developers
only?

I don't think that common help request could help.

What do you think in common about new interface and possibilities to
get involved?

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Twitter Search/Stream API

[Mike Flynn]

Finally a perfect answer! Thanks!

On Wed, Sep 15, 2010 at 9:29 AM, Tom van der Woerdt  wrote:
> The search gives you back a list of tweets from the past, the stream
> will send tweets to your application the moment they are sent.
>
> Tom
>
>
> On 9/15/10 6:13 PM, Mike wrote:
>> What is the difference between the "Search" and "Stream" API?  I can't
>> really tell.  Detail would be great, and how it can be applied in the
>> real world other then the "Search" one over the "Stream".
>>
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> http://groups.google.com/group/twitter-development-talk?hl=en
>



-- 
Mike Flynn
Creative Vision Media
502-939-2619
mfl...@cvmediaonline.com

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Twitter xauth login for posting and receiving Tweets

[Ernandes Jr.]

Your code looks OK! Either your problem is related to your keys our your
environment. Have you tryied to run you code on a real device?

On Wed, Sep 15, 2010 at 6:30 AM, vinod  wrote:

> Hi,
> Hi,
>
> I imported the libraries:
>
> xauth-encoders.jar
> kxml2-min-2.3.0.jar,
> mobile-ju-framework-1.0.jar
> twitter_api_me-1.3.jar
>
>
> After using Ernandes library i am receiving errors as below
> I used single access token here
> verification of credentials are successfull. but failed to Tweet and
> received below errors
>
> In WTK 3.0
> javax.microedition.io.ConnectionNotFoundException: ConnectionNotFound
> error in socket::open : error = 10060
>
> In WTK 2.5.2
> java.lang.SecurityException: Invalid / expired Token
>
> Source is as follows:
>
> Token token = new Token("token_access", "token_secret");
> Credential c = new Credential("rahulka...@gmail.com",
> "8oHIBK7T90Ye7GjIF6SToA",
> "4Ebm4f7bie2AAYyN75DxwSUYeg8x0SBlL0IyKIXzaw", token);
> UserAccountManager m = UserAccountManager.getInstance(c);
> try {
> if (m.verifyCredential()) {
> System.out.println("Consumer or token keys are success");
> Tweet t = new Tweet("Hi!!! This is my first tweet via Twitter API
> ME.");
> TweetER ter = TweetER.getInstance(m);
> t = ter.post(t);
>
> } else {
> System.out.println("Consumer or token keys are invalid!");
> }
> } catch (Exception ex) {
> System.out.println("Exception here1="+ex);
> }
>
> If i use normal credentials my application is not able to validate
> credentials itself
>
> In WTK 3.0
>
> javax.microedition.io.ConnectionNotFoundException: ConnectionNotFound
> error in socket::open : error = 10060
>
> In WTK 2.5.2
>
> Credentials unsucessfull
>
> Also when i am not able to import Equifax cert
> Please help to authentication, post and receive tweets using my
> application.
>
> Regards,
> Basu
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk?hl=en
>



-- 
Ernandes Jr.
-
"ALL programs are poems. However,
NOT all programmers are poets."

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: Twitter Search/Stream API

[Justin]

Also, from what I understand, search may not include everything, it's
filtered a bit, streaming is everything.


On Sep 15, 11:29 am, Tom van der Woerdt  wrote:
> The search gives you back a list of tweets from the past, the stream
> will send tweets to your application the moment they are sent.
>
> Tom
>
> On 9/15/10 6:13 PM, Mike wrote:
>
> > What is the difference between the "Search" and "Stream" API?  I can't
> > really tell.  Detail would be great, and how it can be applied in the
> > real world other then the "Search" one over the "Stream".

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Question about User Vs Site Streams, and Moving away from REST calls.

[Justin]

I've successfully migrated one of my sites away from making search and
mention rest calls, switched over to the streaming API and I'm loving
it. I still need to move it to OAuth but now that I have that in test
I'm reading up on the User and Site streams and I have a question.

It seems the User stream states that websites should not use it, and
should use the Site stream instead, but I don't consume or care about
my user's activity, my site is centered around the messages and
interactions with the application user not the users themselves.

Right now I track and evaluate followers and other bits using the rest
calls but from what I see I could eliminate those rest calls and be
off them (possibly) all together if I could use the User stream to
accept information about new and broken friendships, favorites, dms,
etc.

Is it acceptable to use the User stream in that manor since I would
only need it for the app user account not my site user's accounts? If
so, I can just maintain the two streams (filtered streaming api and
user stream) and eliminate or cut back my rest calls dramatically?
Please let me know so I can plan accordingly.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: POSTing problem

[Taylor Singletary]

Spotted some more encoding errors in your example -- on your oauth_token you
are encoding the "-" character (both in the base string and your
authorization header), which is not a reserved character for these purposes
(see http://oauth.net/core/1.0a/#encoding_parameters ) . What library, if
any, are you using to develop this?

Other things to verify: is your system's timestamp within +/- 5 minutes of
Twitter's servers at the time of request? Does your application record
reflect a read/write application?

Taylor

On Wed, Sep 15, 2010 at 11:24 AM, MTCoder  wrote:

> didnt work.
>
> i cant believe this is that hard.
>
> PLEASE HELP ME, THIS COMPUTER IS ABOUT TO SLEEP WITH THE FISHES
>
> thanks,
> MTCoder
>
> On Sep 14, 5:00 pm, MTCoder  wrote:
> > I am away from my work computer so i cant try out this suggestion just
> > yet but is this what it should look like when i do?
> >
> > basestring:
> >
> > POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml&
> > oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26
> > oauth_nonce%3D4E444934514E7A30544D344D6B3D673D%26
> > oauth_signature_method%3DHMAC-SHA1%26
> > oauth_timestamp%3D1284487942%26
> > oauth_token%3D180440869%2D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4%26
> > oauth_version%3D1.0%26
> > status%3Dsetting%2520up%2520my%2520twitter
> >
> > POST:
> >
> > POST /1/statuses/update.xml? HTTP/1.1
> > Content-Type: application/x-www-form-urlencoded
> > Authorization: OAuth oauth_nonce="4E444934514E7A30544D344D6B3D673D",
> >  oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284487942",
> >  oauth_consumer_key="3RmYCDlNEUoRLXmeQDgA",
> > oauth_token="180440869%252D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4",
> >  oauth_signature="w8K2sgFoGQuF7NrMTEeoDtiOCYI%3D",
> > oauth_version="1.0"
> > Content-Length: 40
> > status=setting%20up%20my%20twitter
> >
> > On Sep 14, 2:18 pm, Taylor Singletary 
> > wrote:
> >
> >
> >
> >
> >
> >
> >
> > > MTCoder:
> >
> > > You've got a little bit of an escaping problem here..
> >
> > > First, "spaces" aren't valid characters for your POST body. Personally,
> I
> > > recommend using %20 to represent a space. "+" would also be valid in a
> POST
> > > body.
> >
> > > Once your POST body is correct, the escaping for your OAuth signature
> base
> > > string is then considered.
> >
> > > If you used %20 to encode spaces in your POST body, then in your
> signature
> > > base string, %2520 should be used where a %20 was before. If you used
> "+" in
> > > your POST body, %2B should be used instead of "+" in your OAuth
> signature
> > > base string.
> >
> > > The OAuth signature base string's validity depends on the initial,
> valid
> > > encoding of your POST body.
> >
> > > Taylor
> >
> > > On Tue, Sep 14, 2010 at 1:11 PM, MTCoder  wrote:
> > > > all the keys are the same that use when making calls to get the
> > > > timeline.
> >
> > > > Steve
> >
> > > > On Sep 14, 1:08 pm, Tom van der Woerdt  wrote:
> > > > > Your Base String looks fine. Are you using the right keys to sign
> the
> > > > > request? Is there any response from the API, except for 401? (Error
> > > > > message?)
> >
> > > > > Tom
> >
> > > > > On 9/14/10 8:14 PM, MTCoder wrote:
> >
> > > > > > still getting the 401
> >
> > > > > > basestring:
> > > > > > POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml&
> > > > > > oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26
> > > > > > oauth_nonce%3D4E444934514E7A30544D344D6B3D673D%26
> > > > > > oauth_signature_method%3DHMAC-SHA1%26
> > > > > > oauth_timestamp%3D1284487942%26
> > > > > >
> oauth_token%3D180440869%2D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4%26
> > > > > > oauth_version%3D1.0%26
> > > > > > status%3Dsetting%2520up%2520my%2520twitter
> >
> > > > > > POST:
> > > > > > POST /1/statuses/update.xml? HTTP/1.1
> > > > > > Content-Type: application/x-www-form-urlencoded
> > > > > > Authorization: OAuth
> oauth_nonce="4E444934514E7A30544D344D6B3D673D",
> > > > > >  oauth_signature_method="HMAC-SHA1",
> oauth_timestamp="1284487942",
> > > > > >  oauth_consumer_key="3RmYCDlNEUoRLXmeQDgA",
> > > > > >
> oauth_token="180440869%252D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4",
> > > > > >  oauth_signature="w8K2sgFoGQuF7NrMTEeoDtiOCYI%3D",
> oauth_version="1.0"
> > > > > > Content-Length: 40
> >
> > > > > > status=setting%2520up%2520my%2520twitter
> >
> > > > > > On Sep 14, 11:39 am, Tom van der Woerdt  wrote:
> > > > > >> It says "setting up my twitter" in the Base String, not
> > > > "status=setting
> > > > > >> up my twitter".
> >
> > > > > >> Tom
> >
> > > > > >> On 9/14/10 7:30 PM, MTCoder wrote:
> >
> > > > > >>> Im posting this again here to make sure its seen (other thread
> here
> >
> > > >
> http://groups.google.com/group/twitter-development-talk/browse_thread...)
> >
> > > > > >>> I have tried many different things and cant seem to get the
> status
> > > > > >>> POST to work(thanks Tom for the help with getting the
> timeline).
> >
> > > > > >>> my base string:
> >
> > > > > >>> POST&http%3A%2F%2Fapi.twitter.com

[twitter-dev] Re: POSTing problem

[MTCoder]

didnt work.

i cant believe this is that hard.

PLEASE HELP ME, THIS COMPUTER IS ABOUT TO SLEEP WITH THE FISHES

thanks,
MTCoder

On Sep 14, 5:00 pm, MTCoder  wrote:
> I am away from my work computer so i cant try out this suggestion just
> yet but is this what it should look like when i do?
>
> basestring:
>
> POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml&
> oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26
> oauth_nonce%3D4E444934514E7A30544D344D6B3D673D%26
> oauth_signature_method%3DHMAC-SHA1%26
> oauth_timestamp%3D1284487942%26
> oauth_token%3D180440869%2D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4%26
> oauth_version%3D1.0%26
> status%3Dsetting%2520up%2520my%2520twitter
>
> POST:
>
> POST /1/statuses/update.xml? HTTP/1.1
> Content-Type: application/x-www-form-urlencoded
> Authorization: OAuth oauth_nonce="4E444934514E7A30544D344D6B3D673D",
>  oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284487942",
>  oauth_consumer_key="3RmYCDlNEUoRLXmeQDgA",
> oauth_token="180440869%252D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4",
>  oauth_signature="w8K2sgFoGQuF7NrMTEeoDtiOCYI%3D",
> oauth_version="1.0"
> Content-Length: 40
> status=setting%20up%20my%20twitter
>
> On Sep 14, 2:18 pm, Taylor Singletary 
> wrote:
>
>
>
>
>
>
>
> > MTCoder:
>
> > You've got a little bit of an escaping problem here..
>
> > First, "spaces" aren't valid characters for your POST body. Personally, I
> > recommend using %20 to represent a space. "+" would also be valid in a POST
> > body.
>
> > Once your POST body is correct, the escaping for your OAuth signature base
> > string is then considered.
>
> > If you used %20 to encode spaces in your POST body, then in your signature
> > base string, %2520 should be used where a %20 was before. If you used "+" in
> > your POST body, %2B should be used instead of "+" in your OAuth signature
> > base string.
>
> > The OAuth signature base string's validity depends on the initial, valid
> > encoding of your POST body.
>
> > Taylor
>
> > On Tue, Sep 14, 2010 at 1:11 PM, MTCoder  wrote:
> > > all the keys are the same that use when making calls to get the
> > > timeline.
>
> > > Steve
>
> > > On Sep 14, 1:08 pm, Tom van der Woerdt  wrote:
> > > > Your Base String looks fine. Are you using the right keys to sign the
> > > > request? Is there any response from the API, except for 401? (Error
> > > > message?)
>
> > > > Tom
>
> > > > On 9/14/10 8:14 PM, MTCoder wrote:
>
> > > > > still getting the 401
>
> > > > > basestring:
> > > > > POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml&
> > > > > oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26
> > > > > oauth_nonce%3D4E444934514E7A30544D344D6B3D673D%26
> > > > > oauth_signature_method%3DHMAC-SHA1%26
> > > > > oauth_timestamp%3D1284487942%26
> > > > > oauth_token%3D180440869%2D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4%26
> > > > > oauth_version%3D1.0%26
> > > > > status%3Dsetting%2520up%2520my%2520twitter
>
> > > > > POST:
> > > > > POST /1/statuses/update.xml? HTTP/1.1
> > > > > Content-Type: application/x-www-form-urlencoded
> > > > > Authorization: OAuth oauth_nonce="4E444934514E7A30544D344D6B3D673D",
> > > > >  oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284487942",
> > > > >  oauth_consumer_key="3RmYCDlNEUoRLXmeQDgA",
> > > > > oauth_token="180440869%252D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4",
> > > > >  oauth_signature="w8K2sgFoGQuF7NrMTEeoDtiOCYI%3D", oauth_version="1.0"
> > > > > Content-Length: 40
>
> > > > > status=setting%2520up%2520my%2520twitter
>
> > > > > On Sep 14, 11:39 am, Tom van der Woerdt  wrote:
> > > > >> It says "setting up my twitter" in the Base String, not
> > > "status=setting
> > > > >> up my twitter".
>
> > > > >> Tom
>
> > > > >> On 9/14/10 7:30 PM, MTCoder wrote:
>
> > > > >>> Im posting this again here to make sure its seen (other thread here
>
> > >http://groups.google.com/group/twitter-development-talk/browse_thread...)
>
> > > > >>> I have tried many different things and cant seem to get the status
> > > > >>> POST to work(thanks Tom for the help with getting the timeline).
>
> > > > >>> my base string:
>
> > > > >>> POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fupdate.xml&
> > > > >>> oauth_consumer_key%3D3RmYCDlNEUoRLXmeQDgA%26
> > > > >>> oauth_nonce%3D544D44594D4E347A7735514D3D3D4934%26
> > > > >>> oauth_signature_method%3DHMAC-SHA1%26
> > > > >>> oauth_timestamp%3D1284483693%26
> > > > >>> oauth_token%3D180440869%2D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4%26
> > > > >>> oauth_version%3D1.0%26setting%2520up%2520my%2520twitter
>
> > > > >>> And the POST:
>
> > > > >>> POST /1/statuses/update.xml? HTTP/1.1
> > > > >>> Content-Type: application/x-www-form-urlencoded
> > > > >>> Authorization: OAuth oauth_nonce="544D44594D4E347A7735514D3D3D4934",
> > > > >>>  oauth_signature_method="HMAC-SHA1", oauth_timestamp="1284483693",
> > > > >>>  oauth_consumer_key="3RmYCDlNEUoRLXmeQDgA",
> > > > >>> oauth_token="180440869%252D38LrgS7ccUZ9l2M1SD5ODKclih3AOiUb6nist1y4",
> > > > >>>  oauth_

[twitter-dev] Re: Any plans to increase user_timeline limit of 3200

[Invader]

Thanks for the quick response. I eagerly await when your
infrastructure is ready to allow a larger limit.

On Sep 15, 12:52 pm, Taylor Singletary 
wrote:
> Hi Invader,
>
> We'd love to provide more tweets than that but infrastructure issues prevent
> it at this time. There is no timeline for historical tweet access right now.
>
> Taylor
>
>
>
> On Wed, Sep 15, 2010 at 9:51 AM, Invader  wrote:
> > My app is a tweet backup app and is highly dependent on accessing old
> > tweets. Are there any plans on increasing the user_timeline 3200 limit?
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >http://groups.google.com/group/twitter-development-talk?hl=en

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: Auto tweet implementation

[Ken]

Yes.

This is a FAQ. Until Twitter staff update the group FAQ, search the
group archives for "My Access Token".

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Any plans to increase user_timeline limit of 3200

[Taylor Singletary]

Hi Invader,

We'd love to provide more tweets than that but infrastructure issues prevent
it at this time. There is no timeline for historical tweet access right now.

Taylor

On Wed, Sep 15, 2010 at 9:51 AM, Invader  wrote:

> My app is a tweet backup app and is highly dependent on accessing old
> tweets. Are there any plans on increasing the user_timeline 3200 limit?
>
> --
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> http://groups.google.com/group/twitter-development-talk?hl=en
>

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Any plans to increase user_timeline limit of 3200

[Invader]

My app is a tweet backup app and is highly dependent on accessing old
tweets. Are there any plans on increasing the user_timeline 3200 limit?

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Twitter Search/Stream API

[Mike]

What is the difference between the "Search" and "Stream" API?  I can't
really tell.  Detail would be great, and how it can be applied in the
real world other then the "Search" one over the "Stream".

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Twitter Search/Stream API

[Tom van der Woerdt]

The search gives you back a list of tweets from the past, the stream
will send tweets to your application the moment they are sent.

Tom


On 9/15/10 6:13 PM, Mike wrote:
> What is the difference between the "Search" and "Stream" API?  I can't
> really tell.  Detail would be great, and how it can be applied in the
> real world other then the "Search" one over the "Stream".
> 

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: iPhone::Incorrect oauth_signature for xAuth?

[Taylor Singletary]

Hi Everyone,

I've revised the xAuth examples at http://dev.twitter.com/pages/xauth --
you'll find they should have signatures that are easier to reproduce and was
confirmed functional at the time of execution.

Thanks for the nudge, Tom.

Thanks,
Taylor


On Mon, Sep 13, 2010 at 11:41 AM, Tom van der Woerdt  wrote:

> 2010-09-13 20:39:11.190 Test[56513:207] NSData *HMAC: <3146268a 86d17682
> bab34655 aa8e3140 d34ed7bc>
> 2010-09-13 20:39:11.191 Test[56513:207] NSString *HMAC64:
> MUYmiobRdoK6s0ZVqo4xQNNO17w=
>
> Looks like you're right :-)
>
> @episod: You should fix that! :-)
>
> Tom
>
>
> On 9/13/10 8:23 PM, Nikolay Klimchuk wrote:
> > Still no luck
> >
> > With your code I'm gettings exactly the same result
> > MUYmiobRdoK6s0ZVqo4xQNNO17w=
> >
> > Something really strange in example here
> http://dev.twitter.com/pages/xauth
> >
> > Nikolay Klimchuk
> >
> > On Sep 13, 7:19 am, Tom van der Woerdt  wrote:
> >> Oh, hehe, good point. That's because my Base String has one extra
> >> urlencoded '&' on the end, and that shouldn't be there.
> >>
> >> Tom
> >>
> >> On Mon, 13 Sep 2010 04:18:06 -0700 (PDT), Nikolay Klimchuk
> >>
> >>
> >>
> >>  wrote:
> >>> Thank you Tom
> >>
> >>> I will try your algorithm and compare results.
> >>> Quick question: why you do this [str substringToIndex:[str
> >>> length]-3] ?
> >>
> >>> Nikolay Klimchuk
> >>
> >>> On Sep 13, 2:46 am, Tom van der Woerdt  wrote:
>  Hi Nikolay,
> >>
>  The first part of your code looks fine. You may, however, like to do
>  some debugging on the HMAC part - it looks a bit too simple to me.
> >>
>  This works :
>  NSString *compKey = [NSString stringWithFormat:@
> "%@&%@",secret,userSecret];
>  const char *cKey = [compKey
> cStringUsingEncoding:NSUTF8StringEncoding];
>  const char *cData = [[str substringToIndex:[str length]-3]
>  cStringUsingEncoding:NSUTF8StringEncoding];
>  unsigned char cHMAC[CC_SHA1_DIGEST_LENGTH];
>  CCHmac(kCCHmacAlgSHA1, cKey, strlen(cKey), cData,
> strlen(cData), cHMAC);
>  NSData *HMAC = [[NSData alloc] initWithBytes:cHMAC
> length:sizeof(cHMAC)];
>  (str being the Base String)
> >>
>  Hope it helps :-)
> >>
>  Tom
> >>
>  On 9/13/10 3:02 AM, Nikolay Klimchuk wrote:
> >>
> > I'm trying to understand why algorithm for calculation of
> > oauth_signature does not give me the same result as shown here:
> > http://dev.twitter.com/pages/xauth
> >>
> > In my case I'm getting signedSK = 'MUYmiobRdoK6s0ZVqo4xQNNO17w='
> >>
> > If I URL encode such result it's still very different from
> > yUDBrcMMm6ghqBEKCFKVoJPIacU%3D
> >>
> > I've tried different implementations, all of them give the same
> > result. After few hours of exercises with all this stuff I completely
> > run out of ideas, please help
> >>
> > // Test with input data taken from Twitter page
> >>
> > NSString *s= @"POST&https%3A%2F%2Fapi.twitter.com%2Foauth
> > %2Faccess_token&oauth_consumer_key%3DsGNxxnqgZRHUt6NunK3uw
> > %26oauth_nonce%3DWLxsobj4rhS2xmCbaAeT4aAkRfx4vSHX4OnYpTE77hA
> > %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
> > %3D1276101652%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth
> > %26x_auth_password%3D%2525%2526123%2521aZ%252B
> > %2528%2529456242134%26x_auth_username%3DtpFriendlyGiant";
> >>
> > NSString *k = @"5kEQypKe7lFHnufLtsocB1vAzO07xLFgp2Pc4sp2vk&";
> >>
> > NSString *signedSK = [NetworkManager base64forData:[NetworkManager
> > HMACSHA1withKey:k forString:s]];
> >>
> > // Source code
> >>
> > + (NSData *)HMACSHA1withKey:(NSString *)key forString:(NSString
> > *)string
> > {
> >NSData *clearTextData = [string
> > dataUsingEncoding:NSUTF8StringEncoding];
> >NSData *keyData = [key dataUsingEncoding:NSUTF8StringEncoding];
> >>
> >uint8_t digest[CC_SHA1_DIGEST_LENGTH] = {0};
> >>
> >CCHmacContext hmacContext;
> >CCHmacInit(&hmacContext, kCCHmacAlgSHA1, keyData.bytes,
> > keyData.length);
> >CCHmacUpdate(&hmacContext, clearTextData.bytes,
> > clearTextData.length);
> >CCHmacFinal(&hmacContext, digest);
> >>
> >return [NSData dataWithBytes:digest length:CC_SHA1_DIGEST_LENGTH];
> > }
> >>
> > //Sourcehttp://www.cocoadev.com/index.pl?BaseSixtyFour
> >>
> > + (NSString *)base64forData:(NSData *)data
> > {
> > static const char encodingTable[] =
> > "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/";
> >>
> > if ([data length] == 0)
> > return @"";
> >>
> > char *characters = malloc((([data length] + 2) / 3) * 4);
> > if (characters == NULL)
> > return nil;
> > NSUInteger length = 0;
> >>
> > NSUInteger i = 0;
> > while (i < [data length])
> > {
> > char buffer[3] = {0,0,0};
> > short bufferLength = 0;
> > while

Re: [twitter-dev] signature with xAuth

[Tom van der Woerdt]

On 9/15/10 3:38 PM, andy wrote:
> Can someone explain to me exactly how I cover the parameter
> "oauth_signature"? The documentation of Twitter is as difficult. Do I
> use my Access_token_secret?
> 

You may like to read the OAuth 1.0 RFC itself instead of the Twitter
docs. http://tools.ietf.org/html/rfc5849#section-3.4

Tom

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] Re: HttpRequest and Unshortening problems

[João Paulo Sabino de Moraes]

I'm using AS3 / Flex , but I can call javascript functions.
do you know any similar javascript function ?

other question... if the url is already unshortened, will the returned array
contain the same unshortened link at 'location' index ?

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: Geo Search -> Tweet Search

[johnw]

I've been testing with averaging the points to get the centerpoint and
passing to Twitter with the Search API.  Seems to be working.

On Sep 14, 12:20 pm, johnw  wrote:
> I have the results from Geo Search coming back and I want to feed this
> into a subsequent Search API query to base the tweet search radius on.
>
> However,  I'm not sure the best means to use the bounding box
> coordinates.  Given this:
>
>       "bounding_box": {
>           "coordinates": [
>             [[
>                 -82.437165,
>                 41.065485
>               ], [
>                 -82.387024,
>                 41.065485
>               ], [
>                 -82.387024,
>                 41.094768
>               ],  [
>                 -82.437165,
>                 41.094768
>               ]
>             ]
>           ],
>
> The (tweet) Search API requires a single lat/long for a geo radius,
> not a bounding box.  I am assuming that it would be best to calculate
> the central point of the four coordinates and pass that onto Search?
> I wonder what Twitter does in their advanced search, under the covers,
> as they would have the same issue.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: HttpRequest and Unshortening problems

[johnw]

I'm using PHP and used get_headers: 
http://php.net/manual/en/function.get-headers.php.
If you are not using PHP, maybe there is an equivalent in whatever you
are using.

I inspect the returned array and see if there is a 301 code in
Array[0] and then get Array['location'] for the unshortened url.

John

On Sep 15, 9:49 am, João Paulo Sabino de Moraes 
wrote:
> Anybody ?
> --
> João Paulo S. de Moraes
> +55 81 3432 3804
> +55 81 9189 3814 (mobile)

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] historical tweets

[Kam]

Hi,

We have been harvesting the sample feed (spritzer and gardenhose) for
over two years now as part of an academic sentiment analysis project.
As the volume of tweets has increased, we've had our share of hiccups
retrieving and storing them. In particular, there is a 6 month period
in 2009 in which we have inconsistent tweet volume, about 4 weeks of
which we don't have any tweets. We are getting close to publication of
an initial paper, but would like to fill in the gaps.

The API does not seem to be set up to allow the retrieval of
historical tweets. We are hoping that either Twitter or somebody in
the data mining community could help us with these missing data.

Best,

Kameron Decker Harris
University of Vermont

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Auto tweet implementation

[Morris Li]

Hi,

My client requested a function to enable his club members to auto post
tweets to twitter when they join any event on the website. When any
member signs up for an event, we do something about updating the
database, and at that point, we also want to post a tweet to twitter.

Following the example I can work out how to post a message using PHP
after getting authorization. But what I can do now is slight different
from what I need to. i.e. we expect a member login once on our site
then he / she doesn't need to login again every time he / she signs an
event. Is it possible to achieve this by a PHP script?

Many thanks for all of you.
Morris Li

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Twitter xauth login for posting and receiving Tweets

[vinod]

Hi,
Hi,

I imported the libraries:

xauth-encoders.jar
kxml2-min-2.3.0.jar,
mobile-ju-framework-1.0.jar
twitter_api_me-1.3.jar


After using Ernandes library i am receiving errors as below
I used single access token here
verification of credentials are successfull. but failed to Tweet and
received below errors

In WTK 3.0
javax.microedition.io.ConnectionNotFoundException: ConnectionNotFound
error in socket::open : error = 10060

In WTK 2.5.2
java.lang.SecurityException: Invalid / expired Token

Source is as follows:

Token token = new Token("token_access", "token_secret");
Credential c = new Credential("rahulka...@gmail.com",
"8oHIBK7T90Ye7GjIF6SToA",
"4Ebm4f7bie2AAYyN75DxwSUYeg8x0SBlL0IyKIXzaw", token);
UserAccountManager m = UserAccountManager.getInstance(c);
try {
if (m.verifyCredential()) {
System.out.println("Consumer or token keys are success");
Tweet t = new Tweet("Hi!!! This is my first tweet via Twitter API
ME.");
TweetER ter = TweetER.getInstance(m);
t = ter.post(t);

} else {
System.out.println("Consumer or token keys are invalid!");
}
} catch (Exception ex) {
System.out.println("Exception here1="+ex);
}

If i use normal credentials my application is not able to validate
credentials itself

In WTK 3.0

javax.microedition.io.ConnectionNotFoundException: ConnectionNotFound
error in socket::open : error = 10060

In WTK 2.5.2

Credentials unsucessfull

Also when i am not able to import Equifax cert
Please help to authentication, post and receive tweets using my
application.

Regards,
Basu

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: HttpRequest and Unshortening problems

[João Paulo Sabino de Moraes]

Anybody ?
-- 
João Paulo S. de Moraes
+55 81 3432 3804
+55 81 9189 3814 (mobile)

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Help for twitteroauth

[kilotto]

Hi all,

I'm trying use twitteroauth but I have some problems.

When I use twitter twitteroauth in my webserver ( http://twitter.domain.net
)  the script display the error: "Could not connect to Twitter.
Refresh the page or try again later.".

If I use other script, it display: "Woah there! This page is no longer
valid. It looks like someone already used the token information you
provided. Please return to the site that sent you to this page and try
again ... it was probably an honest mistake."

I've tried twitteroauth in local and it works fine.

How I can fix this ?

Tnx!

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: Tweet Button counter url encoding

[Remo]

Hi Matt

Thank you for your response!

The #newtwitter looks great btw!

Cheers
Remo

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] signature with xAuth

[andy]

Can someone explain to me exactly how I cover the parameter
"oauth_signature"? The documentation of Twitter is as difficult. Do I
use my Access_token_secret?

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Awesome

[Jacky]

Simply awesome...great effort !

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

[twitter-dev] Re: twitter relationship

[ashy]

Hi Matt,

But can I use it as a production database like mysql?

thanks
ashy

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Re: [twitter-dev] New Twitter API?

[Minhee Kim]

Thanks Tom for your advice,

I've found out the issue  "Account Verification Request Form Broken" at
Twitter Help Center.
I guess that would be the reason for 401 error.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en