The videos are preserved at http://justin.tv/twitterchirp/all.
Thanks,
Doug
On Tue, Apr 13, 2010 at 1:41 PM, 46Bit wrote:
> Just to check - if we're unable to watch the live stream I presume
> saved videos will be available afterwards?
>
> On Apr 13, 8:06 pm, Doug Williams
For completeness sake, the URL below will host the video on the Chirp site:
http://chirp.twitter.com/live.html
<http://chirp.twitter.com/live.html>Thanks,
Doug
On Tue, Apr 13, 2010 at 12:06 PM, Doug Williams wrote:
> Dewald,
> This will be public (no access code needed) f
Dewald,
This will be public (no access code needed) for the event.
Thanks,
Doug
On Tue, Apr 13, 2010 at 10:54 AM, Dewald Pretorius wrote:
> I notice that the Chirp channel is set to a private channel.
> http://www.justin.tv/twitterchirp
>
> Is it going to be made public on Wednesday, or else,
Hi all --
The Hack Day at Chirp is a remarkable opportunity for the Twitter
Platform. It is the first time that the ecosystem and Twitter's
extended team will meet under one roof. We are excited to collaborate
at such a deep level; answering questions face-to-face while updating
the Twitter team on
Jonathan,
Lead the way! I'll happily point to any any efforts you are doing around
coordination with the @Chirp account, etc...
Thanks,
Doug
On Tue, Apr 6, 2010 at 3:30 PM, Abraham Williams <4bra...@gmail.com> wrote:
>
>
> On Tue, Apr 6, 2010 at 15:06, Jonathan Strauss <
> jonat...@snowballfact
Hi all --
With only nine days left until Biz's opening speech, Chirp -- Twitter's
first conference for developers -- is fast approaching! The two day event
will be in San Francisco on April 14th and 15th. You can image how excited
we are to have a conversation with everyone from the ecosystem in th
We're going to use moderator to drive some of the discussion tonight. Ask
and vote for questions here: http://bit.ly/bhRx7L
Thanks,
Doug
On Sat, Feb 27, 2010 at 3:27 PM, Jaanus wrote:
> On Feb 27, 1:00 am, "Orian Marx (@orian)" wrote:
> > If TwitterHQ isn't opposed I'm sure there's someone wh
t the best platform on the web, please apply:
http://bit.ly/Twitter_Platform. The work here is fast and
dynamic, and we don't always know where the road will lead. Which is
what makes it fun.
We look forward to hearing from you and all of your ideas to make the
Platform great.
Thanks,
Doug Williams
http://twitter.com/dougw
> > [1]
> http://status.twitter.com/post/163603406/working-on-unexpected-downtime
> >
> > > Thanks,
> > > Doug
> >
> > > On Aug 15, 11:08 am, Doug Williams wrote:
> >
> > > > Hi all --If you have been monitoring our status blog [1]
Hi --
Auto following is discouraged. However if your app relies on the user
following your account, you should clearly state well ahead of the
auto follow action what relationship changes will occur to the user's
account.
Thanks,
Doug
Sent from my mobile.
On Aug 15, 2009, at 12:07 PM, b
Hi all --If you have been monitoring our status blog [1] or been to
Twitter.com today you have noticed that we are once again experiencing
problems due to external causes. The issues causing the downtime require
that we once again take measures to bring the site back online.
The first step our ope
Hi there --
Check out #6 in the Things Every Developer Should Know article [1].
1. https://apiwiki.twitter.com/Things-Every-Developer-Should-Know
Thanks,
Doug
On Sun, Aug 2, 2009 at 11:27 AM, dp wrote:
>
> When the REST API limit for using count/page reaches 3200 for a
> particular user accoun
Hi all --
We are excited to announce that Chad Etzel has joined our team part-time to
support the developer community. He is the one man show behind TweetGrid [1]
amongst other projects [2]. We reached out to Chad to join our team after
his continual and valuable participation in the community made
working now?
> Jesse
>
>
> On Fri, Jul 31, 2009 at 1:31 PM, Doug Williams wrote:
>
>> Jesse,
>> That is not true. With the Sign in with Twitter flow (not the standard
>> OAuth flow which is also available) -- If the user is logged in and has
>> previously a
ove to a
>>> better Auth system than OAuth? With Facebook Connect I just have to click
>>> once, and if the user is already logged in and approved my app, they never
>>> see the Facebook login box again. Where as with Twitter there are 3 points
>>> of potential
Thanks for the kind words, from the Twitter team.
Cheers,
Doug
On Thu, Jul 30, 2009 at 8:52 PM, MRWILLAN wrote:
>
> I like to take this time to personally THANK Twitter Development for
> the work your doing and fixing in the line of spam follow up and
> tactical problems, I know there must be
o being consistent...
>
> Thanks!
>
> Brooks
>
>
>
>
> On Jul 21, 3:45 pm, Doug Williams wrote:
> > Chad,Your assessment is spot on.
> >
> > At the heart of search there are a number of data stores that accept
> queries
> > (reads) while at the same t
You can access advanced search here: http://search.twitter.com/advanced
Thanks,
Doug
On Thu, Jul 30, 2009 at 10:01 AM, Vincent Nguyen wrote:
> Yes, me too! Dunno where it went??
>
> 2009/7/30 Joseph
>
>>
>> From twitter.com. I'm pretty sure it was there a couple of days ago.
>> Am I not caffeine
The account/end_session method does not log the user out of Twitter.com. It
simply invalidates the session token that is created with the current API
session.
There is no method that will log a user out of Twitter.com.
Thanks,
Doug
On Wed, Jul 29, 2009 at 10:53 AM, Stuart wrote:
>
> 2009/7/29 G
> mean rolling back the fix so as not to affect multiple, successful,
> authorized logins? I'm hopeful that "this approach" means that our
> apps will not be affected yet again by changing to a new auth
> approach.
>
> I appreciate you all keeping this thread infor
Well said, Duane.
Thanks,
Doug
On Wed, Jul 29, 2009 at 7:18 AM, Duane Roelands wrote:
>
> First, let me state from the start that I am no fan of OAuth,
> Twitter's implementation of it, or the way that they've behaved with
> regard to it. Now, with all that being said.
>
> If your website expect
You can also take a look at the public /follow method of the Streaming API:
http://apiwiki.twitter.com/Streaming-API-Documentation
Thanks,
Doug
On Tue, Jul 28, 2009 at 9:23 PM, chinaski007 wrote:
>
>
> There is no direct way to do this, no. But you might be able to
> accomplish the same thing
Guna,Check into the in_reply_to_status_id parameter for the statuses/update
method [1]:
in_reply_to_status_id. Optional. The ID of an existing status that the
update is in reply to.
- Note: This parameter will be ignored unless the author of the tweet
this parameter references is mentioned
If you are using a client library, please specify the library and version.
There is a chance that you are all running into the same library-based
incompatibility and could work together (or with the maintainer) to
determine the fix.
Thanks,
Doug
On Mon, Jul 27, 2009 at 9:40 PM, Doug Williams
Please use the OAuth playground [1] to test your signatures against the
expected result. I am working to gather specifics to help your debug process
(i.e. what changed?) in the mean time.
1. http://googlecodesamples.com/oauth_playground/
Thanks,
Doug
On Mon, Jul 27, 2009 at 9:29 PM, winrich wrot
Duane,I will gather some specifics and post them here. We appreciate your
patience.
In the mean time, you can use the OAuth playground to see where your
signature is failing:
http://googlecodesamples.com/oauth_playground/
Thanks,
Doug
On Mon, Jul 27, 2009 at 9:27 PM, Duane Roelands wrote:
>
> S
wrote:
> > Are we sure there is no further regression bug in this new fix?
> >
> > On Jul 27, 7:14 pm, Doug Williams wrote:
> >
> >
> >
> > > If you are still seeing errors you should check your code to ensure
> that you
> > > are sending th
hinaski007 wrote:
> > Doug:
> >
> > Does this mean that Marcel made a fix for this? Or rather that we
> > should examine our code to find the culprit?
> >
> > Thanks,
> > Peter Bray
> >
> > On Jul 27, 6:24 pm, Doug Williams wrote:
> &
statuses/replies is an alias for statues/mentions. It is completely due to
history where mentions used to be called replies. Rather than break apps
that relied on statuses/replies, we made an alias to ensure backward
compatibility.
Thanks,
Doug
On Sun, Jul 26, 2009 at 9:23 AM, Kuo Yang wrote:
There is currently no Streaming API to receive DMs for a given user. If you
have a great use case for this please share it here.
We like to have justification for new streaming methods. If you have ideas
to help augment a business case for engineering resources, we would love to
know about them.
T
We index tweets very quickly, normally within a few seconds.
Thanks,
Doug
On Mon, Jul 27, 2009 at 4:26 PM, Green McP wrote:
>
> Hi,
>
> How quickly are Tweets available in the search results? Should I
> assume a minute until it's guaranteed to show up? Five minutes? Just
> wondering for an a
and ensure you are correctly signing requests
as per the spec.
Thanks,
Doug
On Mon, Jul 27, 2009 at 6:05 PM, Doug Williams wrote:
> Marcel is shipping a fix for this as I type.
>
> Thanks,
> Doug
>
>
>
>
> 2009/7/27 João Pereira
>
> Same here.
>>
>>
Marcel is shipping a fix for this as I type.
Thanks,
Doug
2009/7/27 João Pereira
> Same here.
>
>
> On Tue, Jul 28, 2009 at 1:26 AM, goodtest wrote:
>
>>
>> twitter api server seems to be down (getting invalid signature) since
>> 5.15 pm pst
>
>
>
>
>
No. We currently only return around 7 days of data with search.
You can learn more about this, and the reasons behind it, in our Getting
Started materials provided on apiwiki.twitter.com.
Thanks,
Doug
On Mon, Jul 27, 2009 at 2:23 PM, jms wrote:
>
> We recently hosted conference attendees used
monitor these forums and the API Issues and still see too many OAuth
> > issues being reported to give me a level of comfort that I can safely
> > switch over to OAuth.
> >
> > On Jul 24, 5:46 pm, Doug Williams wrote:
> >
> >
> >
> > > Well said
I see this is the second post for this same question. Please refrain from
posting multiple times. It adds value to the list.
You are running into a bug that has been discussed here in the past. The
value of the following field was unreliable due to caching constraints. A
few weeks ago we deprecated
We've got a method for that:
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-friendships-show
Thanks,
Doug
On Mon, Jul 27, 2009 at 8:39 AM, cem wrote:
> w can I know from my application that the user sent the reply is
> fallowing me . I fallowed myself from another account and the
>
Please see http://apiwiki.twitter.com/Return-Values
Thanks,
Doug
On Mon, Jul 27, 2009 at 8:00 AM, cem wrote:
>
> Hi I am getting data from twitter in an array but I need detailed
> definition of fields there for example what will the value fallowing
> get if the user is fallowing me ? Is ther
I was unable to reproduce with a script. Is anyone else seeing this?
Thanks,
Doug
On Sun, Jul 26, 2009 at 7:12 PM, TjL wrote:
>
>
> http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-friends_timeline
> lists
>
> URL:
> http://twitter.com/statuses/friends_timeline.format
>
> Format
>>> but since it defaults to be the same as their public ID, only those
>>> concerned about their service being denied would change it and
>>> subsequently use it instead of their public ID to access associated
>>> sites such as twitpic or twxlate.
>>>
&g
t; "http://twitter.com/statuses/followers.xml?count=100&page=44"; | grep
>> > > > "" | wc -l
>> > > > 17
>> > > > doug-williamss-macbook-pro:~ igudo$ curl -u dougw:PASSWORD
>> > > > "http://twitter.com/statuses/
What John was referring to above were the statements in the EULA which
you sign to access the gardenhose which prohibit this type of
redistribution.
Thanks,
Doug
On Thu, Jul 23, 2009 at 7:19 AM, Twittledee wrote:
>
> So, I actually think that this is a very interesting idea ... but I
> would
All --Last month we sent out the following call to developers [1] to add
identifying User Agents and HTTP Referrer strings to their Search API
traffic. This is part of a drawn out push to incent as much of our search
traffic as possible to include this identifying data.
To identify your applicatio
Scott,This change will only affect Basic Auth, and will not affect OAuth
applications.
Thanks,
Doug
On Tue, Jul 21, 2009 at 4:27 PM, Scott wrote:
>
> Thanks for the update Doug. Does this still apply to OAuth apps?
> Also, if a user goes through an app and unsuccessfully attempts to
> login
Verified and accepted this defect. In the future, let's keep noise down on
this list by leaving this discussion to the issue tracker itself.
Thanks,
Doug
On Wed, Jul 22, 2009 at 12:34 PM, Coderanger wrote:
>
> I recently posted this as a bug and was hoping if anyone else can
> verify it: htt
Joseph,I assume you mean the sentiment portion of the Search API? That is
not available as structured data through an API call.
Thanks,
Doug
On Wed, Jul 22, 2009 at 3:36 AM, Joseph wrote:
>
> Is the attitude (tude) flag stored as part of a tweet? and if so, do
> any of the data structures re
Let's bring the discussion on the update to the new thread:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/2d68c74567bc9809
Thanks,
Doug
On Mon, Jul 20, 2009 at 10:08 PM, Doug Williams wrote:
> Martin,
> The change certainly went out premature
Devs --A change shipped last week that limited the number of times a user
could access the account/verify_credentials method [1] in a given hour. This
change proved hasty and short-sighted as pointed out by the subsequent
discussion [2]. We apologize to any developer that was adversely
affected. Gi
Chad,Your assessment is spot on.
At the heart of search there are a number of data stores that accept queries
(reads) while at the same time perform writes from an indexer. Heavy load --
large numbers of queries, large number of writes or both, or both -- can
cause the write replication between th
se my application because everyone will get suspended who uses it
> then?
>
> Thanks,
> Serge
>
> On Jul 20, 11:11 pm, Doug Williams wrote:
>> Serge,
>> Looking at the account I'm not quite sure why it was suspended. The
>> records are inconclusive. I'
Martin,
The change certainly went out prematurely which is admittedly a
mistake on our end. I will have details tomorrow morning to share
about our fix.
Thanks,
Doug
On Mon, Jul 20, 2009 at 7:45 PM, Martin Omander wrote:
>
> Doug,
>
> Thanks for letting us know about the new request limit. I
We are going to roll this change back and re-evaluate how we can
better accomplish our goals. There are problems and shortcomings of
this strategy that we need to mitigate.
I will update this thread when we have a concrete plan to share. I do
not have a definite date or time for the rollback but
x27;d like to work on the API, we're hiring:
>>> http://static.twitter.com/jobvite_frame.html?c=q8X9VfwT&jvi=oAYcVfwp,Job.
>>>
>>> On Sun, Jul 19, 2009 at 22:05, Doug Williams wrote:
>>> >
>>> > We will certainly miss having you on the team,
> Support also keeps changing the status on my support thread to solved
> while it clearly isn't.
>
> Thanks for looking in to this.
>
> Serge
>
> On Jul 20, 8:43 pm, Doug Williams wrote:
>> Hard to check into your suspension without a username :) I&
Kevin,
Please do not bump your thread here. It adds no value and contributes noise.
That said, there is an open issue for this [1]. Be sure to add a star
to receive updates to the defect. The defect is due to a replication
delay and typically takes less than 90 minutes for the replication to
reac
Hard to check into your suspension without a username :) I'd take this
off-list but I am hoping there is a learning opportunity here.
Whitelisted accounts are able to get suspended. Whitelisting affects
REST API GET requests and DM update limits only. It does not protect
you from suspension, it w
We have discussed establishing a more formal relationship with
developer representatives to help bring outside perspective and
balance to our larger platform decisions. We are still a few quarters
away from where we envisioned this model being viable.
If Peter and others could come up with a plan
All,
This change was thrown out on the pipeline rather quickly. We admittedly
should have done a better job voicing this rollout well in advance though it
was not a normal week at HQ for a number of very public and private reasons.
Users are now limited to 15 calls to account/verify_credentials pe
Andy,
What is your goal?
Thanks,
Doug
On Sun, Jul 19, 2009 at 12:15 PM, Andrew Badera wrote:
> On Sat, Jul 18, 2009 at 8:07 AM, Stuart wrote:
>
>>
>> 2009/7/18 Andrew Badera :
>> > What's the best/lowest impact fashion of polling Twitter for status if
>> > you're not already performing an op
We will certainly miss having you on the team, Matt.
Regards,
Doug
On Fri, Jul 17, 2009 at 11:19 PM, surya sravanthi wrote:
>
> All the bast Matt!!! Thanks for all you
> r help .
>
>
> On Sat, Jul 18, 2009 at 2:48 AM, Matt Sanford wrote:
> >
> > Hi everybody*,
> >
> >Starting next week I
Abir,By default, accounts are limited to 250 direct messages a day.
Whitelisted accounts are able to make 10K direct messages a day. Design for
these constraints and ensure notifications are opt-in, and we are happy to
support your app.
Thanks,
Doug
On Thu, Jul 16, 2009 at 7:16 PM, Abir wrote
You can page through a user_timeline [1], up to the last 3200 tweets [2].
1.
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-user_timeline
2.
http://apiwiki.twitter.com/Things-Every-Developer-Should-Know#6Therearepaginationlimits
Thanks,
Doug
On Thu, Jul 16, 2009 at 4:50 PM, John
By suspension, do you mean rate limiting [1]?
1. http://apiwiki.twitter.com/Rate-limiting
Thanks,
Doug
On Thu, Jul 16, 2009 at 12:21 PM, sjespers wrote:
>
> Nothing special. It's a simple mobile Twitter app. Because I'm using
> Flash Lite I use my server as a proxy between the app and the
That looks like the result from a rather old bug (which has been closed)
that allowed images to upload without resizing.
Thanks,
Doug
On Wed, Jul 15, 2009 at 11:22 PM, TCI wrote:
>
> ... which is evidently slowing down pages that download these images
> and then scale them to their small size.
Agreed. I will massage the copy today. Of course I'm assuming people read
the documentation but it is at least a start.
Again, if you have suggestions, please email a...@twitter.com.
Thanks,
Doug
On Thu, Jul 16, 2009 at 7:37 AM, Matt Sanford wrote:
>
> Hi Lee,
>
>The rate limit is per-acc
Whitelisted users have a direct messaging limit of 5K messages per day.
Whitelisted users do not receive and increase in public status updates,
however.
Thanks,
Doug
On Thu, Jul 16, 2009 at 9:29 AM, Andrew Badera wrote:
> On Thu, Jul 16, 2009 at 11:32 AM, jmathai wrote:
>
>>
>> If you're se
There have never been any conversations internally about shutting down
services for competitive reasons. That would contradict our ethos of
an open API and work against the fostering of a healthy ecosystem. The
majority of our conversations center around how to stabilize the
developer-base and ens
ers started with
>
> HTTP/1.1 200 OK
>
> In other words, this is the same problem I ran into yesterday. Is
> there any other data that would help troubleshoot this?
>
> All the best,
>
> /Martin
>
>
>
> On Jul 13, 5:52 pm, Doug Williams wrote:
>> Martin
Martin,
This sounds like issue 795 [1].
When you get the 200, are you sending the same (duplicate) text as the last
successful update? If so, this is the expected behavior.
However, if you are sending new (non duplicate) text and you are hitting the
update limit, you should be receiving a HTTP 40
Martin,
That's interesting.
Is there a pattern to this? Can you offer steps for recreation? It would be
helpful to have full header information when this does happen so we can look
to see if a specific machine that is returning incorrect information.
Thanks,
Doug
On Mon, Jul 13, 2009 at 4:26 P
Randy,
Please see the help article on this very subject [1].
If this is for a developer or API related project please contact us off list
so we can discuss [2].
1. http://help.twitter.com/forums/10713/entries/42646
2. http://apiwiki.twitter.com/Support
Thanks,
Doug
On Mon, Jul 13, 2009 at 5:
Confirmed on my end. Can you please create a new issue for this [1].
1. http://code.google.com/p/twitter-api/issues/entry
Thanks,
Doug
On Sun, Jul 12, 2009 at 9:09 AM, Thorsten Suckow-Homberg
wrote:
>
> Hey there,
>
> when calling /favorites/create/[id].xml
>
> the response body always retur
This seems like a caching invalidation bug. We will be discussing it at
tomorrow's team meeting and I am hopeful the fix will be coming shortly.
Thanks,
Doug
On Mon, Jul 13, 2009 at 2:30 PM, Rudifa wrote:
>
>
> Thank you, Clint
>
> After I posted my questions I went out for a long walk.
> Now
Tom,
We do not allow HTML in tweets. Only plain text. Any links sent will be
automatically linked on Twitter.com but it is up to third-party clients to
handle any linking within their application.
Thanks,
Doug
On Mon, Jul 13, 2009 at 6:38 AM, Stuart wrote:
>
> 2009/7/13 Tom :
> >
> > I'm kind
rls would be delivered sometime in June 2009. Do we have any
> updates? Thanks.
>
>
>
> On May 21, 6:14 pm, Doug Williams wrote:
> > Thanks for your patience guys -- we realize the benefits of predictable
> > static URLs. It's unfortunately kind of back-burner wo
You can post bugs and feature requests here:
http://code.google.com/p/twitter-api/issues/list
This specific issue will be moved to the V2 Roadmap but please to create one
so we can track the request.
Thanks,
Doug
On Sun, Jul 12, 2009 at 7:53 AM, JDG wrote:
> Post a reply to @twitterapi for
Samir,
User search is something we would like to offer in the future through the
API. The project is not highly ranking on the current overall roadmap, so
there is no ship date to report.
Thanks,
Doug
On Fri, Jul 10, 2009 at 2:53 PM, SamirR wrote:
>
> Are there plans to implement user sear
All --
We are rolling back the twimg.com change because a number of issues became
apparent when we moved it into production -- one being the lack of SSL
support in the caching layer that many have noted. We do hope to make this
change rather soon, but we have problems to fix before moving forward w
Joe,
With the REST API you will need to perform parsing of data based on
timestamp on the client side. We do not have facility in the API to request
data since a timestamp. There was a parameter ("since") that allowed such a
search but it was removed a number of months back as you see in the
change
hu, Jul 9, 2009 at 8:53 AM, Clint Shryock wrote:
>
>> I'm still having issues with the profile_image_url attribute of users/show
>> updating in a timely fashion, any chance this issue be resolved with this
>> update?
>> +Clint
>>
>>
>> On Wed, Jul 8,
Indeed, this is by design. As Grant said, it is to prevent brute force
attacks.
Thanks,
Doug
On Thu, Jul 9, 2009 at 10:58 AM, Grant Emsley wrote:
>
> I thought it might be by design, but couldn't find that mentioned
> anywhere. I guess it is necessary to prevent apps guessing the pin,
> thou
aribitrary
sub-domain (*.twimg.com).
Thanks,
Doug
On Jul 8, 2009, at 6:20 PM, Doug Williams wrote:
Folks --
We are going to be moving images to a new domain (twimg.com) to
streamline our image hosting and offer better performance. We hope
this will have limited impact as will only change the
At the moment there is no internal interest in offering a programmatic URL
scheme to locate user images. One of the easiest cache breaking strategies
is to change the URL for the image which works across browsers,
applications, etc., which is why we like the unique URLs. Additionally, we
want to en
Folks --
We are going to be moving images to a new domain (twimg.com) to streamline
our image hosting and offer better performance. We hope this will have
limited impact as will only change the image URL. Example URLs include:
Profile images:
http://s3.amazonaws.com/twitter_production/profile_ima
It is not possible to view a user's email address. Additionally, it is not
possible to perform a user lookup based on an email address. If you do not
trust an application enough to not change your email address, we suggest you
not use that application.
As always, please email a...@twitter.com if y
The documentation for the /search method [1] specifies that all queries
should be performed with an HTTP GET. On or after July 15, 2009, we will
begin enforcing the use of HTTP GET for all queries. Requests sent to the
/search method which are not performed with an HTTP GET will be met with an
HTTP
The documentation for the /search method [1] specifies that all queries
should be performed with an HTTP GET. On or after July 15, 2009, we will
begin enforcing the use of HTTP GET for all queries. Requests sent to the
/search method which are not performed with an HTTP GET will be met with an
HTTP
Abraham Williams has a great PHP sample here that is simple and easy to use:
http://twitter.abrah.am/
Thanks,
Doug
On Wed, Jul 8, 2009 at 12:25 PM, Echieo wrote:
>
> Hey everyone,
>
> I'd really like to use OAuth for my new twitter application, as I know
> Twitter is trying to move in that di
The replies and DMs sent to @spam are manually reviewed by our abuse support
staff at the moment.
Thanks,
Doug
On Tue, Jul 7, 2009 at 5:58 PM, Zac Bowling wrote:
>
> Is the @spam account monitored by a bot or a human?
>
> Zac Bowling
>
>
>
>
> On Tue, Jul 7, 2009 at 5:34 PM, Jeffrey
> Greenbe
but it returns 502 error. I realize that when I typed it to the
> browser's adress bar, there is no problem.
>
>
>
> On Jul 7, 12:54 am, Doug Williams wrote:
> > Kaan,Please provide more details about what you are doing and how you are
> > trying to obtain the data. Withou
Yes they are sequential, meaning that you can and should use the last tweet
a user has read as the since_id for subsequent calls.
Thanks,
Doug
On Mon, Jul 6, 2009 at 5:43 PM, Duane Roelands wrote:
>
> Is a tweet with a higher status ID always newer than a tweet with a
> lower status ID?
>
>
Kaan,Please provide more details about what you are doing and how you are
trying to obtain the data. Without any of these details, it's hard to deduce
why you are getting a 502 Timeout.
Thanks,
Doug
2009/7/6 Kaan ŞENGÜL
>
> I'm working on a project that needs one person's timeline, I mean al
u follow me? http://twitter.com/dougw
On Mon, Jul 6, 2009 at 10:32 AM, Duane Roelands wrote:
>
> Do you ever get an empty response set? I was experimenting with the
> pagination and I found that if you request page 20 (for example) for
> someone who only has one page of friends, y
Please email the API team for questions pertaining to development or
application accounts [1].
1. http://apiwiki.twitter.com/Support
Thanks,
Doug
On Mon, Jul 6, 2009 at 10:40 AM, tweetalkr wrote:
>
> My web app was flagged by Google two weeks ago as an attack site
> though I have never foun
You should either page through statuses/friends until you get an empty
response set or use statuses/show to get the number of friends expected and
intelligently page to the end of the list.
Thanks,
Doug
On Mon, Jul 6, 2009 at 1:39 AM, Dmitriy Vyukov wrote:
>
> Hi!
>
> It's unclear how I mus
Peter,
Verification of companies is in the future for Twitter. There is no publicly
released ship date to mention but it is safe to say that within the next
year that this should be coming to the service.
Thanks,
Doug
On Sat, Jul 4, 2009 at 4:47 PM, JDG wrote:
> i think the only thing that wo
Yes, you can use two Streaming API methods from the same IP address. As you
already know, it will require two accounts when connecting simultaneously.
Thanks,
Doug
On Sun, Jul 5, 2009 at 9:33 PM, Cary Knoop wrote:
>
> I am writing an application and ideally I like to use Tracker to
> follow
Josh,
Check out our help article on user names [1]. If you own the trademark,
please submit a ticket through the support site and explain your situation.
They have a 10 day backlog so please be patient.
1. http://help.twitter.com/forums/10713/entries/14608
Thanks,
Doug
On Fri, Jul 3, 2009 at
Try the page parameter. Here's the documentation to get you started [1].
1.
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses-user_timeline
Thanks,
Doug
On Fri, Jul 3, 2009 at 10:39 AM, Ravinder Chopra <
ravinderc.impi...@gmail.com> wrote:
>
> hi
>
>
> I think i need extra param
ou please help me understand what I can do to add followers
>> again?
>>
>> Thanks for your attention.
>>
>> On Jul 2, 8:13 am, Doug Williams wrote:
>>
>>> It initially seemed like you were asking about the update limit but now
>>> you
&
1 - 100 of 617 matches
Mail list logo
