hi!

are you still, as of monday 10 may, having this problem?  if so, please send
me an email directly with a list of screen_names that you are seeing this
problem on, and i can personally track it down.

i'll then also update this mailing list.

thanks!

On Sat, May 8, 2010 at 6:21 PM, catalyst media <
catalystmediastud...@gmail.com> wrote:

> Is this fixed yet? I'm still having issues with this problem. Is
> anyone else still experiencing issues with it?
>
> Thanks!
> Paul
>
> On May 7, 10:03 am, Taylor Singletary <taylorsinglet...@twitter.com>
> wrote:
> > Melissa,
> >
> > We had to pause the cache expiration for a little while yesterday
> afternoon,
> > but it resumed last night. It's going to continue working through the
> queue
> > today.
> >
> > Taylor Singletary
> > Developer Advocate, Twitterhttp://twitter.com/episod
> >
> > On Fri, May 7, 2010 at 7:51 AM, Taylor Singletary <
> >
> >
> >
> > taylorsinglet...@twitter.com> wrote:
> > > Hi Melissa,
> >
> > > Sorry to hear you are still down. Can you send along some examples of
> > > payloads still including the embedded user object and the URL used to
> access
> > > it?
> >
> > > Taylor Singletary
> > > Developer Advocate, Twitter
> > >http://twitter.com/episod
> >
> > > On Fri, May 7, 2010 at 7:41 AM, melissa <melissaleff...@gmail.com>
> wrote:
> >
> > >> Sorry, missed your last reply.  Anyway, we are still down.  I assume
> > >> propagation *should* have happened - what can we do to debug this?
> >
> > >> On May 7, 10:39 am, melissa <melissaleff...@gmail.com> wrote:
> > >> > Guys, we really need an update on this.  I understand if you don;t
> > >> > have a resolution, but not responding at all is not cool.  Looks
> like
> > >> > maybe Tweetsharp, the API we use, thinks the problem is resolved,
> but
> > >> > our customers are still DOWN.  Do we need to redeploy a workaround?
> > >> > What is the ETA?
> >
> > >> > On May 6, 12:19 pm, Taylor Singletary <taylorsinglet...@twitter.com
> >
> > >> > wrote:
> >
> > >> > > We're working on getting this fixed as soon as we can.
> >
> > >> > > Taylor Singletary
> > >> > > Developer Advocate, Twitterhttp://twitter.com/episod
> >
> > >> > > On Thu, May 6, 2010 at 9:12 AM, irhetoric <karst...@microsoft.com
> >
> > >> wrote:
> > >> > > > This appears to still be broken.  It affects anyone using the
> > >> > > > TweetSharp library as well. There's a workaround (http://
> > >> > > > tweetsharp.codeplex.com/Thread/View.aspx?ThreadId=211712), but
> > >> > > > hopefully it will be fixed soon so that we don't have to
> redeploy
> > >> with
> > >> > > > the workaround.
> >
> > >> > > > On May 6, 5:23 am, Raffi Krikorian <ra...@twitter.com> wrote:
> > >> > > > > i'm currently looking into this now.
> >
> > >> > > > > On Thu, May 6, 2010 at 4:51 AM, Rich <rhyl...@gmail.com>
> wrote:
> > >> > > > > > Yep looks like I spoke to soon, many of my users are still
> > >> seeing this
> > >> > > > > > issue.  I've actually handled it but Apple are now taking
> about
> > >> a week
> > >> > > > > > to approve updates
> >
> > >> > > > > > On May 6, 6:50 am, Raul <raulr...@gmail.com> wrote:
> > >> > > > > > > We still see this issue on every request athttp://
> streamd.in,
> > >> Also
> > >> > > > > > > all other apps that use twitter4j are experiencing this
> issue.
> >
> > >> > > > > > > On May 5, 6:04 pm, Taylor Singletary <
> > >> taylorsinglet...@twitter.com>
> > >> > > > > > > wrote:
> >
> > >> > > > > > > > This should now be fixed, though it may take a little
> while
> > >> for the
> > >> > > > > > cache to
> > >> > > > > > > > completely clear the labyrinth.
> >
> > >> > > > > > > > Let us know if you're still having wide spread problems.
> >
> > >> > > > > > > > Thanks!
> > >> > > > > > > > Taylor
> >
> > >> > > > > > > > On Wed, May 5, 2010 at 2:27 PM, Rich <rhyl...@gmail.com
> >
> > >> wrote:
> > >> > > > > > > > > Cool, thanks Raffi, I was more concerned if it was
> > >> intentional
> > >> > > > rather
> > >> > > > > > > > > than a bug :)  Of course we all get unintentional bugs
> > >> from time
> > >> > > > to
> > >> > > > > > > > > time
> >
> > >> > > > > > > > > On May 5, 10:21 pm, Raffi Krikorian <
> ra...@twitter.com>
> > >> wrote:
> > >> > > > > > > > > > my stance on versioning is for when something has
> > >> changed that
> > >> > > > > > breaks
> > >> > > > > > > > > > backwards compatibility.  in this case, we haven't
> > >> broken
> > >> > > > backwards
> > >> > > > > > > > > > compatibility, but a regression was introduced.
> > >>  regressions
> > >> > > > can
> > >> > > > > > get
> > >> > > > > > > > > > introduced in a variety of different ways, and
> across a
> > >> variety
> > >> > > > of
> > >> > > > > > > > > different
> > >> > > > > > > > > > properties unfortunately.  software projects do
> their
> > >> best to
> > >> > > > avoid
> > >> > > > > > them
> > >> > > > > > > > > --
> > >> > > > > > > > > > but its orthogonal to versioning....
> >
> > >> > > > > > > > > > either way - we're working on a fix.
> >
> > >> > > > > > > > > > On Wed, May 5, 2010 at 2:11 PM, Orian Marx (@orian)
> <
> > >> > > > > > or...@orianmarx.com
> > >> > > > > > > > > >wrote:
> >
> > >> > > > > > > > > > > Well, I'm not sure if Rich was referring to the
> output
> > >> per se
> > >> > > > or
> > >> > > > > > > > > > > rather that this bug was probably tied to the
> > >> skip_user
> > >> > > > parameter
> > >> > > > > > that
> > >> > > > > > > > > > > was just added to timelines... which one could
> argue
> > >> is a
> > >> > > > > > candidate
> > >> > > > > > > > > > > for versioning.
> >
> > >> > > > > > > > > > > On May 5, 5:02 pm, Raffi Krikorian <
> ra...@twitter.com
> >
> > >> > > > wrote:
> > >> > > > > > > > > > > > versioning has absolutely nothing to do with
> this -
> > >> this is
> > >> > > > > > clearly a
> > >> > > > > > > > > > > bug.
> >
> > >> > > > > > > > > > > > On Wed, May 5, 2010 at 1:39 PM, Rich <
> > >> rhyl...@gmail.com>
> > >> > > > > > wrote:
> > >> > > > > > > > > > > > > Oh I'll add, I thought the point of a
> versioned
> > >> API was
> > >> > > > that
> > >> > > > > > this
> > >> > > > > > > > > sort
> > >> > > > > > > > > > > > > of thing didn't happen?
> >
> > >> > > > > > > > > > > > > On May 5, 9:37 pm, Rich <rhyl...@gmail.com>
> > >> wrote:
> > >> > > > > > > > > > > > > > I noticed today inside the user tags an
> extra
> > >> user tag
> > >> > > > has
> > >> > > > > > > > > appeared
> >
> > >> > > > > > > > > > > > > > We now have user->status->user
> >
> > >> > > > > > > > > > > > > > This is causing a crash on my app and number
> of
> > >> engines
> > >> > > > > > I've
> > >> > > > > > > > > tried.
> > >> > > > > > > > > > > > > > When did this get added and did I miss the
> > >> > > > notification?
> >
> > >> > > > > > > > > > > > > > Many thanks
> > >> > > > > > > > > > > > > > Richard
> >
> > >> > > > > > > > > > > > --
> > >> > > > > > > > > > > > Raffi Krikorian
> > >> > > > > > > > > > > > Twitter Platform Teamhttp://twitter.com/raffi
> >
> > >> > > > > > > > > > --
> > >> > > > > > > > > > Raffi Krikorian
> > >> > > > > > > > > > Twitter Platform Teamhttp://twitter.com/raffi
> >
> > >> > > > > --
> > >> > > > > Raffi Krikorian
> > >> > > > > Twitter Platform Teamhttp://twitter.com/raffi
>



-- 
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi

Reply via email to