[twitter-dev] Re: User tag inside users/show
20 views
Skip to first unread message
Message has been deleted
Rich
May 5, 2010, 4:39:21 PM5/5/10
to Twitter Development Talk
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
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
Orian Marx (@orian)
May 5, 2010, 4:40:39 PM5/5/10
to Twitter Development Talk
This totally just broke my app as well. Twitter please change this
back ASAP!
back ASAP!
Taylor Singletary
May 5, 2010, 4:42:53 PM5/5/10
to twitter-deve...@googlegroups.com
Looking into it. Sorry about the chafe. While the versioning in the API is important as noted, we continually stress that API clients need to be resilient to new fields appearing on any node.
Rich
May 5, 2010, 4:45:15 PM5/5/10
to Twitter Development Talk
My app is usually pretty resiliant to this, however I didn't expect a
second user tag
On May 5, 9:42 pm, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
second user tag
On May 5, 9:42 pm, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
> Looking into it. Sorry about the chafe. While the versioning in the API is
> important as noted, we continually stress that API clients need to be
> resilient to new fields appearing on any node.
>
> Taylor Singletary
> Developer Advocate, Twitterhttp://twitter.com/episod
> important as noted, we continually stress that API clients need to be
> resilient to new fields appearing on any node.
>
> Taylor Singletary
Taylor Singletary
May 5, 2010, 4:48:06 PM5/5/10
to twitter-deve...@googlegroups.com
Admittedly, a very odd condition and a side effect our tests didn't appear to pick up.
Taylor Singletary
Developer Advocate, Twitter
Taylor Singletary
Developer Advocate, Twitter
Orian Marx (@orian)
May 5, 2010, 4:49:33 PM5/5/10
to Twitter Development Talk
This broke for me because my app has logic that handles instantiation
of User objects as it comes across them in XML. The addition of a new
user node that contained nothing but an <id> broke this. Sorry Taylor
but this is different than adding a new field that doesn't already
have an existing meaning / structure.
On May 5, 4:42 pm, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
of User objects as it comes across them in XML. The addition of a new
user node that contained nothing but an <id> broke this. Sorry Taylor
but this is different than adding a new field that doesn't already
have an existing meaning / structure.
On May 5, 4:42 pm, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
> Looking into it. Sorry about the chafe. While the versioning in the API is
> important as noted, we continually stress that API clients need to be
> resilient to new fields appearing on any node.
>
> Taylor Singletary
> Developer Advocate, Twitterhttp://twitter.com/episod
> important as noted, we continually stress that API clients need to be
> resilient to new fields appearing on any node.
>
> Taylor Singletary
Taylor Singletary
May 5, 2010, 4:59:54 PM5/5/10
to twitter-deve...@googlegroups.com
Agreed
Raffi Krikorian
May 5, 2010, 5:02:47 PM5/5/10
to twitter-deve...@googlegroups.com
versioning has absolutely nothing to do with this - this is clearly a bug.--
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi
Orian Marx (@orian)
May 5, 2010, 5:11:08 PM5/5/10
to Twitter Development Talk
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.
>
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.
>
Raffi Krikorian
May 5, 2010, 5:21:59 PM5/5/10
to twitter-deve...@googlegroups.com
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.
Rich
May 5, 2010, 5:27:32 PM5/5/10
to Twitter Development Talk
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
than a bug :) Of course we all get unintentional bugs from time to
time
Message has been deleted
Sami
May 5, 2010, 11:07:35 PM5/5/10
to Twitter Development Talk
How long does it take for the change to propagate. My application is
still down along with every application using the twitter4j java
library
Thanks
still down along with every application using the twitter4j java
library
Thanks
Rich
May 6, 2010, 2:37:10 AM5/6/10
to Twitter Development Talk
Excellent, thanks guys seems to be working fine now :)
ericdoe...@gmail.com
May 6, 2010, 6:28:53 AM5/6/10
to Twitter Development Talk
I'm still seeing this problem on statuses as recent as 5/6 @ 7:45 AM
UTC, or three hours ago for me. For example, as of this moment,
http://api.twitter.com/1/users/show/shanselman.xml is exhibiting this
issue.
On May 5, 8: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
> > > Twitter Platform Teamhttp://twitter.com/raffi- Hide quoted text -
>
> - Show quoted text -
UTC, or three hours ago for me. For example, as of this moment,
http://api.twitter.com/1/users/show/shanselman.xml is exhibiting this
issue.
On May 5, 8: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
>
> - Show quoted text -
Message has been deleted
BenoitX
May 6, 2010, 6:06:03 AM5/6/10
to Twitter Development Talk
Still not working here... (based in London if that helps).
> > Thanks- Hide quoted text -
rohit
May 6, 2010, 4:04:56 AM5/6/10
to Twitter Development Talk
My application is still not working?
I use Twitter4j and it is still giving a problem.
Regards,
Rohit
I use Twitter4j and it is still giving a problem.
Regards,
Rohit
Raul
May 6, 2010, 1:50:18 AM5/6/10
to Twitter Development Talk
We still see this issue on every request at http://streamd.in , Also
all other apps that use twitter4j are experiencing this issue.
On May 5, 6:04 pm, Taylor Singletary <taylorsinglet...@twitter.com>
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:
> 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:
Rich
May 6, 2010, 7:51:28 AM5/6/10
to Twitter Development Talk
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
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
Raffi Krikorian
May 6, 2010, 8:23:57 AM5/6/10
to twitter-deve...@googlegroups.com
i'm currently looking into this now.
irhetoric
May 6, 2010, 12:12:00 PM5/6/10
to Twitter Development Talk
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.
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.
Taylor Singletary
May 6, 2010, 12:19:21 PM5/6/10
to twitter-deve...@googlegroups.com
We're working on getting this fixed as soon as we can.
melissa
May 6, 2010, 4:01:45 PM5/6/10
to Twitter Development Talk
Any ETA? We need to know how long, and propagation time, or we will
have to deploy a workaround. It's been about 24 hours now, and t is
affecting our customers.
Thanks, Melissa, Awareness
On May 6, 12:19 pm, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
have to deploy a workaround. It's been about 24 hours now, and t is
affecting our customers.
Thanks, Melissa, Awareness
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
>
> Taylor Singletary
Taylor Singletary
May 6, 2010, 4:36:38 PM5/6/10
to twitter-deve...@googlegroups.com
We think this should be all resolved out within the next few hours -- already hearing reports of some relief for a number of Twitter clients. We're slowly expiring the cache on several objects in the system to clear this up rather than waiting for them to clear on their own. This has to be done with great care.
Taylor Singletary
Developer Advocate, Twitter
Thanks for the patience and apologies for the effect this has on your users.
Taylor Singletary
Developer Advocate, Twitter
irhetoric
May 6, 2010, 9:09:13 PM5/6/10
to Twitter Development Talk
I'm back up -- thanks for the quick response.
On May 6, 1:36 pm, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
On May 6, 1:36 pm, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
> We think this should be all resolved out within the next few hours --
> already hearing reports of some relief for a number of Twitter clients.
> We're slowly expiring the cache on several objects in the system to clear
> this up rather than waiting for them to clear on their own. This has to be
> done with great care.
>
> Thanks for the patience and apologies for the effect this has on your users.
>
> Taylor Singletary
> Developer Advocate, Twitterhttp://twitter.com/episod
> already hearing reports of some relief for a number of Twitter clients.
> We're slowly expiring the cache on several objects in the system to clear
> this up rather than waiting for them to clear on their own. This has to be
> done with great care.
>
> Thanks for the patience and apologies for the effect this has on your users.
>
> Taylor Singletary
Message has been deleted
melissa
May 7, 2010, 10:41:55 AM5/7/10
to Twitter Development Talk
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>
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
>
> > We're working on getting this fixed as soon as we can.
>
> > Taylor Singletary
Taylor Singletary
May 7, 2010, 10:51:46 AM5/7/10
to twitter-deve...@googlegroups.com
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
May 7, 2010, 12:03:34 PM5/7/10
to twitter-deve...@googlegroups.com
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.
melissa
May 7, 2010, 2:14:49 PM5/7/10
to Twitter Development Talk
Thanks Taylor. Basically, pre-exisiting users appear to fail during
the verify credentials call. It seems that we're still getting the
spurious userid. We use Tweetsharp. We tried it with new users and
it works, and is able to de-serialize the response. We are getting
the token fine - it is definitely failing in verification. We can
give you an example shortly, but if this sounds like the caching would
fix it, any ETA on when cache expiration would be completed, or
anything you can do to clear the cache? We can give you information
telling you what users/etc if you can manually clear something.
Thanks so much for replying. BTW, check out our app sometime, it's
pretty cool ;).
Melissa, Awareness Inc.
On May 7, 12:03 pm, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
the verify credentials call. It seems that we're still getting the
spurious userid. We use Tweetsharp. We tried it with new users and
it works, and is able to de-serialize the response. We are getting
the token fine - it is definitely failing in verification. We can
give you an example shortly, but if this sounds like the caching would
fix it, any ETA on when cache expiration would be completed, or
anything you can do to clear the cache? We can give you information
telling you what users/etc if you can manually clear something.
Thanks so much for replying. BTW, check out our app sometime, it's
pretty cool ;).
Melissa, Awareness Inc.
On May 7, 12:03 pm, 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
>
> 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
>
> On Fri, May 7, 2010 at 7:51 AM, Taylor Singletary <
>
> 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
>
> > 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
>
melissa
May 7, 2010, 2:56:32 PM5/7/10
to Twitter Development Talk
Taylor, one of our users is now working, I guess we are on the last
servers.....not sure if there is any timeframe we can tell our
customers hen we know this will be completed.
Thanks, Melissa
www.awarenessnetworks.com
Follow us on Twitter <http://twitter.com/awarenessinc>
On May 7, 12:03 pm, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
servers.....not sure if there is any timeframe we can tell our
customers hen we know this will be completed.
Thanks, Melissa
www.awarenessnetworks.com
Follow us on Twitter <http://twitter.com/awarenessinc>
On May 7, 12:03 pm, 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
>
> 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
>
> On Fri, May 7, 2010 at 7:51 AM, Taylor Singletary <
>
> 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
>
> > 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
>
Message has been deleted
catalyst media
May 8, 2010, 1:21:38 PM5/8/10
to Twitter Development Talk
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:
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
>
> 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
>
> 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: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
>
Reply all
Reply to author
Forward
Message has been deleted
0 new messages