Hi all,
I've been trying to write a JavaScript OAuth module in order to write
my own twitter client (I know there are libraries out there, but it's
for my education as well as fun).
I'm stumped, unfortunately, right at the beginning -- trying to get a
request token. I've tried GETting and POSTin
Working within the rate limits is a really big pain in the tail :).
Had to get that off my chest. The issue I'm seeing is that I'm
getting the following response with a 403 code.
{"request":"\/direct_messages\/new.json","error":"There was an error
sending your message: You can't send direct mes
Running this request:
http://search.twitter.com/search.atom?q=linux
and then fetching the 'refresh' link doesn't work.
http://search.twitter.com/search.atom?q=linux&since_id=2011153563
Is this broken?
The documentation seems to hint that I can use this to fetch more
content after this item.
This is working for me in IE 8 now. I've not tested IE 7.
-Dave
On Jun 2, 6:02 pm, Matt Sanford wrote:
> Hi all,
>
> The fix for this went out about 20 minutes ago [1] and I'm
> waiting on equally voracious users of Google Code to reply and make
> sure it's working right. This deploy a
Working for me know. Thank you!
On Jun 2, 3:02 pm, Matt Sanford wrote:
> Hi all,
>
> The fix for this went out about 20 minutes ago [1] and I'm
> waiting on equally voracious users of Google Code to reply and make
> sure it's working right. This deploy also had a fix for the http/https
Hi Dave,
A fix for this went out this afternoon. Everything should be
working without security warnings again. We also added some better
tests to prevent the Big Scary Warning™ in the future.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On Jun 1, 2009, at 3:49 PM, Dave wrote:
Hi Dale,
There hasn't been and change in the follow email policy to my
knowledge. In the example you provided where you un-follow and re-
follow are you getting the mail inconsistently or never? Knowing which
should help me track down that case at the very least.
Thanks;
– Matt Sanfo
Hi all,
The fix for this went out about 20 minutes ago [1] and I'm
waiting on equally voracious users of Google Code to reply and make
sure it's working right. This deploy also had a fix for the http/https
issue on the same page (and it turns out elsewhere on the site)
causing a warn
I'm confused about how since_id and page should be used. Can they be
used together in the same search.atom command?
I get different results with search.atom depending upon what order I
place the since_id and the page parameters. For example,
http://search.twitter.com/search.atom?q=blah&rpp=10&s
Yes, please hurry! Internet Explorer is still utilized by a few
vociferous users.
On Jun 2, 7:30 am, alon wrote:
> you da man!
>
> On Jun 2, 4:35 pm, Matt Sanford wrote:
>
> > Hi there,
>
> > It looks like this went out along with a few other things
> > yesterday. I'll get a fix ready to
Thanks for considering this Doug. I figured it probably wouldn't be
possible until 100% OAuth was in place, but at least the idea's out there.
Looking forward to when that happens!
@Jesse
On Tue, Jun 2, 2009 at 2:11 PM, Doug Williams wrote:
> Chad is correct. Until we have everyone pushed thro
Are these authenticated API requests? If the are unauthenticated there is
probably some other application originating from that IP eating up the the
API hits. I just test rate_limit_status several times unauthenticated and
saw no change in remaining hits.
On Tue, Jun 2, 2009 at 15:54, ballan wrot
That is an issue when users are on slow internet connections or the target
site is really slow. Not sure that I would call it a bug... but it does need
a solution.
The http request from the auto redirect hits the target sites callback but
before html is downloaded and the browser redraws replacing
Hi Matt,
An item on http://status.twitter.com would be good – I'm now seeing
this on my oauth_callback page too.
Thanks for the response,
David.
On Jun 2, 8:30 pm, Matt Sanford wrote:
> Hi David,
>
> They shouldn't randomly disappear like that. We're busy fixing
> some database issues
Thanks Adam.
On Jun 2, 3:09 am, Adam Varga wrote:
> I reported this error
> here...http://code.google.com/p/twitter-api/issues/detail?id=639&colspec=ID%...
>
> Hopefully Twitter takes care of this soon.
>
> On Jun 1, 7:06 am, மனோஜ் (Manoj G) wrote:
>
>
>
> > I am also looking for the answer o
But how would the blocked app work out the API key for TweetDeck unless
TweetDeck makes their private API key public?
2009/6/2 Chad Etzel
>
>
--
cashflowclublondon.co.uk
("`-''-/").___..--''"`-._
`6_ 6 ) `-. ( ).`-.__.`)
Hey all,
I am re-creating a feed that that will be displayed in a custom
widget. However, the rate limit is being reached almost right away,
even though this is currently in development, and only a handful of
people would be looking at this.
I have implemented the following steps to avoid this:
Lately I've noticed once the user "Grant"s on the Twitter oAuth page,
the "Redirect" page from Twitter is showing up a little longer.
There's a typo "dosen't" on this page by the way.
The bigger problem though is that a redirect is taking place but the
browser hasn't reacted and the user has a c
Chad is correct. Until we have everyone pushed through a funnel where API
keys are required or applications can be deduced (as with OAuth) we have no
way of knowing which application actually sent an update or DM in some
cases. Furthermore, we don't have the notion of tweet level spam reporting.
Cu
No, it can't be required. Worse yet, it can be spoofed w/ basic auth,
so a "blocked" app could just change it's source parameter and appear
as something like TweetDeck.
-Chad
On Tue, Jun 2, 2009 at 3:36 PM, Developer In London
wrote:
> Couldnt the app-id be made a required parameter for the AP
Couldnt the app-id be made a required parameter for the API calls? That way
it can still work with basic auth.
2009/6/2 Doug Williams
> Floated the idea. Until we funnel everyone through OAuth (that means no
> Basic Auth) this really isn't possible. It's something we'll keep in our
> back pocket
Floated the idea. Until we funnel everyone through OAuth (that means no
Basic Auth) this really isn't possible. It's something we'll keep in our
back pockets for the long-term.
Great suggestion though, Jesse.
Cheers,
Doug
--
Doug Williams
Twitter Platform Support
http://twitter.com/dougw
On Tu
Hi David,
They shouldn't randomly disappear like that. We're busy fixing
some database issues at the moment and my guess is that is causing the
problem. Hopefully by the end of the day all of that will be sorted out.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On Jun 2, 2009
Hi there,
My application at twitdiff.appspot.com is getting finding that random
user accounts' OAuth tokens are no longer valid. I assumed that they
were revoking the application's access at Twitter.com, so I modified
the exception handler to send a mail telling them "looks like you
revoked me -
I believe there is a feature request open in the issue tracker for this. It
makes sense for much larger users that decide they want to follow their
followers.
@Jesse
On Tue, Jun 2, 2009 at 12:29 AM, kkp <33spa...@gmail.com> wrote:
>
> Hi,
>
> I want to follow/unfollow multiple users in one web r
> > Leo,This has been covered many times before. It's 140 UTF-8 characters.
> > Please search the archives of this group for the complete conversation,
>
> If you cared to read my messages, you_d have seen that they reference
> half a dozen conversations in this list, with "employee participation
Hello,
I'm sorry if this is a dumb question but I just wanted to be sure I
wasn't missing something...
Is it true that I can get data for only 100 users/hour with the "users/
show" API method?
Is there a way to get data for multiple users in one request using
"users/show"?
Is there another way I
agreed, I'd like this as well.
On May 31, 6:52 pm, Jesse Stay wrote:
> Not going to name names, but there are a few really noisy apps out there
> right now. It would be really nice if, via either the API (my preference as
> it would be less work on your part and fits well with my app), or the U
you da man!
On Jun 2, 4:35 pm, Matt Sanford wrote:
> Hi there,
>
> It looks like this went out along with a few other things
> yesterday. I'll get a fix ready to be deployed today.
>
> Thanks;
> - Matt Sanford / @mzsanford
> Twitter Dev
>
> On Jun 2, 2009, at 12:13 AM, Xim wrote:
On Jun 1, 3:16 pm, Doug Williams wrote:
> Leo,This has been covered many times before. It's 140 UTF-8 characters.
> Please search the archives of this group for the complete conversation,
If you cared to read my messages, you’d have seen that they reference
half a dozen conversations in this lis
Hi there,
We have a change ready to be deployed to help secure applications
like this. Since the change is not backward compatible I gave 7 days
notice to the list here. I'll deploy the change the beginning of next
week so you can incorporate the changes. After those changes having a
> Looks like right now IE can't be used at all to sign in with
> Twitter. I'm not just talking about oauth either. I mean I can't go
> to twitter.com in and IE8 Browser and login. The response is 403
> Forbidden: The server understood the request, but is refusing to
> fulfill it.
I don't think
Looks like right now IE can't be used at all to sign in with
Twitter. I'm not just talking about oauth either. I mean I can't go
to twitter.com in and IE8 Browser and login. The response is 403
Forbidden: The server understood the request, but is refusing to
fulfill it.
On Jun 2, 9:25 am, Matt
Hi there,
It looks like this went out along with a few other things
yesterday. I'll get a fix ready to be deployed today.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On Jun 2, 2009, at 12:13 AM, Xim wrote:
It looks like the problem in meta tag that twitter uses for client
s
You might be having the same issue as this thread:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/0929e54c4e59ba17
On Tue, Jun 2, 2009 at 08:04, nattu wrote:
>
> Hi,
>
> I currently have two source parameters which were working fine, but
> are not working anymore. I
Hi Dave,
I'll take a look at this today. There was some content versioning
changes that must have caused an issue. Hopefully we can get it fixed
again soon.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On Jun 1, 2009, at 3:49 PM, Dave wrote:
In IE https://twitter.com/oauth
That is a known caching issue.
On Mon, Jun 1, 2009 at 17:16, RC wrote:
> Can this also explain why on a few accounts I'm seeing a discrepancy
> between the number of ids in the following JSON versus what Twitter is
> showing when you see the account on the web? I have at least two
> accounts th
Hi,
I currently have two source parameters which were working fine, but
are not working anymore. I read in other threads that using OAuth will
solve the problem. Mine is a .NET application and I am using Yedda
Twitter library. If somebody can throw light on this OAuth, it would
be helpful.
Thank
http://code.google.com/p/twitter-api/issues/detail?id=580
On Tue, Jun 2, 2009 at 02:15, sandeepcec wrote:
>
> By REST API i get twitter user detail.
> url used: http://twitter.com/users/show/40741376.xml
>
> (see user profile : 40741376, name Tweetactics)
> isue:
> The followers,followers cou
I was thinking something similar but I think it would probably have to
work something like:
http://twitter.com/statuses/friends_timeline_number.format and a
since_id parameter (this would give you the number of messages since
message with that id)
#
Or for direct messages:
http://twitter.com/dir
By REST API i get twitter user detail.
url used: http://twitter.com/users/show/40741376.xml
(see user profile : 40741376, name Tweetactics)
isue:
The followers,followers count does not match
With user profile if we check from twitter site(http://twitter.com)
In some other users detail i fou
It looks like the problem in meta tag that twitter uses for client
side redirection. It misses "url=..." in
http://example.com"; />
it should be
http://example.com"; />
Guys from twitter, it would be great if you fix it ASAP.
Thanks
On 2 июн, 06:13, Dave wrote:
> Did something just change l
Bulk social graph operations sound quite spammy. Enabling such
functionality would be counter-productive. Perhaps there's a better
way to legitimately provide the same functionality?
If you need a stream of updates from a large dynamic group of users,
consider the /birddog resource in the Streami
2009/6/1 Nick Arnett :
>
>
> On Sun, May 31, 2009 at 3:57 PM, Stuart wrote:
>>
>> Much as I respect Twitter and the great people who work there, I don't
>> buy that this would place too much demand on their servers. They
>> already use Memcached extensively, and this would be a pretty simple
>> a
44 matches
Mail list logo