(this will become easier once we can roll out entities into the XML/JSON
payload)
On Fri, May 14, 2010 at 5:21 AM, Abraham Williams 4bra...@gmail.com wrote:
You could just do a check to see if the status contains a http:// or
https://. You might miss a few that don't include the protocol but
Hi Guys
Whilst our desktop app has been desktop OAuth-based since launch, the
media uploading has been username / password based (yfrog, twitpic
etc). With basic auth going the way of the dodo next month, I just
wanted to check to see what folks are doing for media uploads to
services that use
Yes, this would be very cool. Any ideas on when this would be rolled
out?
1) It would be nice to have the profile_image_url in it as well. I can
imagine a lot of nice visual enhancements with that.
2) +1 for making it optional. A lot of people are suggesting
additional stuff, so maybe it would
Love the idea - pretty hard to do. Want to doit. Not sure when :p
On Friday, May 14, 2010, Adam v0id@gmail.com wrote:
I'm not sure if this has been asked before, but I was wondering about
the inclusion of a read/unread field included with a status. So many
applications conduct their own
Very often illegal XML is returned by a call to
http://api.twitter.com/1/statuses/user_timeline.rss .
The value is twitter:source is not XML encoded.
E.g.
twitter:source
a href=http://www.google.com/support/youtube/bin/answer.py?
hl=enanswer=164577 rel=nofollowGoogle/a
/twitter:source
It
Wouldn't that be something for the upcoming Annotations?
Ole
--
Jan Ole Suhr
s...@mobileways.de
On Twitter: http://twitter.com/janole
On 14 Mai, 12:45, Raffi Krikorian ra...@twitter.com wrote:
Love the idea - pretty hard to do. Want to doit. Not sure when :p
On Friday, May 14, 2010, Adam
Hi,
I am developing an application where i want to get twitter updates
(follow-ups, tweets etc.) based on keywords straightaway into my
application. I am using twitter4j for that purpose. The problem is
that the search results are quite outdated as compared to the ones
gotten through twitter
+1 for making this optional.
It's faster for mobile apps to do this themselves than download it.
Besides, if this is the library used for web, you're not doing it
right. :)
For example, to mention URL parsing only, you don't check for valid
domain names (e.g. www.test.failure is matched as URL),
People, help me out with this one.
I'm twitting about CATS and DOGS. I have followers who are interested
about CATS or DOGS, but not both. How do I send my tweets about cats
to only those followers who needs to know about cats, and send the
dogs updates only to the subscribers interested in dogs?
Besides, if this is the library used for web, you're not doing it
right. :)
For example, to mention URL parsing only, you don't check for valid
domain names (e.g. www.test.failure is matched as URL),
some characters are not recognized as part of a link (e.g. | in
annotations are immutable along with the tweet. you create annotations when
you create a tweet, and they are stored with that tweet.
On Fri, May 14, 2010 at 12:37 PM, janole s...@mobileways.de wrote:
Wouldn't that be something for the upcoming Annotations?
Ole
--
Jan Ole Suhr
Results from the Search API should be delayed only by a few seconds
during normal operations. If there's some operational issue, search
can get behind, but this should be fairly rare.
The lowest latency API is the Streaming API. Results are often
available here before they are published onto
Read-until is naturally stored with, or in relation-to, the User
object. Due to temporary infrastructure limitations, that is database
issues, it's not really feasible to add additional high-velocity
columns on Users for a little while. Once this limitation is sorted
out, the Platform team can do
I understand. And I don't have anything against it (even if it will be
default), as long as it will be optional.
And we're all appreciating the library (and its Java implementation:
http://github.com/mzsanford/twitter-text-java).
On May 14, 3:47 pm, Raffi Krikorian ra...@twitter.com wrote:
all
Use since and until parameters to specify the time period
for which you would like to see the results. For each day you can
retrieve a maximum of 1500 tweets per search term.
On Fri, May 14, 2010 at 11:48 AM, Amit saksena...@gmail.com wrote:
Hi,
I am developing an application where i want to
+1 for it being optional as well -- keep the bandwidth to a minimum
for scenarios where it's not needed.
+1 for having short URLs' original (long) URL provided (perhaps also
an option?)
Disambiguating short URLs and delivering the true URL and title would
be a real plus, not just for developers, but for the target of a URL.
While it does add a load to twitter's servers, it will save many, many
useless hits to the target.
Imagine 100,000 Twitter apps resolving each short URL
Ahh I see. Yeah, didn't think about it like that. Thanks for the reply.
Maybe in the future eh?
Adam
On Fri, May 14, 2010 at 9:54 PM, John Kalucki j...@twitter.com wrote:
Read-until is naturally stored with, or in relation-to, the User
object. Due to temporary infrastructure limitations, that
Raffi,
A bit advanced request. Would it be possible to attach list of
significant words and phrases present in the tweet. We could then use
this info to categorize tweets and even build a trends list on the
tweets aggregated by our apps.
In one of our apps, we use Yahoo Terms Extraction service
Hi Miles,
You're right in that we don't go back very far with search right now. We
want to improve that. There's no timeline right now, but it's certainly
something we're looking at. There are so many tweets. We want you to have
them all. Some day.
Taylor Singletary
Developer Advocate, Twitter
Hi,
I am trying to use a callback URL with my desktop client. Twitter
added twittia://oauth_token/ as my callback url but when I try to use
it and open the
http://twitter.com/oauth/authorize?oauth_token=mDu9cZQBVCm0yrZufUAKujduyIxl7OoFwAlEM3q7rg
resource in the browser, the user authorizes the
Hi Jeena,
I'll investigate this and let you know what I figure out.
Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod
On Fri, May 14, 2010 at 9:09 AM, Jeena jeenaparad...@gmail.com wrote:
Hi,
I am trying to use a callback URL with my desktop client. Twitter
added
If this thread is a duplicate, feel free to point me to the correct
thread.
I found some documentation that isn't correct.
On http://dev.twitter.com/doc/post/favorites/:id/create the
documentation state that you should send a post to
https://api.twitter.com/1/favorites/insert-id/create.json, but
Ok great, looking forward to it.
On May 14, 6:19 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Jeena,
I'll investigate this and let you know what I figure out.
Taylor Singletary
Developer Advocate, Twitterhttp://twitter.com/episod
On Fri, May 14, 2010 at 9:09 AM, Jeena
Hi Tijs,
I'm actually working on these errors now. It's more of a systematic thing
than anything -- quirks. When in doubt, the API wiki is still up and running
and can give clarity until the plumbing on this is fixed.
Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod
On
Thanks. As I note, that is a non-trivial project/barrier.
FWIW, I'm putting together a generic service for this application,
where a user can oAuth to the site and then create proxy credentials
that can be used to tweet etc.
http://www.supertweet.net/
Feedback welcome.
On May 12, 7:35 am, John
Hi Glenn,
FWIW, the application and platform is extremely small and lightweight
- there is nothing as powerful or huge as 'curl' there. It is all raw
C code, stripped down libraries, etc. measured in K-bytes, not
Megabytes, to say nothing of Gigabytes.
For example, the current 'tweet' code
SOLVED!
The moral of the story is to keep your nonce values SIMPLE.
We were generating a random value:
Base64.encode('1:' + counter++ + ':' + random + Date.now());
which most of the time resulted in a string that contained an equals
sign character, which then gets urlencoded to %3D.
It
Mr Blog wrote:
For example, the current 'tweet' code binary is 18K bytes. If you can add
oAuth
in 100K bytes or less, that might work, but that one function would then
still be
bigger than the entire rest of the application. In fact, the entire file
system ROM
image, with all the binaries
I have an application that executes the statuses/retweets_of_me.format
api method. The call works just fine and my app receives the retweets.
But the user section of the statuses returned contains the original
tweeter not of the user that posted the retweet. I can use the status
id in another call
Hello,
I have seen this a few times in the last couple of days and did
not see it mentioned on the list. If it is a duplicate report I
apologize.
A simple search is on a keyword, the first result does not contain the
keyword at all, here is a screen shot displaying the behavior on
Naveen,
I saw a case with one of my searches this morning where a bit.ly url
appeared to have been expanded before Twitter Search matched on the
tweet. Tim Haines said this morning on Twitter he had seen something
similar.
So, for the first tweet:
$ curl -I http://bit.ly/cMsa7U;
HTTP/1.1 301
I'm trying to implement the following in Ruby:
http://dev.twitter.com/pages/oauth_single_token
Unfortunately I'm receiving 401's from to Twitter usernames, harvest
and harvest_test. Both have been set up with an OAuth key and secret.
I'm essentially using the identical code to your sample. I
On May 15, 12:41 am, kuhkatz kuhk...@googlemail.com wrote:
so i suppose i am doing things wrong.
i followed your instructions, but when i apply the diff, i get this:
$ patch -i twurldiff
Close. You can do either one of
patch -p 1 -i twurldiff
or
git apply twurldiff
Faried.
Yes, we do match parts of the expanded URL on searches. That currently
includes query parameters, but we'll be removing that soon.
On May 14, 1:35 pm, Damon Clinkscales sca...@pobox.com wrote:
Naveen,
I saw a case with one of my searches this morning where a bit.ly url
appeared to have been
http://dev.twitter.com/doc/get/statuses/mentions
This API doesn't take a parameter for a username so it's only
available via an auth call.
We tried to hit http://api.twitter.com/1/statuses/mentions.json via
Hurl.it and got a 401.
Which means that the doc is wrong wrt auth URL.
--dwf
Hello,
I am implementing an auto login feature in my web application. What I
want to do is detect the presence of twitter. If it is present
(open) then I want to do an auto-login which will send a callback to
my server to initiate the login.
What I want to know is: How can I detect the
I have an app using OAuth (actaully xAuth) and it is working well...
or almost well.
I had a few bugs with encoding, I was not using UTF8 and now I do, so
I am able to tweet stauff like Peñarol á é í ó ú (spanish lang
characters). I was making some tests and I noticed that if I want to
set '!' as
We've been running Oauth Twitter redirect to our site for months now
(www.society.me). All of the sudden the sign in page won't redirect
back to our URL. It works with a different product we offer
(different domain). Has anyone else seen this bug? The app works
fine otherwise (people who
Hi Leonard,
Are you explicitly setting your oauth_callback in the request_token
step or are you relying on a callback pre-registered in your
application record on Twitter?
In either case, what's the value set to when it fails? What happens on
the failed redirect?
We haven't changed code in this
Will fix, thanks.
On Friday, May 14, 2010, DWF dwfr...@pivotallabs.com wrote:
http://dev.twitter.com/doc/get/statuses/mentions
This API doesn't take a parameter for a username so it's only
available via an auth call.
We tried to hit http://api.twitter.com/1/statuses/mentions.json via
I just came across a coworker's browser that triggered an alert() call
from anywhere.js. While okay for development, the use of alert() is
not friendly for production websites. Could these be converted
console.log() or some other benign mechanism?
Grepping through anywhere.js I found two
Both of which are issues that will pretty much stop @Anywhere from working
and need to be noticed as soon as possible at installation. Hiding them in
console.log will make it more likely that @Anywhere will be installe
improperly and the admins will only find out when users complain.
Abraham
On
I'm working on a Japanese twitter app and have had similar challenges with
encoding (i.e. the OAuth lib I used didnt support Japanese). I'll have a bit
of a look and see if I have the same ! problem as you and let you know.
Adam
On Sat, May 15, 2010 at 7:22 AM, @sebagomez
Hi, Faried -
I tried it too, since I have Linux 10.04, and it also has a problem at
the patching part, even provided your two ways to execute the diff.
I'm also new to Ruby stuff.
$ patch -i twurldiff
patching file Rakefile
Hunk #1 FAILED at 2.
Hunk #2 FAILED at 69.
2 out of 2 hunks FAILED --
45 matches
Mail list logo
