responsible for this.
Is this a known issue, or has someone else run into something similar?
Thanks,
Doug
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.co
Thanks for the feedback, but that's not quite what I was looking for.
I'm not looking simply for a display of the user's tweets client side,
but to get them server side and do stuff based on the contents of the
tweet. For example (making this up), I might track the number of
times a given word is
ers my app is following into my app. I'm a bit concerned that this
may simply be a hack and maybe even violate twitter's TOC.
So, overall, I'm just looking for a bit of guidance out of the gate on
where to start research and work. Also, if you know of any quality
Ruby gems that implem
I cannot find any documentation on how to prepare for it. I use fully
qualified URLs in the tweets over the REST API. Will these
automatically be converted? And if so, what is the size we should
assume for their length?
I would hate to have to integrate another service for shortening if
this on
Got it. Thanks, Taylor.
On Mar 22, 11:16 am, Taylor Singletary
wrote:
> Hi Doug,
>
> We don't have a search result counting API available at this time. One
> approach would be to prepare ahead of time and use the Streaming API's track
> filter on the URL you're int
ld like is the count... the number of statuses
that mention that URL.
Is there a way to simply retrieve _just_ the count of URL mentions?
Thanks, Doug
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/
LOL thanks that was it (palm-to-face).
Thanks for the suggestions folks
On Sep 27, 3:38 am, Tom van der Woerdt wrote:
> Hi Doug,
>
> The only thing I can think of is that you aren't sending an
> Authorization: header that starts with OAuth.
>
> Tom
>
> On
Hi folks,
I have been banging my head against the wall trying to figure out why
I keep getting 'failed to validate oauth signature and token' when
requesting the access token using xauth. I did get xauth enabled,
however I should point out there is nothing indicating this in the
app's detail page
I am loving the terminology.
-Doug Tangren
http://lessis.me
On Mon, Aug 30, 2010 at 9:33 PM, John Kalucki wrote:
> Spritzer remains at 1%. We can't increase this one at the moment due to
> technical reasons unrelated to capacity or policy. We'll probably leave this
> at 1%
I cannot create a new app, I get a screen that says "Something is
technically wrong. Thanks for noticing - we're going to fix it up and
have things back to normal soon." How do I get around this error?
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 Wednes
0.
1. http://bit.ly/chirpshowcase
Thanks,
Doug
http://twitter.com/dougw
--
To unsubscribe, reply using "remove me" as the subject.
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, Jonath
we opened tickets for the Hack Day. There are still $140 Hack Day passes and
a few full conference tickets left so if you would like to attend please
head to http://chirp.twitter.com and register. We hope to see you there!
Thanks,
Doug
http://twitter.com/dougw
--
To unsubscribe, reply using "remove me" as the subject.
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 opp
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
guage. Its probably not that helpful for all those
not actually using the web ui, but for those interested, its up on the
githubs (http://github.com/softprops/bird-speak/blob/master/).
-Doug Tangren
http://lessis.me
@softprops
On Thu, Oct 8, 2009 at 6:08 PM, Marcel Molina wrote:
>
> Over
Sean,At this time we are monitoring the situation and containing issues as
we see them. Let's hold off on restoration requests until things stabilize.
Thanks,
Doug
On Sat, Aug 15, 2009 at 1:17 PM, Sean Callahan wrote:
>
> Thanks for the update Doug. Users on TweetPhoto are not ab
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:
operations team must take will likely cause API downtime,
especially affecting OAuth. We apologize for the inconvenience and we will
work quickly to reduce the impact to the API. We appreciate your patience
and I will update you as soon as we know more.
Thanks,
Doug
Will Statuses/Replies be deprecated in the future (e.g. v2 of the
API?)
On Jul 27, 6:56 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
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
> partic
lease let us
know.
1. http://tweetgrid.com
2. http://jazzychad.net
3. http://twitpic.com/a99zj (@noradio and @al3x in frame)
Thanks,
Doug
Jesse,
If it is not, then it is a defect. That is the intended functionality.
Thanks,
Doug
On Fri, Jul 31, 2009 at 10:57 AM, Jesse Stay wrote:
> Doug, interesting - I didn't realize that's what Sign on With Twitter did.
> Last I tried that wasn't working though - is that
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
approved the app, they will be immediately redirected back to the
application without ever seeing a Twitter dialog.
Thanks,
Doug
On Fri
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 t
, there is no ETA on a fix.
Thanks,
Doug
On Thu, Jul 30, 2009 at 7:12 AM, Brooks Bennett wrote:
>
> Doug,
>
> Is there any status update on this issue? Users are really starting to
> get frustrated with results and wondering what the status is on things
> getting back 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 co
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:
>
> 200
dress. If a single IP address makes 15 attempts to access a
> protected resource unsuccessfully for a given user (as indicated by an
HTTP 401),
> then the user will be locked out of authenticated resources from that
> IP address for 1 hour.
Thanks,
Doug
On Wed, Jul 29, 2009 at 9:51 AM, Ray
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 sai
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 th
mentioned within the status text. Therefore,
you must include @username, where username is the author of the
referenced tweet, within the update.
1.
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0update
Thanks,
Doug
On Tue, Jul 28, 2009 at 8:26 AM, Guna wrote:
>
>
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
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
As stated above, some applications were sending invalid signatures which we
were accepting as valid. This vulnerability was pointed out by a developer.
Some libraries and code which may have previously worked may be broken by
this security fix.
Thanks,
Doug
On Mon, Jul 27, 2009 at 7:44 PM
If you are still seeing errors you should check your code to ensure that you
are sending the correct signature.
Thanks,
Doug
On Mon, Jul 27, 2009 at 7:10 PM, winrich wrote:
>
> mine broke too. i wonder though, i'm using the oauth python libraries
>
> On Jul 27, 6:35 pm, c
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
.
Thanks,
Doug
On Mon, Jul 27, 2009 at 5:24 AM, Fabien Penso wrote:
>
> Hi.
>
> I wonder if there is a way to use the streaming API to receive DM for
> a list of specific users.
>
> As far as I understand there isn't, is anyone working on this? Basicly
> I wan
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? Jus
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 attendee
Thanks to everyone who has contributed feedback. This approach is what we
are going to take.
Alex will be making this change shortly. I will update this thread when
there is timeframe to share.
Thanks,
Doug
On Mon, Jul 27, 2009 at 7:52 AM, TinBlue wrote:
>
> What is happening?
&g
deprecated that value and will now return it as null
permanently. Please use the friendships/show method [1] to access this data.
1. http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-friendships-show
Thanks,
Doug
On Mon, Jul 27, 2009 at 8:25 AM, cem wrote:
>
> Hi where can I get a
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 fallo
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/fr
should we
proceed with this as our solution?
Thanks,
Doug
On Fri, Jul 24, 2009 at 11:08 AM, Joshua Perry wrote:
>
> Jim's concern is valid, fortunately OAuth is immune to brute-force attacks
> once the access key has been issued to an application. For this reason alone
> I wou
http://status.twitter.com).
Thanks,
Doug
On Fri, Jul 24, 2009 at 11:31 AM, Karthik Murugan wrote:
> yes, each page request counts against the API limit
>
> On Fri, Jul 24, 2009 at 10:25 PM, Joseph wrote:
>>
>> Just as aside, does anyone know if each call to a new page count
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
&
Search API into the
future.
1.
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/f7cd82f2c43a77d0
2. http://apiwiki.twitter.com/Rate-limiting
Thanks,
Doug
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 at
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
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 s
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
will update with details and a timeline for shipping this
update.
1.
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0verify_credentials
2.
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/b057014336ff502b
Regards,
Doug
of search should continue to
improve.
Thanks,
Doug
On Tue, Jul 21, 2009 at 11:57 AM, Chad Etzel wrote:
>
> Hi API Team,
>
> A few of us have been discussing off list a funky behavior we have
> been noticing and now users are starting to notice.
>
> There is a proble
Serge,
You can always verify the whitelisted status of your IP or user
through a call to account/rate_limit_status. For instance, here are my
results:
doug$ curl -u dougw:PASSWORD http://twitter.com/account/rate_limit_status.xml
2009-07-21T08:29:35+00:00
19995
2
1248164975
Notice
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 requ
it should be
soon.
As always, thanks for your patience.
Thanks,
Doug
On Mon, Jul 20, 2009 at 6:22 PM, Jesse Stay wrote:
> The problem is so long as they are complaining on some of our apps they are
> complaining on all our apps and there's no way of telling which app cause
We are hiring front-end engineers as well if working on
HTML/CSS/JS/etc... is your cup of tea.
Thanks,
Doug
On Mon, Jul 20, 2009 at 12:13 PM, JDG wrote:
> and of course, as soon as i type that, my firefox decides to stop being a
> jerk and showing it.
>
> SEE WHAT HAPPENS WHEN Y
Serge,
Looking at the account I'm not quite sure why it was suspended. The
records are inconclusive. I've unsuspended the account.
For posterity's sake I'll repeat that whitelisting will not protect
you from suspension. Whitelisting raises select REST API limits.
Thanks,
Do
reach the object serialized by the API. I'm still working on who
actually owns this defect and will update the thread in the issue list
when I learn more.
1. http://code.google.com/p/twitter-api/issues/detail?id=758
Thanks,
Doug
On Mon, Jul 20, 2009 at 11:56 AM, Kevin Dunglas wrote:
>
n, it will not raise your follower limits, and it
will not raise your daily status update limit.
That said, what is the screen name of the account getting suspended?
Let's see if we can get you out of jail.
Thanks,
Doug
On Mon, Jul 20, 2009 at 11:38 AM, Joel Strellner wrote:
> Can you
plan, a team, and the ability
to organize an opinion, we would listen to more formal representation
from the community. If anything, it would allow us to explore what a
hybrid corporate / representative decision making process might look
like.
Interested,
Doug
On Fri, Jul 17, 2009 at 10:47 PM
, please
help us update this policy and share details of your use case.
Chad, et. al, I will follow up with the answer to your question (if this
limit affects calls to the method with correct credentials) when I have a
moment to speak with Alex.
Thanks,
Doug
On Sat, Jul 18, 2009 at 5:43 PM
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
>&
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*,
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
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
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 betw
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 s
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
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:
>
>>
project, I'd be happy to
take them off thread for privacy [1].
1. http://apiwiki.twitter.com/Support
Thanks,
Doug
On Wed, Jul 15, 2009 at 2:34 PM, MakeMoney wrote:
>
> Thanks, This was very helpful. I do not use any sort of bots or
> anything like that, and only people that wis
Sounds like we have all we need. Thanks for the help, Martin. I'll add
a link to this thread to the bug report for posterity.
Thanks,
Doug
On Tue, Jul 14, 2009 at 4:40 PM, Martin Omander wrote:
>
> Doug,
>
> Thanks for your prompt reply.
>
> Yes, it does sound like is
403 response code.
Can you specify exactly what you are doing so we can debug?
1. http://code.google.com/p/twitter-api/issues/detail?id=795
Thanks,
Doug
On Mon, Jul 13, 2009 at 4:38 PM, Martin Omander wrote:
>
> Hi there,
>
> Earlier today I ran afoul of the rate limit for upd
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
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 re
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
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 :
>
Shannon,
We have decided not to proceed with static URLs. Please see the recent
thread on the image host change for more information.
Thanks,
Doug
On Sun, Jul 12, 2009 at 10:26 AM, Shannon Whitley wrote:
>
> I recall seeing a post from a Twitter employee that static profile
> image u
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 @twitter
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 implemen
with
this change.
Updates to come as we learn about them. Thanks for your patience, here.
Twitter devs rock.
Doug
On Fri, Jul 10, 2009 at 9:49 AM, Matt Sanford wrote:
> Hi all,
> I'm working with our ops folks now to get SSL fixed on twimg.com. No
> need for running p
see in the
changelog.
The Search API does have since: and until: parameters but these only allow
specifying granulartiy down to the day. Again, any parsing down to hours
must be performed on the client side.
Thanks,
Doug
On Fri, Jul 10, 2009 at 9:05 AM, Joe Bowman wrote:
>
> An applicatio
I've asked the operation's teams to leave the old S3 hosted images available
for 2 weeks after the deploy. This should give you time to update your
caches.
Cheers,
Doug
On Thu, Jul 9, 2009 at 6:09 AM, Hayes Davis wrote:
> Are you going to shut off the S3 URLs immediately or wi
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 gu
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
quality of service and ensures
timely image updates.
The change should come within the next day or two. It is owned by another
team and they are being pretty aggressive about moving forward with the
deploy.
Thanks,
Doug
On Wed, Jul 8, 2009 at 6:23 PM, Lachlan Hardy wrote:
> Got a rough timel
/profile_images/35240332/2929920.gif
http://a0.twimg.com/profile_images/35240332/2929920.gif
Background images:
http://s3.amazonaws.com/twitter_production/profile_background_images/18156348/jessica_tiled.jpg.jpeg
http://a0.twimg.com/profile_background_images/18156348/jessica_tiled.jpg.jpeg
Thanks,
Doug
om if you have found an application
behaving poorly.
Thanks,
Doug
On Wed, Jul 8, 2009 at 3:34 PM, JDG wrote:
> if we're going with "shoulds", i think it should be both or neither.
> personally, i'd like it to be both, with the option that the user be able to
>
HTTP 403 response.
Please check your code and make any necessary updates before this change is
deployed.
1. http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search
Thanks,
Doug
HTTP 403 response.
Please check your code and make any necessary updates before this change is
deployed.
1. http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search
Thanks,
Doug
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 tr
1 - 100 of 636 matches
Mail list logo
