Tom, by the time this launches all apps using TWRequest will get proper
attribution like "from YourApp on iOS" :)
--
Ryan Sarver
@rsarver <https://twitter.com/intent/follow?screen_name=rsarver>
On Tue, Jun 28, 2011 at 5:07 PM, Tom van der Woerdt wrote:
> First of all, I t
need to optimize
for that.
We definitely understand the needs and we're exploring options on our side
to make it happen. stay tuned
--
Ryan Sarver
@rsarver <https://twitter.com/intent/follow?screen_name=rsarver>
On Tue, Jun 28, 2011 at 4:48 PM, Paul Haddad wrote:
> Ryan,
>
reat experience so let us know how we can help.
Ryan
--
Ryan Sarver
@rsarver <https://twitter.com/intent/follow?screen_name=rsarver>
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tra
x27;s authorization as that doesn't
make sense.
I don't expect everyone to be able to use User Streams or Site Streams, but
that is why the REST API exists.
--
Ryan Sarver
@rsarver <http://twitter.com/rsarver>
On Wed, Mar 16, 2011 at 8:52 PM, M. Edward (Ed) Borasky <
zn...@b
vices that
the user did not intend to send them to.
Users trust us with their content and we want them to have an idea of where
the content goes and how it is going to be used.
Hope that helps clarify.
Ryan
--
Ryan Sarver
@rsarver <http://twitter.com/rsarver>
On Mon, Mar 14, 2011 at
.html?jvi=o5DxVfwU,Job).
Please send along any recommendations of people you think would be a great
fit for the role. We have a few more people starting in two months which I
think will make a big difference.
Ryan
--
Ryan Sarver
@rsarver <http://twitter.com/rsarver>
On Mon, Mar 14, 2011
Tim, sorry for taking so long to follow up. Responses inline below...
--
Ryan Sarver
@rsarver <http://twitter.com/rsarver>
On Mon, Mar 14, 2011 at 4:39 PM, Tim Haines wrote:
> Hey Ryan, Raffi, Taylor, Matt, and other Twitter staff,
>
> I've been confused about Ryan
Steve, thanks for the email. Some inline responses below...
--
Ryan Sarver
@rsarver <http://twitter.com/rsarver>
On Wed, Mar 16, 2011 at 8:24 PM, Steve Eley wrote:
> On Mar 11, 4:18 pm, Ryan Sarver wrote:
> >
> > With more people joining Twitter and accessing the servi
We should have been more clear, but elevated levels of streaming was
included in the previous statement about ending the whitelisting
program. There are open levels for each stream or you can contact Gnip
if you are looking for elevated access for the purposes of data
analysis.
Also as we stated b
Adam, I don't know how else to make this any more clear. As long as you stay
within the rules, your app will not get shut off. We would like to see, and
recommend that, developers focus on bigger opportunities with more potential
than writing another consumer client app.
--
Ryan Sarver
@rs
Tim, thanks for taking the time to write up such an epic email. Give me some
time to parse through it so I can follow up on all the points.
Also, not sure what happened to the thread on api-announce, but I reposted
linking to this thread so people can still find it.
Best, Ryan
--
Ryan Sarver
To be clear, Raffi is clearly articulating the situation. It's a complex
thing and we can't expect to get it perfectly right the first time, so the
dialogue and questions are great.
Raffi is also a much better communicator than I am :)
--
Ryan Sarver
@rsarver <http://twitter.com/r
investors see them as great potential businesses.
Of course statuses/update is still allowed. As is statuses/user_timeline.
We've added more policies and given guidance that we don't think there is a
business in building consumer clients, but none of the APIs have changed.
--
Ryan Sarver
@rsa
David, we are specifically talking about consumer clients. HootSuite and
Seesmic are focused on a more enterprise or marketer audience as I called
out at the bottom of the email.
Best, Ryan
--
Ryan Sarver
@rsarver <http://twitter.com/rsarver>
On Sat, Mar 12, 2011 at 12:32 AM, David W
at the
bottom of the email.
Hope that helps clarify.
Best, Ryan
--
Ryan Sarver
@rsarver <http://twitter.com/rsarver>
On Fri, Mar 11, 2011 at 9:09 PM, Mike Champion wrote:
> Thanks for the clarification Ryan. Two questions:
>
> 1) Do you have a clear definition of what counts a
Hey all, I’d like to give you an update about the state of the Twitter
Platform and hopefully provide some much requested guidance.
Since this time last year, Twitter use has skyrocketed. We’ve grown from 48
million to 140 million tweets a day and we’re registering new accounts at an
all-time rec
Orian,
You should definitely plan on working within 350/hr for the forseeable
future. FWIW, we have watched #newtwitter usage and an average session uses
between 80-120 rq/hr.
Hope that helps clarify. Best, Ryan
--
Ryan Sarver
@rsarver <http://twitter.com/rsarver>
On Thu, Feb 10, 201
y provided. Developers
interested in elevated access to the Twitter stream for the purpose of
research or analytics can contact our partner Gnip for more
information.
As always, we are here to answer questions, and help you build
applications and services that offer value to users.
Ryan
--
Ryan Sarve
Spritzer is currently at 1% of the Firehose, but as the docs say it's
subject to change without notice
On Sun, Nov 21, 2010 at 10:18 PM, M. Edward (Ed) Borasky
wrote:
> Quoting Ryan Sarver :
>>
>> Many of you may wonder what this means for elevated access and
>>
The basic level of statuses/filter will remain unchanged
On Fri, Nov 19, 2010 at 12:06 AM, Scott J wrote:
> I would like to know the answer to this as well. What will the limits
> be on the statuses/filter?
>
> On Nov 17, 9:44 am, Dewald Pretorius wrote:
>> Ryan,
>>
>> The Gnip blog post states
Ed, many developers don't want or can't afford the full Firehose. The
market for Gnip is very large based on the demand that we were unable
to serve.
On Wed, Nov 17, 2010 at 2:04 PM, M. Edward (Ed) Borasky
wrote:
> I quite frankly don't see *any* economic value in a downsampled Firehose.
> Why sh
That's explicitly not true. You are bound by both the Twitter API
Rules and Gnip's TOS
On Wed, Nov 17, 2010 at 1:31 PM, Dewald Pretorius wrote:
> By the way, if you get Twitter data from Gnip, you are not bound to
> the Twitter TOS. Your business and contractual relationship is with
> Gnip, not T
I am consulting some business
>> clients on a range of social media tools and as analytics and the
>> appropriate use of them is a core part of my recommendations I'm following
>> these developments closely and look forward to I hope new competitors in the
>> analytic
://twitter.com/znmeb
>
> "A mathematician is a device for turning coffee into theorems." - Paul Erdos
>
>
> Quoting Ryan Sarver :
>
>> Dewald,
>>
>> The basic levels of all of the streaming APIs -- Spritzer, Follow,
>> Track -- will remain open, free an
the
> appropriate use of them is a core part of my recommendations I'm following
> these developments closely and look forward to I hope new competitors in the
> analytics space soon)
>
> -
> Real Things - http://realthings.posterous.com/
> Slow Brand -
Dewald,
The basic levels of all of the streaming APIs -- Spritzer, Follow,
Track -- will remain open, free and direct from us. Elevated levels
for non-display use will be served through Gnip.
Hope that answers the question.
Best, Ryan
On Wed, Nov 17, 2010 at 5:44 PM, Dewald Pretorius wrote:
>
Companies have leveraged Twitter’s open API to analyze and report on
conversations and sentiment across the network since its inception.
These products have been indispensable in helping brands, marketers
and businesses engage with their customers on Twitter. This is an area
we want to support more
Dave, we really appreciate your note and the kind words. We appreciate all
the time that you guys as developers devote to working on our API, providing
feedback and being an active part of the community. It's great to know that
Taylor, Matt and the rest of the team's hard work pays off sometimes :)
Ed,
As part of the migration we worked with many developers to help them with
the transition and some of them, including our own Android app, had some
extenuating circumstances that made them unable to make the date. For those
few exceptions and extreme cases we granted them a stay of execution as
I wanted to email everyone and give notice that we are going to be holding
off on approving any additional whitelist requests until after the World Cup
is over. We actually paused this last week, so if you haven't gotten a
response, this is why. It will take us a while to get through the backlog
af
Abraham,
Really sorry to hear that we'll be losing you. You have been a HUGE part of
this community for many years and have helped countless developers make
their way through, at times, really choppy waters. We can't thank you enough
for the time and energy you have put into helping developers in
Here is the page that we'll use to coordinate everything this weekend.
Let us know if you have any questions.
https://apiwiki.twitter.com/Annotations-Hackfest-May-25th
Best, rs
Ed, I'm going to post a wiki page shortly to coordinate all the local
and remote groups. Stay tuned, it kicks off at 1pm PST today
On Sat, May 29, 2010 at 11:03 AM, M. Edward (Ed) Borasky
wrote:
> Quoting Ryan Sarver :
>
>> Hey all,
>>
>> Just wanted to update ever
Hey all,
Just wanted to update everyone and let you know that we are going to be
extending the Annotations hackfest to anyone interested, regardless of
whether or not you are able to make it to SF. We'll be providing a preview
of Annotations to anyone interested with the caveat that it might get t
I want to make sure this part is clear -- this policy change isn't meant to
say that we are going to start policing if the content of something a user
tweets is an ad or not. The policy change affects 3rd party services that
were putting ads in the middle of a timeline.
So if Liz is paid by Reebok
Adam,
Thanks for the email and happy to try to clear things up.
1. The TOS go into affect today and section *4. Updates* states that
everyone has 30 days to comply with any changes to the ToS. If you
2. The TOS **does not** restrict the content coming from a user, whether
posted through an app o
Wanted to make sure everyone saw this post from Dick. Please let us know
what questions you have. The actual Terms will be posted shortly.
http://blog.twitter.com/2010/05/twitter-platform.html
Best, Ryan
Raj, Naveen, @tjaap,
Do any of you still have tcp dumps of the calls you were making that were
getting long timeouts?
On Sat, May 8, 2010 at 12:08 AM, Naveen Ayyagari
wrote:
> We see the same huge latency and timeouts as well (our timeouts are
> also at 30 seconds).
>
> We running out of a US da
Thanks for the notice. That is definitely not an expected behavior or
response time. We're investigating the cause and will follow up with
more information as we figure out the cause.
Thanks for reporting it.
Best, rs
On Saturday, May 8, 2010, Naveen Ayyagari wrote:
> We see the same huge laten
Tim,
We're going to work on a smaller one soon. We wanted to make sure the
username of the person you are following was included so that you knew
exactly who you were following when you clicked the button.
Also, we created a new devlist for @Anywhere specific stuff. Check it out:
http://groups.go
I just wanted to jump into the thread and make sure to clarify a few things
being discussed.
1) Re MyPostButler specifically - Brian and the Policy team did the right
thing in responding to Dean and notifying him that his app is currently in
violation of a number of policies that are listed in the
; > room.
> >
> > The conference opens at the Palace of Fine Arts from 9AM to 6PM on April
> > 14th. The schedule features keynotes from Biz Stone, Ev Williams, Ryan
> > Sarver, and Dick Costolo which include announcements and roadmap details.
> >
> > On April 14th
One more from me. People have been asking for specific details around
Tweetie for Mac and I wanted to make sure we clearly message our plans
as we know it. To be clear, Tweetie for the iPhone and it's developer,
Loren Brichter, were the focus of our acquisition, but as part of the
deal we also got
I wanted to email everyone and share my thoughts on the acquisition
from Friday, the communication around it and where we are going from
here. We're incredibly excited about Chirp, and I think an open
dialogue going into it is important. I look forward to meeting many of
you there and continuing th
itter Platform Team* with Ryan Sarver, Doug Williams, Raffi
Krikorian, Mark McBride, Dana Contreras, Isaac Hepworth, Marcel Molina,
Taylor Singletary, Todd Kloots, Wilhelm Bierbaum
*Office Hours: Design/UX *with Doug Bowman, Zhanna Shamis, Britt Selvitelle,
Patrck Ewing, Mark Trammel, Vitor Lourenç
I wanted to send an update that based on everyone's feedback we have
come up with a solution that will allow us to keep
/statuses/public_timeline alive and we will no longer be deprecating
it.
Thanks for jumping into the thread and giving us all of the great
feedback. It helped us prioritize this
This is an announcement that we will be deprecating the *
/statuses/public_timeline* resource as of April 5th (4/5/10). Please let us
know if there are any major concerns.
Thanks, Ryan
We won't be having a live video stream of the event this time around.
We will be in the IRC channel and we'll be using Google Moderator to
take questions from people both at the event and people who are
remote. We'll walk before we run :)
On Fri, Feb 26, 2010 at 12:42 PM, M. Edward (Ed) Borasky
w
Hey folks,
We wanted to let you know that we're hosting a little developer
gathering at our new offices this coming Monday afternoon. The meetup
is meant to be an informal gathering of Twitter developers where we
will be available to hear how we can improve and answer any questions
you have. We'll
Tim,
We are working on this for our forthcoming developer site. Mark should
be posting to the list in the coming days to get feedback from
everyone on what they would like to see.
We know it's needed and look forward to finally having something in place.
Best, Ryan
On Wed, Feb 17, 2010 at 6:54
Jim Fulford
>
> On Feb 16, 1:46 pm, Ryan Sarver wrote:
> > Sorry I am a little late to the thread and there are a lot of topics here
> so
> > I'll do my best to cover them.
> >
> > 1. Email notices - we send out an email for warnings and for suspensions
> &g
Mike,
It's a known issue right now (sorry) but I don't know when a fix is going
out for it.
Best, Ryan
On Tue, Feb 16, 2010 at 8:03 AM, Mike Champion wrote:
> Over the past several weeks, I have never been able to view the
> details of 1 of my OAuth clients, when I go to:
>
> http://twitter.com
Sorry I am a little late to the thread and there are a lot of topics here so
I'll do my best to cover them.
1. Email notices - we send out an email for warnings and for suspensions
every time to the email on record for the account that is being suspended.
If the email isn't up to date or isn't val
Thanks for sending this out.
I did want to send a note about having developers share consumer keys and
secrets with other applications. While we don't have an explicit policy yet
to block this we STRONGLY advise not to hand out your tokens to other
providers for a number of reasons. Most important
p is called Dodo. I'm just sad that I am going to launch
> with the Twitter account @dodo or even @dodoapp – because both are taken and
> unused - but that I'm going to launch with @dodo_app.
>
> That you guys don't see this is a problem makes me think that you don'
Aral,
I'm not sure where you get the idea that we don't care about developers and
that humans aren't involved in the process. Raffi and the rest of the
platform team actively respond to emails from developers at all hours of the
day on both weekdays and weekends.
As for the issue of handing over
Raffi, has walking pneumonia so we're giving him a few days slack time and
we're afraid of what he would write while on meds :)
On Tue, Feb 9, 2010 at 8:48 AM, Raffi Krikorian wrote:
> in progress :P
>
>
> On Tue, Feb 9, 2010 at 12:18 AM, mynetx wrote:
>
>> And where’s the announced post by Raf
Dewald,
1) good idea
2) also a good idea
3) tons :)
On Tue, Feb 9, 2010 at 5:28 AM, Dewald Pretorius wrote:
> Two additions to OAuth that will be very helpful:
>
> 1) When a user removes the application from their connections, Twitter
> should make a callback to my system so that I can delete t
ompletely for many (most?
> > > all?) phones using older browsers, can you please revert to the
> > > previous version, and then stage a new version somewhere else that we
> > > can help you test?
> >
> > > -- Charles
> >
> > > On Feb 3,
Following up on my earlier email. I jumped the gun and the rollback never
actually happened :)
However, we are getting some reports of the buttons not functioning in a
number of browsers and are working on a fix.
Best, Ryan
On Thu, Feb 4, 2010 at 3:27 PM, Ryan Sarver wrote:
> We'v
h a 6.1 & 6.5
> device.
>
> On Feb 3, 6:16 pm, Ryan Sarver wrote:
> > FINALLY!
> >
> > An update has just gone live that fixes rendering of the OAuth screens
> for
> > most mobile devices. We also fixed a few small nagging things like the
> > default actio
Michael,
It is definitely on our near-term roadmap, but we've gotten backed up on a
few other things. So it is still coming, but I don't have an exact date for
you. Social graph relief is neigh :)
Best, Ryan
On Wed, Feb 3, 2010 at 3:39 PM, Michael Steuer wrote:
> Hi Raffi et al,
>
> Is there
Good news. A mobile-friendly version of the OAuth page is due to be
deployed next week (finally!:). We look forward to your feedback on
the new screens when they are ready.
Also, we currently block any custom protocol URLs from being
registered as a callback to protect against XSS attacks. However
Just wanted to give everyone a heads up now that we have officially
announced the dates for Chirp and made the first 200 tickets available
for purchase at http://chirp.twitter.com. Chirp will be a two day
event being held on April 14th and 15th and over 800 tickets will be
available in total. You c
Duane,
I've been able to follow up with our lawyers and they confirmed that it is
ok to include "Twitter" in the name of libraries that developers build.
Sorry it took so long to follow up, but I wanted to make sure we got a
strong, final answer back before responding.
Best, Ryan
On Fri, Dec 4,
Dewald,
I appreciate that the response email was probably not helpful to you, but
there are reasons that the new zendesk-based system are greatly beneficial
to the community. Surely we can tailor some of the responses so they are
more specific to your inquiry (and we will do that), but it's import
Hey all,
Now that the dust has settled a bit and we are in the midst of the holidays
I wanted to email everyone and provide some more details on the
announcements we made a few weeks ago at LeWeb.
*50,000 apps*
We are continually amazed by all the incredible work the ecosystem does as a
whole and
Just wanted to follow up with everyone and let you know we are still on this
and haven't forgotten about the thread. Hopefully will have an answer for
you soon.
Best, Ryan
2009/12/5 Ryan Sarver
> Duane,
>
> We definitely don't want to be sending any "nastygrams"
We just posted a status update to blog.twitter.com which you can find
here: http://blog.twitter.com/2009/12/update-on-last-nights-dns-disruption.html
Please let us know if you have any questions.
Best, Ryan
On Thu, Dec 17, 2009 at 11:28 PM, Ryan Sarver wrote:
> Just wanted to drop an email
Just wanted to drop an email to everyone and let you know that we are
investigating the issue and will follow up with more details as we
determine the cause and are able to share information.
Thanks for your patience, Ryan
Duane,
We definitely don't want to be sending any "nastygrams", especially for
something that helps the community. I put a note into our legal / marks
department so that I can get an answer back to you and everyone else. Please
bear with us as it could take a bit, but I'll get you an answer.
Best
Just an update from our end: I am still working with our General Counsel to
get answers to the questions, but it's going to take a bit. So please bear
with us but we'll get an update to you in the coming weeks after we get back
from LeWeb.
Thanks, Ryan
On Tue, Nov 24, 2009 at 9:12 AM, DeWitt Clin
Tim,
can you provide us with your IP so we can look into it?
Thanks, Ryan
On Wednesday, November 25, 2009, timwhitlock
wrote:
> Has anyone found their existing code suddenly getting OAuth failures?
> I'm getting a 401 ("Failed to validate oauth signature and token")
>
> Normally I'd assume that
DeWitt,
Thanks for the email. These are all great questions and I want to make
sure I get all the appropriate answers for you and other people on the
thread so it's clear and transparent. Let me work internally to make
sure we get answers to these and get back to you.
The more general answer is t
Thanks for the idea guys. We'll consider it and see if we can put
something together to help spread awareness of apps.
Best, Ryan
On Mon, Nov 23, 2009 at 12:36 AM, Shyam wrote:
> In that case, twitter could use one of its official account (or create a new
> one), which tweets this.
> --
> Yours,
Wanted to email everyone to point out the subtle, but important change
on twitter.com. Today we have rolled out an update that changes the
text above the "tweet box" from "What are you doing?" to say "What's
happening?". I could try to explain the reasons for the change, but
that's Biz's job :) You
Cross posting here from status.twitter.com:
"On Tuesday, November 17th, we will be upgrading network equipment
between 11p and 1a Pacific. The site may be unavailable for short
periods in that window."
Let us know if you have any questions.
Ryan
I just wanted to add some additional color to this as it didn't come
through well in our email announcement. The actual change is happening
Monday morning. Our email unfortunately said "today" as we were
planning to send it the day of, but we ended up sending it earlier to
give more notice and for
You can request whitelisting here: http://twitter.com/help/request_whitelisting
On Wed, Nov 4, 2009 at 11:27 AM, twittme_mobi wrote:
>
> Hello,
>
> Sorry for posting this again. but I have problems with my mobile
> twitter site, which is
> in production since 4 months now and alreay widely used.
Nish,
It's a known issue with our whitelisting ticket system. As Chris said,
if you email a...@twitter.com the team can follow up and provide you
with more information.
Best, Ryan
On Thu, Nov 5, 2009 at 10:47 AM, Nish wrote:
>
> Hi,
>
> Today i submitted by application to twitter stating that
Today on the Twitter Blog we announced that we will be changing search
results for trending topics to improve the quality. It used to be that
trends were a great way to quickly see what was going on on Twitter,
but they have begun to get fairly noisy due to the sheer volume of
tweets. We wanted to
Guys,
Thanks for the reports. We are aware of the elevated 50xs and are
working hard to bring it back down to normal. I don't have a specific
timeline that I can give at this point, but we'll update you regularly
if this continues.
I've update @twitterapi with the latest status as well:
http://t
Rich,
Thanks for the report. Can you elaborate on which problem you are
seeing and can you send us the HTML that is being output?
Ryan
On Mon, Oct 19, 2009 at 9:31 AM, Rich wrote:
>
> We're getting problems on the iPhone clients again, it looks like the
> old 200 error might have cropped up ag
Dewald,
Can you produce some TCP dumps and requests with headers so we can better debug?
Thanks, Ryan
On Sun, Oct 18, 2009 at 12:05 PM, Dewald Pretorius wrote:
>
> I'm seeing lots of 502's now. Is the API overloaded?
>
> Dewald
>
> On Oct 18, 2:58 pm, Ryan Sarver
hat exactly
> happened?
> Thanks.
> Michael
>
>
>
> On Oct 18, 2009, at 10:53 AM, Atul Kulkarni wrote:
>
> Works Fine... Duluth, MN.
>
> On Sun, Oct 18, 2009 at 12:51 PM, Ryan Sarver wrote:
>>
>> I wanted to check in and see if everyone is back to no
I wanted to check in and see if everyone is back to normal? We think
things have been fixed but its hard to confirm without your help.
Let me know if you are still experiencing any issues and if so, where
you are located.
Best, Ryan
On Sun, Oct 18, 2009 at 10:48 AM, Dewald Pretorius wrote:
>
>
Dave,
It depends on which button you are seeing. A lot of blogs and sites have
integrated Sign in with Twitter. It allows you to easily leverage Twitter
for authentication and to link their identity on your site.
http://apiwiki.twitter.com/Sign-in-with-Twitter
Check it out and let us know if you
I appreciate the healthy debate here over the issue, and we all read the
threads in this forum, but the reality is we don't have the time to respond
to every inquiry. Chad has done a great job in making sure explicit
questions get answered and we are happy to have an open discussion about the
topic
ll of this, if the user has their flag off and we
> submit the location with their tweet will that location information be
> saved with the tweet for future use or disgarded due to the setting
> being off?
>
> Axthelm
>
> On Oct 9, 8:10 pm, Ryan Sarver wrote:
>> Ther
Hey everyone,
I wanted to email the list to start gathering some feedback on how we
can improve the OAuth workflow. As we have discussed in the past,
Basic Auth is going to be deprecated at some point in the future for
OAuth and we want to make sure we improve the experience to meet
everyone's ne
Isaiah,
We are definitely interested in hearing what type of workflow you
would prefer for OAuth-ing desktop applications. We want to make the
experience the best it can be and look for your feedback on how we can
improve it.
Let me start another thread so we can make sure to capture everyone's
There is going to be a read-only flag on the
object that denotes whether or not the user has enabled geolocation.
For security reasons, the user will need to come to twitter.com to
change the setting.
Best, Ryan
On Fri, Oct 9, 2009 at 8:18 AM, Axthelm wrote:
>
> On that note, is it known if t
Ok, who broke Twitter? fess up... :)
On Thu, Oct 8, 2009 at 8:54 AM, Rich wrote:
>
> No problems, I think it's more than a few, try this search
>
> http://search.twitter.com/search?q=twitter+broken
>
> On Oct 8, 4:49 pm, Ryan Sarver wrote:
> > Thanks for p
Thanks for pinging the list with this and confirming a few people are seeing
it. I will follow up internally to figure out what is going on and report
back here.
Thanks again, Ryan
On Thu, Oct 8, 2009 at 8:45 AM, stephane wrote:
>
> Echo, you are not alone
>
> Stephane
> @sphilipakis
> http://ww
To give everyone another update, we are still on track to trigger
Twitpocalypse II tomorrow (Tuesday 9/22) at 11:30am PST. We are trying
to do it as early in the day as we can on our side to accommodate
developers in other timezones.
For those of you unaware of what the Twitpocalypse is (hopefull
Hardip,
Thanks for your email. Our intent is to stop spamming accounts. Your
use does not fall into that category, but its good practice to be
judicious when including a lot of links in your updates as it triggers
a lot of the filters that try to catch spam.
Best, Ryan
On Tue, Sep 15, 2009 at 7
WyoKnott,
Thanks for your email. We really appreciate the candid feedback and
definitely is not something we want to see happening. I would like to
hear more about what you mean by "not stable enough" and what specific
issues we can work on that would get you to consider Twitter a
platform worthy
f it is Twitter's bug and not my own.
>
> So... ETA??
>
> Thanks!
>
> On Sep 13, 5:49 pm, Ryan Sarver wrote:
>> Waldron,
>>
>> Thanks for the email. I am working with our team internally to track
>> down the issue and figure out how to resolve it
Waldron,
Thanks for the email. I am working with our team internally to track
down the issue and figure out how to resolve it. I will get back to
you with an update shortly, but know that we are listening and working
on this.
Best, Ryan
On Sun, Sep 13, 2009 at 8:55 AM, Waldron Faulkner
wrote:
es, 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, 12
1 - 100 of 136 matches
Mail list logo
