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:simplytweet2since_id=1297312280
The problem of course is that this query fails [1] since searching
with a since_id
getting an update ID from a protected user?
-Chad
On Tue, Mar 10, 2009 at 4:31 PM, Hwee-Boon Yar hweeb...@gmail.com 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
update.
http://search.twitter.com
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 luo...@gmail.com wrote:
This seems like it would be a fairly easy project to do, something like
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 ja...@renkel.name wrote:
Richard,
I think the problem you're trying to solve here is: given a URL of the
formhttp://twitter.com/xxx, is
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
://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 guess it's a bug.
Eberhard
On Mar 20, 9:40 am, Hwee-Boon Yar hweeb
This:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/bba8bbd5176fbb24/4a9cb5d5780da976?hl=enlnk=gstq=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
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 jkalu...@gmail.com wrote:
Matt,
As Doug mentioned, we're working on fixing the public
Oh god. Please share where is this twitter-announce list?
--
Hwee-Boon
On May 10, 12:51 pm, Jesse Stay jesses...@gmail.com 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
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
Isn't this what I said?
--
Hwee-Boon
On Jul 24, 2:36 pm, srikanth reddy srikanth.yara...@gmail.com wrote:
@jim.renkel. Thanks a ton. I think now it is clear.
It appears to me that each user of a white-listed site gets 20k
requests per hour, independent of any other users of that site or
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
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
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 jazzyc...@gmail.com wrote:
We've asked
Is favoriting broken?
--
Hwee-Boon
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,
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 a...@twitter.com wrote:
As mentioned previously, the Twitter operations team willartificially
increase the maximum status ID to 4294967296 this
One suggestion: similar to API changes, it seems more appropriate that
if you want to force it, to do it earlier in the week, starting
Monday, rather than Friday. That leaves enough resources and hands to
stock up water and non-perishable goods rather than on a Friday.
--
Hwee-Boon
On Sep 12,
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 ghil...@gmail.com wrote:
I believe that search does not return statuses of protected users (even when
authenticated, though I may be wrong and
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
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 luo...@gmail.com wrote:
On Tue, Oct 20, 2009 at 2:11 PM, Michael Ivey michael.i...@gmail.com wrote:
As an aside; please don't bump threads on this list.
As an aside, how
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
range which 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 hweeb...@gmail.com wrote:
I have been having these very slow API response running on Slicehost
(most of the time way more than 2
On Oct 22, 12:05 am, RandyC bioscienceupda...@gmail.com 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
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
(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
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
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
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_1since_id=6357863332
{results:[],max_id:6358271161,since_id:
On Jan 14, 8:30 am, twittme_mobi nlupa...@googlemail.com wrote:
Hello ,
Regarding Basic Auth Deprecation is June
Any where this is announced?
--
Hwee-Boon
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 rhyl...@gmail.com wrote:
Ryan Sarver said it last last
yearhttp://twitter.com/Scobleizer/status/6493268213
On Jan 17, 4:46 am, Hwee-Boon Yar hweeb...@gmail.com
Is there a reasonable replacement to provide the same functionality in
mobile apps?
--
Hwee-Boon
On Mar 5, 12:04 am, Raffi Krikorian ra...@twitter.com 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,
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
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 15, 10:39 pm, Hwee-Boon Yar hweeb...@gmail.com wrote:
My
This is probably so obvious I'm missing it. How do I delete a retweet?
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
I get my list from http://search.twitter.com/advanced.
--
Hwee-Boon
On Jun 3, 10:21 am, Bess bess...@gmail.com 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
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 therhysmeis...@hotmail.com wrote:
Hi All,
I am having
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
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
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,
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:
42 matches
Mail list logo
