curl "http://search.twitter.com/search.atom?q=test%20filter%3Alinks
%20(yfrog)"
returns no results and there are only 3 results on the search page for
the same query:
http://search.twitter.com/search?q=http+filter%3Alinks+%28yfrog%29
--
Twitter developer documentation and resources: http://dev.
See
http://code.google.com/p/oauth-python-twitter/source/browse/trunk/oauthtwitter.p
y?r=6 which extends python-twitter to include OAuth calls. I added a
method at a fork at http://github.com/hboon/oauthtwitter/ to include
the XAuth token exchange call.
--
Hwee-Boon
On Jun 13, 10:39 am, pythonis
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 14
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 to
Since it's GET works and POST, no. 1 reason is to make sure the base
URI in the base signature string is constructed correctly. In your
example, you don't need source= since it's OAuth.
--
Hwee-Boon
On Jun 6, 8:56 pm, rhysmeister wrote:
> Hi All,
>
> I am having problems identifying what is
I get my list from http://search.twitter.com/advanced.
--
Hwee-Boon
On Jun 3, 10:21 am, Bess wrote:
> I'd like to confirm the list of language support on Search API b/c I
> couldn't find any documentation in this Google group
> andhttp://dev.twitter.com.
>
> From my online search developers say
So, does this mean (to paraphrase):
IDs will remain sorted *all* the time except when comparing between 2
tweets sent within 1 second apart, the order *might* be reversed. And
therefore, for most Twitter apps, no change is necessary?
--
Hwee-Boon
On Jun 2, 10:00 am, themattharris wrote:
> Hey e
This is probably so obvious I'm missing it. How do I delete a retweet?
the process at the lower half
> ofhttp://twitter.zendesk.com/entries/18367and our Policy team will be
> happy to help you with this. If not, please follow up on your ticket
> (for privacy reasons) and we'll look into it further.
>
> Thanks!
> Brian Sutorius
>
> On May
My Twitter app runs on iPhone (and has a server side component that
user doesn't directly interact with). It has been running on Basic
Auth for more than a year. I would like to register it as OAuth and
migrated users over, i.e. running both in parallel under end June
since not everyone will update
Is there a reasonable replacement to provide the same functionality in
mobile apps?
--
Hwee-Boon
On Mar 5, 12:04 am, Raffi Krikorian wrote:
> sorry - its being deprecated as of today. it is being removed on 5 april
> 2010. hope that clears up the confusion.
>
> On Thu, Mar 4, 2010 at 6:54 AM,
Thanks. Hope it's not official. I don't remember reading anything like
that on the 2 lists.
--
Hwee-Boon
On Jan 18, 7:01 pm, Rich wrote:
> Ryan Sarver said it last last
> yearhttp://twitter.com/Scobleizer/status/6493268213
>
> On Jan 17, 4:46 am, Hwee-Boon Yar wrote:
>
On Jan 14, 8:30 am, twittme_mobi wrote:
> Hello ,
>
> Regarding Basic Auth Deprecation is June
Any where this is announced?
--
Hwee-Boon
This is search results for JSON and Atom call, 10 minutes after the
tweet was sent (timestamp 2009-12-05T03:38:11Z). 0 results for JSON, 1
result for Atom
JSON
===
0 results:
$ curl "http://search.twitter.com/search.json?
q=to:Smoothe_1&since_id=6357863332"
{"results":[],"max_id":6358271161,"sin
I tried searching against http://search.twitter.com and the ATOM
search API and found that retweets created using the API appears as
plain text in search results, with no metadata referring to the
original tweet. Is this the expected behavoir? If so, any plans to
make it consistent?
--
Hwee-Boon
I did an experiment.
user1 tweets update1
user2 retweets update1 as update2 (a RT, with update1 embedded)
user3 retweets update2, the embedded update is update1 instead of
update2.
I can't find documentation on this. Is this the expected behavoir?
--
Hwee-Boon
(S)omeone blocks (Y)ou.
Web
===
If you are logged in as Y and go to http://twitter.com/S, you get no
indication that you are blocked, being able to view S's timeline, etc.
API
===
When accessing S's timeline using /statuses/user_timeline/S.xml
authenticated as Y, however, you get a 401/Not Author
Like I have mentioned privately to someone:
"Can I then make a next best suggestion that is most easy to implement
and yet effective? It has been suggested more than once. Post an
update to status.twitter.com. Even a short message. Give us something
to retweet, to forward to users. If you want to
On Oct 22, 12:05 am, RandyC wrote:
> I'm surprised more people aren't talking
> about this unless we're the only ones affected.
Me too. Which is why I'm posting it here. No one else seems to be
complaining. I was beginning to wonder I was alone.
--
Hwee-Boon
ch is about the same I'm getting locally.
>
> Are all API endpoints slow for you or just a select few?
>
> Josh
>
>
>
> On Wed, Oct 21, 2009 at 10:53 AM, Hwee-Boon Yar wrote:
>
> > I have been having these very slow API response running on Slicehost
> > (m
I have been having these very slow API response running on Slicehost
(most of the time way more than 2-3 seconds) for the past 2 days. Is
this something being actively worked on?
It's becoming really painful that people are telling me my app doesn't
work.
--
Hwee-Boon
I've observed the same behavoir at least 10 hours ago and still seeing
it now.
--
Hwee-Boon
On Oct 21, 3:57 am, TjL wrote:
> On Tue, Oct 20, 2009 at 2:11 PM, Michael Ivey wrote:
> > As an aside; please don't bump threads on this list.
>
> As an aside, how about someone answers the question rat
ps.google.com/group/twitter-development-talk/browse_thread...
>
> Let me know if this helps.
>
> Leon
>
> ________
> From: Hwee-Boon Yar
> To: Twitter Development Talk
> Sent: Mon, October 19, 2009 4:30:42 AM
> Subject: [twitter-dev] Re: XML AP
Which one?
On Oct 19, 5:40 pm, Leon Spencer wrote:
> Hi.
>
> I think there is a similar post in the discussion. A Twitter support person
> appears to have responded directly to it.
>
> Leon
>
> ________
> From: Hwee-Boon Yar
> To: Twitter
I'm reposting a support email I sent to API support to see if anyone
else is facing the same issue:
1. Some users of SimplyTweet (iPhone app) are receiving old versions
of the DM timeline.
2. On a related note, I seem to be having the same issue with
SimplyTweet's servers (for push notification s
On Sep 24, 2:16 pm, Josh Roesslein wrote:
> This could be done by just
> posting a second
> tweet with the reply parameter pointing at the retweet.
With the current way RT works (without the RT API) and at least as of
a month ago, making RTs a reply makes it limited to people who follow
both the
Along the same line, updates from accounts considered spamming
wouldn't be included in search results too.
--
Hwee-Boon
On Sep 17, 12:07 am, JDG wrote:
> I believe that search does not return statuses of protected users (even when
> authenticated, though I may be wrong and should be corrected i
Nicholas Moline wrote:
> >> >> > And nobody thought about the significance of accelerating anything
> >> >> > called a *pocolypse to be on the anniversary of a date that thousands
> >> >> > died in a terrorist attack Tactful Tw
May I know when and where was it mentioned that it will be
artificially increased this coming Friday?
--
Hwee-Boon
On Sep 10, 2:49 am, Alex Payne wrote:
> As mentioned previously, the Twitter operations team willartificially
> increase the maximum status ID to 4294967296 this coming Friday,
> S
I filed this a few weeks ago and the ticket wasn't commented on nor
discussed here, so I replicate it here to bring some attention to it.
It's an obscure bug:
==
Calls to account/update_profile API fails if the original screen name
(the one that was signed up with, eg. "User1", inste
Is favoriting broken?
--
Hwee-Boon
Can you confirm if OAuth access is the only known issue? I feel silly
repeating the same question over and over again: "Even /
rate_limit_status calls are timing out on my server. I have no API
access *at all*".
--
Hwee-Boon
On Aug 17, 5:21 am, Chad Etzel wrote:
> We've asked the keeper-o-the-
> The API team is actively debugging the OAuth issues as we speak.
This is what worries very much.
I can't even do this without timing out:
curl "http://twitter.com/account/rate_limit_status.xml?
screen_name=hboon"
I have no API access *at all*.
--
Hwee-Boon
I was trying to be patient with this, but seeing that no one is
complaining, I'm afraid I might be alone here.
One of SimplyTweet's server had not been able to access the API *at
all*. Even /rate_limit_status (nothing to do with OAuth) timeout every
time. Is this expected? No response when I twee
Isn't this what I said?
--
Hwee-Boon
On Jul 24, 2:36 pm, srikanth reddy wrote:
> @jim.renkel. Thanks a ton. I think now it is clear.
>
> < requests per hour, independent of any other users of that site or *any
> other uses of the twitter API at other sites by that user *>>
>
> probably this is
It's working like you want it to be.
In other words, you have a web app running on a single server with a
single IP. You make authenticated requests using each user's account.
If your IP is whitelisted, the calls go towards your 20k limit, if it
is not whitelisted, it goes against the current 150
Oh god. Please share where is this twitter-announce list?
--
Hwee-Boon
On May 10, 12:51 pm, Jesse Stay wrote:
> Not to be picky, but can we get these announcements on the twitter-announce
> list in the future? Who is this John and is he a real Twitter employee?
>
>
>
> On Sat, May 9, 2009 at 10
Hmm.. when did the Streaming API come about? I see Firehose mentioned
in there, OK that's known. What's Spritzer? (I read the description
and tested it).
-
Hwee-Boon
On May 8, 12:39 am, John Kalucki wrote:
> Matt,
>
> As Doug mentioned, we're working on fixing the public timeline. I hope
> we c
wget http://id:passw...@twitter.com/direct_messages.xml?count=15
grep " | wc -l
prints 9.
Ditto for other numbers.
--
Hwee-Boon
This:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/bba8bbd5176fbb24/4a9cb5d5780da976?hl=en&lnk=gst&q=following+hwee+boon#4a9cb5d5780da976
and http://code.google.com/p/twitter-api/issues/detail?id=157.
Supposed to be fixed? (I haven't verified. I stopped relying on i
.http://code.google.com/p/twitter-api/issues/detail?id=99
>
> Doug Williams
> Twitter API Supporthttp://twitter.com/dougw
>
> On Fri, Mar 20, 2009 at 11:54 AM, Pleasant Software <
>
>
>
> pleasantsoftw...@googlemail.com> wrote:
>
> > Same problem here. I g
So if I do, http://twitter.com/users/show/XXX.xml
What does the value of following (true/false) mean? I tried
authenticating as someone that both follows and is followed by XXX and
yet the value of following is still false.
Docs say: boolean indicating if a user is following a given user
Any th
If that's the problem you are trying to solve, just make a API call to
retrieve the user information for xxx.
--
Hwee-Boon
On Mar 18, 11:22 am, "jim.renkel" wrote:
> Richard,
>
> I think the problem you're trying to solve here is: given a URL of the
> formhttp://twitter.com/xxx, is xxx a valid
I built it into an iPhone client, blogged about it here -
http://motionobj.com/blog/the-conversation-view-in-simplytweet. Is
such a thing in wide demand?
--
Hwee-Boon
On Mar 18, 11:18 am, TjL wrote:
> This seems like it would be a fairly easy project to do, something like
>
> http://tweetbynumb
ate ID from a protected user?
> -Chad
>
>
>
> On Tue, Mar 10, 2009 at 4:31 PM, Hwee-Boon Yar wrote:
>
> > In order to find updates after a protected account's update, I am
> > running the following query, setting since_id to the ID of that
> > updat
In order to find updates after a protected account's update, I am
running the following query, setting since_id to the ID of that
update.
http://search.twitter.com/search.json?q=to:simplytweet2&since_id=1297312280
The problem of course is that this query fails [1] since searching
with a since_id
Hi there,
I took the chance to test out/verify what HTTP status code I should
handle during the current downtime (GMT+8 3pm 19/Feb/2009). But it
looks like 200 is returned when the docs says it should be 502. Can
anyone verify? Thanks.
47 matches
Mail list logo
