Doug,

Patience is key here, I understand that, but it seems to me (and I'm
sure to others) that what you had in place was working.
If you are rolling out a new feature or something, fine, but do it on
a test server while the rest of us can continue to develop our new
apps and have our existing ones keep on working.

By the way, since I'm here, I need Twitter's permission to adapt the
terms of service (much like you did from Flickr). Thanks.

Michael
Developer
http://twitter.com/mobasoft


On Apr 22, 11:37 am, Doug Williams <d...@twitter.com> wrote:
> Shannon,
> More details to come. Thank you for your patience.
>
> Doug Williams
> Twitter API Supporthttp://twitter.com/dougw
>
> On Wed, Apr 22, 2009 at 8:43 AM, Shannon Whitley
> <shannon.whit...@gmail.com>wrote:
>
>
>
> > Hi, Doug.  I think we understand the part about "authenticate" being
> > down, but oAuth isn't working at all right now.
>
> > On Apr 22, 8:33 am, Doug Williams <d...@twitter.com> wrote:
> > > The feature was disabled over the weekend. It will hopefully be
> > > restore within a day. That is all we can say at this time, but more
> > > details will flow after restoration. We appreciate your patience.
>
> > > Doug
>
> > > On 4/22/09, Dossy Shiobara <do...@panoptic.com> wrote:
>
> > > > On 4/22/09 11:15 AM, iematthew wrote:
> > > >> If I'm not mistaken, OAuth is still in public Beta. Or did I miss the
> > > >> memo? (wouldn't have been the first time). I doubt it is wise at this
> > > >> point to push OAuth features live to the public. :)
>
> > > > You forgot to put the new cover page on your TPS report.
>
> > > > --
> > > > Dossy Shiobara              | do...@panoptic.com |http://dossy.org/
> > > > Panoptic Computer Network   |http://panoptic.com/
> > > >    "He realized the fastest way to change is to laugh at your own
> > > >      folly -- then you can let go and quickly move on." (p. 70)
>
> > > --
> > > Sent from my mobile device
>
> > > Doug Williams
> > > Twitter API Supporthttp://twitter.com/dougw

Reply via email to