(I don't /expect/ anyone here to fix this - I mostly wanted to let people
know what I'm seeing and see what discussion arises around the problem.)
I was just working a support issue for a customer when I stumbled across
something really quite maddening and concerning when it comes to PuSH support
on Buzz: The rel="self" link in a user's "Posted" feed points to a different
feed with completely separate content.
Example:
"http://buzz.googleapis.com/feeds/108832773152747423283/public/posted";
references
"https://www.googleapis.com/buzz/v1/activities/108832773152747423283/@public";
as "self".
Not one piece of content in
"https://www.googleapis.com/buzz/v1/activities/108832773152747423283/@public";
exists in the original feed in the same form. (Some source content exists,
but titles and content are wholly different.)
Obviously "self" is being set incorrectly in this instance, and I think it
raises some questions about how a situation like this should be handled.
Right now, when I retrieve the feed manually (which is still required, even in
the spec) I'm ending up with two sets of completely unrelated content.
At least for this user, I feel like there's no real option other than to
disable PuSH for their feed, and investigate whether this is a problem
site-wide.
--
Jay Rossiter | Jack of All Trades
[email protected] <mailto:[email protected]> | Phone: 503.896.6187 | Fax: 503.235.2216
Website: dlvr.it <http://dlvr.it/> | RSS: blog.dlvr.it <http://blog.dlvr.it/>
Community: community.dlvr.it <http://community.dlvr.it/> | Support:
support.dlvr.it <http://support.dlvr.it/>
