Hi John, I replied directly to you, but didn't realise it was also sent to the dev list.
Basically it seems to have gone now as I see the cert is a wildcard one, this morning both the iPhone and Firefox were complaining that the cert was for twitter.com and not api.twitter.com Richard On Oct 16, 11:04 am, John Adams <j...@twitter.com> wrote: > Could you let us know what errors you are seeing via SSL on > api.twitter.com? I'd like to investigate. > > I do not see any SSL errors under Firefox and/or Safari on 10.5 nor > 10.6. > > -j > > On Oct 16, 2009, at 1:00 AM, Marcel Molina wrote: > > > > > > > I've alerted our ops team. Thanks for the heads up. > > > On Fri, Oct 16, 2009 at 12:56 AM, Rich <rhyl...@gmail.com> wrote: > > >> I did notice though that api.twitter.com doesn't have a valid SSL > >> certificate so any clients using the API over SSL will error out too. > > >> On Oct 16, 8:49 am, Marcel Molina <mar...@twitter.com> wrote: > >>> The OAuth endpoints aren't strictly speaking part of the REST API. > > >>>http://api.twitter.com/oauth/authorizeandfamily works at the api > >>> subdomain, but those paths aren't versioned (though maybe they > >>> should > >>> be...). As for search...one step at a time ;-) But thanks for > >>> noticing. > > >>> On Fri, Oct 16, 2009 at 12:46 AM, Rich <rhyl...@gmail.com> wrote: > > >>>> Great news guys, I noticed that the search and oauth API's aren't > >>>> in > >>>> the version one API stream though. > > >>>> Is this intentional? > > >>> -- > >>> Marcel Molina > >>> Twitter Platform Teamhttp://twitter.com/noradio > > > -- > > Marcel Molina > > Twitter Platform Team > >http://twitter.com/noradio > > -- > John Adams > Twitter Operations > j...@twitter.com > Follow me: @netik
