Some of you may be familiar with my Twitter Source Stats project:
http://funkatron.com/tss/
I've recently added the ability to get the ranking data back as JSON.
You can just add ".json" to the end of the URL, and it'll spit it
out.
For example:
http://funkatron.com/tss/lasthour
http://funkatro
+1 to DMs being a stream, and splitting send/received not making much
sense, neither globally nor in one contact context. I treat them as
sort of a single meta-call in my app, consisting of two sub-calls, and
this seems to be general behavior in all apps and also matches user
model.
J
On Apr 23
A fine answer, but does not answer the question ;) looks like you guys
are injecting custom images after some hashtags on the site?
J
On Apr 23, 10:20 pm, Raffi Krikorian wrote:
> http://hope140.org/endmalaria
>
>
>
>
>
> On Fri, Apr 23, 2010 at 2:54 PM, John Meyer wrote:
> > On 4/23/2010 3:4
Without more details this is going to be really hard to troubleshoot.
Can you reliably reproduce this? What are the exact URIs you're
calling that return 500s? What user are you using to make these
calls? What authentication method?
---Mark
http://twitter.com/mccv
On Sat, Apr 24, 2010 at
Is there any kind of special involvement needed from you every time
someone wants to do OAuth Echo? I thought I'll make my own server for
my own app for some purpose. Judging by the spec you posted on your
blog a while ago (http://mehack.com/oauth-echo-delegation-in-identity-
verificatio), it does
At this point, all I'm looking for is a way to upgrade this piece of
PHP code to take into account the new authentication model:
$ch = curl_init('http://twitter.com/statuses/update.xml');
curl_setopt($ch, CURLOPT_CONNECTTIMEOUT, 10);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, C
I am having an issue with users/show API request as well today. I am
repeatedly getting an xml error that I have exceeded the rate limit
even though I have tried it a few times per hour.
On Apr 24, 8:35 am, Dossy Shiobara wrote:
> I've been seeing an unusually high volume of HTTP 500 errors in re
Sounds similar to an issue with normal OAuth.
1) Not signed into Twitter visit http://twitteroauth.labs.poseurtech.com/.
2) Click on "Sign in with Twitter" but don't click "Sign in" once you are on
twitter.com.
3) Open a new tab to twitter.com and sign in. You will end up back at
http://twitteroau
Awesome! I'm going to start planning a party... :-P
Abraham
On Sat, Apr 24, 2010 at 08:40, Raffi Krikorian wrote:
> hi all.
>
> you're going to be hearing a lot from me over the next 9 weeks. our plan
> is to turn off basic authorization on the API by june 30, 2010 -- developers
> will have to
first three are taken care of, just let me know if you need help
coordinating with the others
On Sat, Apr 24, 2010 at 4:34 PM, John Meyer wrote:
> On 4/24/2010 5:05 PM, Raffi Krikorian wrote:
>
>> if there any applications / service providers that you would like the
>> @twitterapi team to ta
On 4/24/2010 5:05 PM, Raffi Krikorian wrote:
if there any applications / service providers that you would like the
@twitterapi team to talk to - let me know. or, have the application /
service provider come to us.
i really want to make this transition as easy as possible.
I'll probably be co
You bet.
I have created three twitter apps for imby. The production twitter
app is in the @imby twitter account. The staging and development
twitter apps are within the @imbyTest twitter account. That account
is private, so people don't see all the test tweets and whatnot.
Development, Staging
if there any applications / service providers that you would like the
@twitterapi team to talk to - let me know. or, have the application /
service provider come to us.
i really want to make this transition as easy as possible.
On Sat, Apr 24, 2010 at 3:57 PM, John Meyer wrote:
> On 4/24/2010
On 4/24/2010 3:44 PM, Raffi Krikorian wrote:
hi tom!
i will be sending more info about it - we've been working with yfrog,
tweetphoto, and twitpic to get their services migrated - they are either
finished or are nearly there. if there are others that you would like
the @twitterapi team involved
hi tom!
i will be sending more info about it - we've been working with yfrog,
tweetphoto, and twitpic to get their services migrated - they are either
finished or are nearly there. if there are others that you would like the
@twitterapi team involved with to help them get migrated over as well, t
I am having a ton of problems with that as well (500s). Actually, I
think mine is with respect to friends and followers.
Code has not done anything useful since last night :-(.
Ryan
On Apr 24, 8:35 am, Dossy Shiobara wrote:
> I've been seeing an unusually high volume of HTTP 500 errors in respon
People,
I have been struggling over the two methods -
Update Profile Image and Update Background Image
I am using EpiTwitter library.
I am uploading GIFs, Twitter returns the expected result for
update_profile_background_image but returns 401 for
update_profile_image
, but the image is not chang
> It would seem that xAuth would be the best method to use as I spent
> the last 2 days looking at ways to use oAuth the web way. I'm not if
> its entirely possible to do a round-trip in the browser window itself
> and pass authorization back to a dialog window that uses XUL.
Why not simply regis
Hi Raffi,
Great that we've got a date for basic auth deprecation, but is there any
news/timescales on OAuth Echo? We've got nine weeks and counting to get the
spec, get the service providers to implement it, build it into clients and
get our user-bases to upgrade if they want to be able to upload
Hi Taylor and Raffi,
My apologies as I think I was a bit vague and unclear.
Here's our current process:
- User right clicks in Firefox to share.
- Chrome dialog window is shown where user enters twitter credentials,
message and tags.
- Submit is form posted to server api which includes a number o
Hi,
Just started noticing something really weird. I have registered an
@anywhere app. Now whenever I log into Twitter.com, I'm redirected to
the callback url in the app with the following appended to the url:
#?oauth_error_reason=not_authed
But just to clarify, I can almost 100% reproduce this
there is a really good chance - now that oauth 2.0 has been submitted as a
draft http://tools.ietf.org/html/draft-hammer-oauth2-00, we are going to
spend some time catching up our oauth 2.0 implementation. at that point,
we'll evaluate letting it loose.
On Sat, Apr 24, 2010 at 8:44 AM, Dewald Pre
Raffi, that is super awesome. Thank you.
Any chance that you will have OAuth 2.0 in production before then?
On Apr 24, 12:40 pm, Raffi Krikorian wrote:
> hi all.
>
> you're going to be hearing a lot from me over the next 9 weeks. our plan is
> to turn off basic authorization on the API by june
sorry! i was just reminded about a point of clarification - streaming API
will still support basic auth. this note *only* pertains to the REST API.
hi all.
>
> you're going to be hearing a lot from me over the next 9 weeks. our plan
> is to turn off basic authorization on the API by june 30, 20
hi all.
you're going to be hearing a lot from me over the next 9 weeks. our plan is
to turn off basic authorization on the API by june 30, 2010 -- developers
will have to switch over to OAuth by that time. between now and then, there
will be a *lot* of information coming along with tips on how t
I've been seeing an unusually high volume of HTTP 500 errors in response
to /users/show API requests today. The availability/status page for it
shows 100% uptime --
http://status.watchmouse.com/7617/127215/users/show
Is this only affecting my requests? Is the status availability service
at Watc
The curl man page explains how to send multiple parameters. If you
just put them in one file, curl runs then all together. You have to
separate them with &, or have curl do it for you by specifying
multiple -d @ pairs:
adrift.local:/tmp> head foo bar
==> foo <==
follow=1234
==> bar <==
track=nort
Thanks a lot!
On Fri, Apr 23, 2010 at 9:49 AM, philip crawford wrote:
> Get the 2 relevant lists from the server, then perform the array
> comparison locally.
>
> Friends
> http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-friends%C2%A0ids
>
> Followers
> http://apiwiki.twitter.com/Twitte
hi matt.
it seems like you are asking about two things here.
1. the status IDs on the public timeline have zeros on the end -- that's
because we have a really simple algorithm picking statuses that go into the
public_timeline
2. between subsequent calls to the public timeline, even after the cac
I'm trying to request the user timeline for a specified user, and I
keep getting Invalid / used nonce errors in the response. I know my
nonce is correct so it must be a catch-all error message for something
else that's going on. The error only happens with some users, others
work perfectly file.
H
I am in the process of implementing a Tweet Box into some of our web
pages using @Anywhere and while we have gotten everything to work
perfectly there is one annoying problem we can't seem to fix and I'm
wondering if any of you have come up with a solution.
When we choose to connect with Twitter
Dear Sirs,
Hello! My name is Xiaowen, I have been playing with Twitter for some
time and I am writing to ask a small question regarding Streaming
API :)
>From the documentation I know we can use the command "curl -d
@locations http://stream.twitter.com/1/statuses/filter.json -
uAnyTwitterUser:Pas
I posted this issue a couple of days ago when I noticed my logs
reporting duplicate status IDs from the public timeline. I haven't
heard back from Twitter support, so I wanted to post another message
out there. Perhaps someone else is experiencing this issue.
I checked and it looks like around 8
Patrick, thank you very much for your help.
You rock !
:-)
On Apr 24, 10:41 am, Patrick Kennedy wrote:
> I also use epiTwitter. Using 'localhost' has worked for me, but
> sometimes it breaks, and I now prefer 127.0.0.1.
>
> As you note: after successful authentication with Twitter, it works
> fi
34 matches
Mail list logo
