PJB wrote:
On Oct 21, 8:01 pm, Dewald Pretorius dpr...@gmail.com wrote:
On Wednesday afternoon/evening the 502s and connection refuses have
been coming thick and fast, much worse than earlier in the week.
When can we expect to see an improvement instead of a worsening of
the API's
Yeah exactly what i was thinking but i thought this was the whole
point of oauth to not need someones pass to authenticate with an app.
Oauth is basically just a setup where it authenticates an app to use
an account, but its not something that I can use to implement a full
login system to my own
Hi guys,
I requested whitelisting API rate limit to twitter and got
approved before 2 days. However, still i am facing the same API rate
limit (150) problem. I have checked it and it did not change from 150
to 20,000 for my account.
does anybody know what went wrong?
my screen name is
Sorry, I should have said that it is the authorization url that
remains the same until a user actually accepts your application.
It is the authorization url that becomes stale if reused, or unused
for a period of time. Access tokens, as you quite rightly say, don't
expire unless revoked.
I
On Wed, Oct 21, 2009 at 11:22:44AM -0700, JB wrote:
Does anyone have a way to compare these two strings in PHP?
I have tried 3 different ways of comparing strings and they all fail.
Even more so recently.
Looking for a solid way to see if a tweet was accepted by the API or
not.
Remember
On Oct 21, 11:28 pm, Nigel Cannings nigelcanni...@googlemail.com
wrote:
Hope that is a better explanation, and might I say on behalf of all
the Perl hackers on the list, keep the good work up!
Hear hear! Net::Twitter is a brilliant and easy-to-use Perl interface
to Twitter.
On Thu, Oct 22, 2009 at 1:39 AM, PJB pjbmancun...@gmail.com wrote:
On Oct 21, 11:28 pm, Nigel Cannings nigelcanni...@googlemail.com
wrote:
Hope that is a better explanation, and might I say on behalf of all
the Perl hackers on the list, keep the good work up!
Hear hear! Net::Twitter
I hope not, Apple are being especially slow at approving my update at
the moment that includes the cursor changes!
On Oct 22, 3:20 am, DustyReagan dustyrea...@gmail.com wrote:
Is page deprecation still scheduled to happen on Oct. 26th?
Is this deprecation happening on all methods that have
Exactly the same scenario here [1] too. Querying with Bulk Ids would
save quite a bit of overhead for both parties.
Btw, if so many people are doing this graph-walking exercise, how
about collaborating and sharing this data? Feel free to contact me off-
list at { harshad.rj AT gmail }
[1]
That's true, it does violate one of the tenets of OAuth. In your case,
saving the access token may not be the most ideal solution, for the simple
fact that you apparently ONLY deal with Twitter and you expect logins from
multiple systems. You could either require OAuth at every step using Sign
in
Keep in mind too, OAuth is really for authorizing, not authenticating
... may sound pedantic, but it's a pretty substantial difference. The
authentication stuff is more of an after thought ...
∞ Andy Badera
∞ +1 518-641-1280
∞ This email is: [ ] bloggable [x] ask first [ ] private
∞ Google me:
Agreed. I think that's something a lot of people misinterpret. OAuth is
for API authorization, not Twitter authentication.
Ryan
On Thu, Oct 22, 2009 at 9:35 AM, Andrew Badera and...@badera.us wrote:
Keep in mind too, OAuth is really for authorizing, not authenticating
... may sound
Hi,
based on the TWITTER API helppage I tried the following statement
(lets assume username:testaccount with password=password):
$pic_update='curl -u testaccount:password -F
image=@'01.png;type=image/
png' http://twitter.com/account/update_profile_image.xml';
print $pic_update;
But, this did
Thanks for those of you signed up (or tried to sign up) to test
http://tags.linkky.com
Well, if you saw my previous post on my Perl OAuth issues, you may have
realised that I managed to get no-one signed up (there were a few minor
problems entirely of my devising as well!)
Anyhow, without
You need to force curl to drop the Expect: header: curl -u userid:password
-H Expect: -F ima...@01.png
http://twitter.com/account/update_profile_image.xml
--
-ed costello
I've got the same problem too with this. We were parallel fetching the
friends list but this new method is going to be too slow and I agree
with Josh that we really need a way to bulk request user payloads by
giving a list of IDs
On Oct 22, 2:10 pm, Harshad harshad...@gmail.com wrote:
Exactly
Hey guys,
@ev: It's not cool to RT a protected tweet
http://twitter.com/ev/status/4955618846
Will the new RT api disallow you from RT'ing protected tweets? I
think this would be a good move.
Tim.
Let's say that after a user allows and Twitter grants an access
token which I persist my app's db, what is the best design to
authenicate this user and match them to the stored token?
If I use a browser cookie (hopefully not with the value of the user's
Twitter User Id which is public, lol) and
Protected tweets will not be retweetable.
On Thu, Oct 22, 2009 at 11:42 AM, Tim Haines tmhai...@gmail.com wrote:
Hey guys,
@ev: It's not cool to RT a protected tweet
http://twitter.com/ev/status/4955618846
Will the new RT api disallow you from RT'ing protected tweets? I
think this
You could encrypt/decrypt the token in a cookie. You certainly wouldn't
want to store it in plain-text.
Or, in your database, have username, password, and access token. The user
enters their username and password to authenticate to you that they are that
user.
The more secure part of OAuth is
Hi,
One of my members cannot connect with a specific account, where other
accounts work. The account is not suspended. Every login try ends with
a OK, you've denied *Twitoaster* access to interact with your
account!.
Account name is @msbookish. Anyone would have experienced that kind
of
The user was authenticating with firefox and this plugin:
https://addons.mozilla.org/en-US/firefox/addon/750
Desactivating the plugin solved the problem.
Hoping that will be useful, if someone already experienced a similar
case,
Arnaud.
On Oct 22, 10:58 pm, Arnaud Meunier
On Oct 21, 11:28 pm, Nigel Cannings nigelcanni...@googlemail.com
wrote:
Sorry, I should have said that it is the authorization url that
remains the same until a user actually accepts your application.
It is the authorization url that becomes stale if reused, or unused
for a period of time.
On Oct 22, 12:54 am, Jesse Stay jesses...@gmail.com wrote:
Same here! BTW, if anyone wants a Catalyst OAuth Authentication::Credentials
module I've got one written - just getting it ready for CPAN right now.
Jesse, let me know when the module is on CPAN. I'll add it to the SEE
ALSO
section in
Hi,
I am collating the thoughts in this thread [1] into a proposal to improve
the efficiency of social-graphing applications.
A common API access pattern for social-graphing applications seems to be:
1. Get the friend/follower ids of a user with [*friends/ids*] or [*
followers/ids*]
2. Get user
I see. Thanks! It sort of makes me emo to have to manage seperate
credentials. Looking for more of a SSO solution, but thats cool.
Interesting tho, Twitter is putting a lot of trust in the third-party
app that they won't mismange tokens. At least it's better than basic
auth. Thanks again.
On
http://code.google.com/p/twitter-api/issues/detail?id=1078
On Fri, Oct 23, 2009 at 7:52 AM, Harshad RJ harshad...@gmail.com wrote:
Hi,
I am collating the thoughts in this thread [1] into a proposal to improve
the efficiency of social-graphing applications.
A common API access pattern for
Hi,
To reply for a tweet, I used twitter.updateStatus
(status,inreplyStatusId) api. Reply posted successfully to twitter
but it shows only about 2 minutes ago from Twitter 4j and it does
not show in reply to 'original tweet'.
Am I using the right api or Is there any api to show a link to
Thanks Tim for the reference, I have starred it.
That issue suggests bulk-id support, but there is no proposal for a
compromise on the size of the data. It might be a crucial difference to
Twitter.
On Fri, Oct 23, 2009 at 5:00 AM, Tim Haines tmhai...@gmail.com wrote:
I don't see why the data size would make a difference. I currently
request the same amount of data in 100 calls of 1 user, as I would in
1 call of 100 users. My application does require a little more info
than yours apparently, and I'm sure every app requires a different
subset, so a user
Michael,
On Fri, Oct 23, 2009 at 8:36 AM, Michael Steuer mste...@gmail.com wrote:
I don't see why the data size would make a difference.
If you application needs the complete data, then it won't make a difference.
But for applications that don't need it, it directly impacts bandwidth, and
Welcome the the Twitter Development Talk
I meant to send that to list owner. Sorry.
33 matches
Mail list logo
