Hey, any chance of ever having one of these meetups in the UK?!
On Jun 7, 12:48 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Mac Devs,
This time last year we hosted an informal meetup of WWDC attendees. The
event turned into a fun evening so we've decided to do it again. We
I'm looking at home_timeline it doesn't seem like retweets are showing
up for me? Also, what type of retweets are supposed to show up in
mentions? Users that retweeted a mention of you I assume?
Neither of these things seem to be working for me. Anyone else seeing
this?
Hi,
We got XAuth approval for outr application.
We are forming the URL and posting to api.twitter.com
We are getting HTTP error 500 - Internal server error
URl detaisl are given below.
Kindly help us to resolve the issue
Signature Base String
---
Hi Taylor,
Thanks for the pointers you wrote in the previous post. I had a
recheck in my program flow based on your pointers.
I send the callback url during signing of the request itself(GET
request). I have added its as default parameter in my header all the
time.
Here's how it looks:
Any news on this issue ?
On 29 mai, 00:12, themattharris thematthar...@twitter.com wrote:
Hi Priyanka,
Thanks. We're aware of the problem and it is being tracked as ticket
1650 [1] on the twitter-api issues log.
1.http://code.google.com/p/twitter-api/issues/detail?id=1650
Matt
On May
+1
I think you make a good point. It's no extra effort to append the data
type to the name. If annotations is to become a wild west then
assuming everything is a string unless proven otherwise is a little
rediculas. It might be better to take it one step further since above
you usefloat when
Hi SlideInCode,
If you're asking for login and password on your website to invoke use of the
API, you're going to need to do some work to continue having a functional
integration after our basic authentication method departs later this month.
This kind of frictionless API integration you seem to
I'm developing an application designed to run on a public computer,
where many users will sign in with Twitter to register for our app.
I've been looking for a way to sign the user out of Twitter when they
exit the application (though a sign out button). Since we cannot
destroy the cookies set by
Hello,
How can I fetch all messages from users that use my Application?
I can fetch messages from all users, that I follow, but how can I do
it from application without user?
Thanks.
There's no super-efficient way to do this at this time. If you're trying to
track all the public tweets issued by users of your application, the
Streaming API's filter/follow features might serve some of what you're
trying to accomplish.
I have a Perl script that downloads historical tweets using the
user_timeline REST API call. I'm running into 503 - Bad Gateway -
Twitter / Over capacity errors when I run it. Questions:
1. When I run into an error, I'm waiting 45 seconds before retrying.
Should I wait longer? Is there a
Taylor,
Can you take the GET commands out of the form until they work? Will
save a lots of people some time.
Thanks,
Sharad
On May 26, 8:51 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Daniel,
There are still some bugs here and there with theAPIconsolethat we
haven't had a
Hi Avinash,
First, it's most appropriate to use a POST on the request token and access
token steps of the OAuth flow (though GET will work fine).
You might be having your issues because you are sending the oauth_token as
part of your request in the request token step. The request token step of
Hi,
What does your POST body look like in this example? Are you including *only*
the x_auth_* parameters in the POST body? Have you escaped the usernames and
passwords? If there's any escaping that must happen for a username and
password, within the signature base string, you'll have to encode
Hi EL,
Thanks for obscuring your secrets in your post.
One issue I see here is that you're providing an oauth_callback in your POST
data, but it's not included in your signature base string.
If you're using POST-based OAuth (as opposed to query string or HTTP header
based OAuth), then your
Hi Michael,
Judging by the output Curl is giving you here, it doesn't look like the
header is being set correctly on this step. The header that you're
presenting should also be comma separated on each discreet element. The
header also should not include your POST parameters (like status in this
Thanks to all your replies helped I can now perform status updates via
oAuth.
I'm rather irritated that Uri.EscapeDataString doesn't escape all
illegal characters. It just fails now if a status update contains
exclamation marks, asterisk, dollar signs, single quotes and probably
a few more. I'll
We are forming the URL and posting to api.twitter.com We are getting
HTTP error 500 - Internal server error URl detaisl are given below.
Kindly help us to resolve the issue
Signature Base String
---
POSThttps%3A%2F%2Fapi.twitter.com%2Foauth%2Faccess_token
Hi Brewbird,
What does your POST body look like in relation to this request? Since the
x_auth_* parameters are not OAuth parameters, you should be sending them in
your POST body (and no other parameters in this area).
Your POST body should look something like (order does not matter in the POST
I'm seeing a temporary error adjusting the since_id on every search
query if I specify lang=en and it wipes out many valid results. I can
tell my backend script to filter out the other languages, but I'm
seeing as many as half a page of results be foreign posts, so that's a
lot of wasted bandwidth
Getting user ids of all the members of a list is crucial for a feature
of my Twitter app, and paging through 20 ids at a time from each list
isn't feasible. (Most of the data would be extraneous, I just want the
ids.) I see a suggestion was made back in Nov 09 to implement a
function like the
Hello, I wanted to know if there is any way of knowing who was the
firstI use a hashtag? I need an analysis I'm doing twitter please can
you send me this information?
hi all.
twitter has been wrapping links in e-mailed DMs for a couple months
nowhttp://bit.ly/twttldmemail.
with that feature, we're trying to protect users against phishing and other
malicious attacks. the way that we're doing this is that any URL that comes
through in a DM gets currently wrapped
Quoting jretamal jreta...@gmail.com:
Hello, I wanted to know if there is any way of knowing who was the
firstI use a hashtag? I need an analysis I'm doing twitter please can
you send me this information?
Depending on how long ago the hashtag was created, you might be able
to determine this
Hello everyone here!
My name is Mike Stachowiak and I work with Twitter API since June
2009.
We did analytical platform for LEWIS PR using our own methodology,
algorithms.
I look forward for any business proposal and comment.
Thanks, Mike
I thnk you have to go through paging and this is only way you can
handle - we do it like this
M
On Jun 8, 11:43 pm, Unfair imunf...@yahoo.com wrote:
Getting user ids of all the members of a list is crucial for a feature
of my Twitter app, and paging through 20 ids at a time from each list
Raffi,
I'm fine with everything up to the new 140 character count.
If you count the characters *after* link wrapping, you are seriously
going to mess up my system. My short URLs are currently 18 characters
long, and they will be 18 long for quite some time to come. After that
they will be 19 for
Hi Raffi,
Interesting... A couple of quick questions:
*1)* Will the redirect from t.co - domain.com be a 301 Moved Permanently or
a 302 Found response?
*2)* Will the t.co URL redirect point to the URL in the original tweet, or
will it point to the ultimate resolved URL?
I.e., if I post Check
How will this affect links for third party services that clients
handle natively, such as Twitpic (and obviously TwitLonger, which
already has shorter dedicated short urls for its posts)?
I'll also be interested to see how this goes down with the privacy
types who will now be paranoid that
Hi Raffi,
On 9/06/10 8:57 AM, Raffi Krikorian wrote:
url : http://t.co/s9gfk2d4;,
display_url : http://dev.twitter.com;,
indices : [23, 43]
Any chance of getting the title of the resolved URL added in here too if
available?
Then we could display a link like :
a title=Twitter Dev
This is not unique to me. This will be problematic for anyone who uses
a shortening service that shortens URLs to less than 20 characters.
In these cases, you are basically adding characters to the submitted
text, and then rejecting the submitted text as being too long.
On Jun 8, 8:33 pm, Dewald
*1)* Will the redirect from t.co - domain.com be a 301 Moved Permanently
or a 302 Found response?
301!
*2)* Will the t.co URL redirect point to the URL in the original tweet, or
will it point to the ultimate resolved URL?
I.e., if I post Check out my site at http://bit.ly/abcd; where
How will this affect links for third party services that clients
handle natively, such as Twitpic (and obviously TwitLonger, which
already has shorter dedicated short urls for its posts)?
that's why we are providing all the data back out in the API. while the
tweet itself may have t.co, we
that would be an awesome service!
On Tue, Jun 8, 2010 at 4:50 PM, John Barratt djo...@gmail.com wrote:
Hi Raffi,
On 9/06/10 8:57 AM, Raffi Krikorian wrote:
url : http://t.co/s9gfk2d4;,
display_url : http://dev.twitter.com;,
indices : [23, 43]
Any chance of getting the title of the
its true, and we understand that.
just to correct my previous post, however -- t.co links are 19 characters.
On Tue, Jun 8, 2010 at 4:53 PM, Dewald Pretorius dpr...@gmail.com wrote:
This is not unique to me. This will be problematic for anyone who uses
a shortening service that shortens URLs
So what are you saying? Suck it up? That's what I am hearing.
I have a work-around for the problem, in that I can simply adjust my
in-house shortening service to start generating 19-character URLs. But
other developers don't have that option.
On Jun 8, 8:58 pm, Raffi Krikorian ra...@twitter.com
Will we be able to get matches on the original URL through the streaming
API?
For example, I'm tracking act so I can match tweets that link to '
http://act.ly'. Will I still be able to do that?
Jim Gilliam
http://act.ly/
http://twitter.com/jgilliam
On Tue, Jun 8, 2010 at 4:33 PM, Dewald
Hi all,
I am having trouble with setting favorites through the oAuth API
(with xAuth). Must other api's work (exception being blocks/exists, see
previous emails).
Here is an example request:
location: https://api.twitter.com/1/favorites/15738870223/create.json
authorizationHeader: OAuth
Awesome, thanks for the quick response!
Those are the right answers, too. : )
Though there's an inconsistency with returning 301's and also requiring
every click to go through the t.co link (as required by the ToS). A 301
means that the redirect is cacheable by any intermediary (because it is
Hi Jim,
Change the URL to
https://api.twitter.com/1/favorites/create/15738870223.json and it should
work.
On Tue, Jun 8, 2010 at 5:04 PM, Jim Cortez j...@jimcortez.com wrote:
Hi all,
I am having trouble with setting favorites through the oAuth API (with
xAuth). Must other api's work
Raffi: Never mind. I just saw the Twitter blog post. The motivation
for this is to get metrics for Promoted Tweets and Resonance. Hence,
the answer is: Suck it up.
DeWitt: Yikes, discarding all shortens between t.co and the final link
will seriously mess with the click stats of a few million
Hi Raffi,
On 9/06/10 9:57 AM, Raffi Krikorian wrote:
that would be an awesome service!
Currently we use one our own services (http://metauri.com/) to do this
for http://trendsmap.com/. In addition to the title, it also gives the
content type, which can be useful in determining how, or if to
If you do this, you will literally be forcing app developers to waste users
time and money, especially over metered GRPS/3G connections.
If the user can see the full URL, then why do they need to be protected
any more than they are when they use any other service? If anything, you
should be
+1 on this, I'd like to know the answer as well.
Damon/@dacort
On Jun 8, 4:43 pm, Jim Gilliam j...@gilliam.com wrote:
Will we be able to get matches on the original URL through the streaming
API?
For example, I'm tracking act so I can match tweets that link to
'http://act.ly'. Will I
I don't see how this feature could impact user privacy more than what
it is right now. Today Twitter stores all links for all users and they
can spy on them and the t.co shortner is not changing that :)
My question is, will developers have access to analytics from t.co
through API?
Thanks
What's the algorithm for the display url? Ideally it will be a
predictable length, to aid predictability in tweet display code.
If the motive is really to protect us from malicious URLs, what about
giving a service we can call to route links through your protective
redirect servers? Then we can
Sami wrote:
I don't see how this feature could impact user privacy more than what it
is right
now. Today Twitter stores all links for all users and they can spy on them
and the
t.co shortner is not changing that :)
Right now, Twitter can see all the links that users *post*, but they don't
see
our hope is to eventually provide this analytics.
On Tue, Jun 8, 2010 at 7:14 PM, Sami sami.ben.romdh...@gmail.com wrote:
I don't see how this feature could impact user privacy more than what
it is right now. Today Twitter stores all links for all users and they
can spy on them and the t.co
Raffi wrote:
related to this: the way the Twitter API counts characters is going to change
ever so slightly. our 140
characters is now going to be defined as 140 characters after link wrapping.
t.co links are of a
predictable length -- they will always be 20 characters. after we make this
What's the algorithm for the display url? Ideally it will be a
predictable length, to aid predictability in tweet display code.
i'm not sure why the display_url would be of predictable length? the
display_url is -exactly- the URL that the user has sent into the system.
so, that may be of
Right now, Twitter can see all the links that users *post*, but they don't
see which links users *click*.
In order to implement this feature, Twitter has already built the framework
that does all the hard work that applications need to protect users'
privacy
against (link-shortener)
yeah - its definitely case that counting characters will become a bit more
subtle. i hope that we can provide a really good and easy way to help you
all out. at the very least we are going to update documentation, but i know
we can do better than that.
On Tue, Jun 8, 2010 at 8:17 PM, Andy
I was basing my statement on the blog post, which indicated that at least
some display URLs will be truncated:
http://blog.twitter.com/2010/06/links-and-twitter-length-shouldnt.html
A really long link such as
http://www.amazon.com/Delivering-Happiness-Profits-Passion-Purpose/dp/044656
3048
Are all links going to be wrapped or only long links? If it's the
latter, what's the definition?
1. This affects how we count characters before sending and has quite a
potential to go wrong, since we'll now need to know exactly which
links are going to be wrapped in a tweet.
2. It's also going
OK, it's a little confusing naming for display URL, as that implies
that is what clients should show directly to the users, as most of the
time I would imagine that field should be cut for brevity.
The difference between having a ping service that can help twitter
track clicks and a redirect
All links will be wrapped. It's not about length.
On Tue, Jun 8, 2010 at 9:06 PM, Alex B alex.boswo...@gmail.com wrote:
OK, it's a little confusing naming for display URL, as that implies
that is what clients should show directly to the users, as most of the
time I would imagine that field
Existing url shortners will continue to work just fine. We're not
going to resolve them to their final link and remove them from the
chain.
By redirecting all links, we can protect all users and the entire
ecosystem much faster. The adoption via opt-in would be slower, and
might never reach
But if apps don't update and user sends a tweet which is just below
140 characters say, 139, and which contain a link(s) shorter than 19
(or is it 20) characters will mysteriously fail. The user will wonder
why the app doesn't let them send the tweet when their app clearly
says it's still within
On Tue, 8 Jun 2010 22:19:04 -0700 (PDT)
Hwee-Boon Yar hweeb...@gmail.com wrote:
But if apps don't update and user sends a tweet which is just below
140 characters say, 139, and which contain a link(s) shorter than 19
(or is it 20) characters will mysteriously fail. The user will wonder
why
- Privacy of click history. Your changes are such a big compromise of
privacy that I might stop using Twitter altogether and not just stop making
applications for it. (To get a feel of how seriously I take privacy of
click-history, see an old blog
60 matches
Mail list logo
