There's actually an issue in the issue tracker on this:
http://code.google.com/p/twitter-api/issues/detail?id=1348
On Jan 29, 7:29 pm, Abraham Williams 4bra...@gmail.com wrote:
The location of statuses are often times a best approximation. You should
probably do some validation/cleanup
Hello everybody!
I want to develop twitter client for a special system, but there's a
problem - this system don't have a web browser.
Does that mean that I can't use OAuth for authentication in my app?
Some project (like dabr) put key and secret in config files.
But I think it really suck for users who want to use my client with
OAuth. Because they have to get a pair of key/secret and do configure
themselves, and the this is not convenience for users.
So I doubt that is it a good way to use
Oh, thanks, Abraham! That's great!
But why isn't it documented anywhere?
And is there any way to redirect to some status of this user?
I mean smth like
http://twitter.com/account/redirect_by_id?id=9436992status=3
???
Thanks once more,
Ivan.
On Fri, Jan 29, 2010 at 11:37 PM, Abraham
There does not appear to be. You could open an feature request and maybe
Twitter will augment it http://code.google.com/p/twitter-api/issues/entry.
Abraham
On Sat, Jan 30, 2010 at 02:06, Ivan Glushkov gli.w...@gmail.com wrote:
Oh, thanks, Abraham! That's great!
But why isn't it documented
we currently have a PIN based workflow for this purpose -
http://apiwiki.twitter.com/Authentication
On Fri, Jan 29, 2010 at 11:21 PM, popoffka popof...@gmail.com wrote:
Hello everybody!
I want to develop twitter client for a special system, but there's a
problem - this system don't have a web
what i would do is just make it clear to people who are using your open
source client that they need to register their downloaded application with
Twitter -- send them to http://twitter.com/apps/new, instruct them to fill
out the form, and build a simple wizard that they can cut and paste the
Lets collect an awesome list of tools and applications we use to help
develop with the Twitter API.
I'll start the list with a couple that I use:
Charles Proxy - @charlesproxy http://twitter.com/charlesproxy -
http://www.charlesproxy.com/
Charles is an HTTP proxy / HTTP monitor / Reverse Proxy
Curl - http://curl.haxx.se/
A command line tool for making HTTP requests. Handy for testing out
the API w/o any coding.
Tweepy - http://github.com/joshthecoder/tweepy/
A Python library that supports the entire REST API, OAuth, and Streaming API.
MIT licensed.
I do most of my Twitter API development in Perl, with some of it in
Ruby. I use Komodo IDE for that.
http://www.activestate.com/komodo/
The Perl Net::Twitter library:
http://search.cpan.org/dist/Net-Twitter/
The Ruby tweetstream gem:
Hello,
I have discovered that the search methods search and trends seem to
work okay with the domain api.twitter.com.
But the methods trends/current, trends/daily, and trends/weekly return
401's. They only appear to work correctly
on the search.twitter.com.
I have opened an issue here [1]. Will
I assume you have 2 versions:
1) the opensource code that developers can use and modify. You would not
include your consumer key/secret and have instructions on how to get their
own. Although you could include your consumer values as defaults and get
free publicity from any projects that don't
You should be using search.twitter.com for all search API calls.
On Jan 30, 2:05 pm, Josh Roesslein jroessl...@gmail.com wrote:
Hello,
I have discovered that the search methods search and trends seem to
work okay with the domain api.twitter.com.
But the methods trends/current, trends/daily,
Not to be a complete pill, but that is a terrible, terrible initial
experience for the average desktop app user. There is no way I would
or could reasonably ask one of my users to register an app themselves,
then fill in obscure hashes.
The OAuth secret is simply impossible to use securely with
I suppose the only other way to make the UX good and to keep the consumer secret
absolutely hidden is to proxy all requests through a hosted server.
This does come as a cost
of having to pay for a server to perform the proxy work. But it's
really the only option
at the moment I can think of that's
Argh!
I opened such a feature request late last November AND you commented
on it late last December.
See http://code.google.com/p/twitter-api/issues/detail?id=1242 .
On Jan 30, 11:17 am, Abraham Williams 4bra...@gmail.com wrote:
There does not appear to be. You could open an feature request
Except that the largest culprit of these (not going to name names) doesn't
use OAuth.
On Fri, Jan 29, 2010 at 8:25 PM, Kevin Marshall falico...@gmail.com wrote:
Also check what apps you've granted access to:
https://twitter.com/account/connections
and remove any that you no longer want to
You could do this internally in your application, using statuses/show to
make sure you have the correct user info before redirecting.
-- ivey
On Sat, Jan 30, 2010 at 4:06 AM, Ivan Glushkov gli.w...@gmail.com wrote:
Oh, thanks, Abraham! That's great!
But why isn't it documented anywhere?
OAuth as-is just wasn't designed for desktop apps, period. Square peg,
round hole. If Twitter is insisting on it, I'd rather this was
portrayed as a trade-off for increased user security, than a solvable
problem -- I don't think it is.
+1
--
personal:
Why not check for the presence of the keys on start-up, if they are missing
re-direct the user (open a browser window) to the new apps page and/or a
step-by-step guide on you site. then store the keys as normal
Sent using BlackBerry® from Orange
-Original Message-
From: Raffi
Thanks a lot, Abraham!
I've created it.
http://code.google.com/p/twitter-api/issues/detail?id=1412
Ivan.
On Sat, Jan 30, 2010 at 10:17 PM, Abraham Williams 4bra...@gmail.com wrote:
There does not appear to be. You could open an feature request and maybe
Twitter will augment it
So, in simple language: Twitter's policy is that every user of every open
source client register as a new twitter application?
Or, have I misinterpreted something? And if so, could you explain further what
mean?
Thanks,
Isaiah
what i would do is just make it clear to people who are using
TwitterVB - a .net framework for twitter and
PHP - custom written code to pull the public time line and users timelimes
Sent using BlackBerry® from Orange
-Original Message-
From: M. Edward (Ed) Borasky zzn...@gmail.com
Date: Sat, 30 Jan 2010 13:17:09
To:
Well, I use python to write my application. Although I can distribute
it with '.pyo' files which only contain bytecode, it's really not hard
to obtain the key/secret for a end user. Decompiling is always able
to succeed for the people who want to discover the secrets in the
program. Yes you are
I have considered this matter. But to use a proxy handle all request
is not my intention... I will go to write a online version if i have
to do that :D.
What I want to know is that: in my distributed version, should I
include the key/secret in the config file(or hardcode in source, it
doesn't
I'm a novice programmer. I found this statement to be confusing
Applications must have a meaningful and unique User Agent when using
this method. A HTTP Referrer is expected but not required. I would
like to not run into any limits even though my app is fairly small.
How does one set this
Actually i can't.
For example, i get some link like
http://twitter.com/AAA/statuses/11, for the message that was
posted month ago. I can't be sure if the current user AAA has the same
guid as the AAA month ago.
If i had the link like http://twitter.com/redirect?id=111status=222 i
would be sure
27 matches
Mail list logo
