I didn't notice this until I subscribed to my Buzz feed, but it looks like GReader's version of Atom feeds don't include a lot of important information. In the case of Buzz feeds, the most notable absences are the Atom threading, MediaRSS, and activity stream extensions. Are these expected to be supported at some point?
On Thu, Feb 11, 2010 at 1:00 PM, Nick Bradbury <nick.bradb...@gmail.com> wrote: > I didn't notice this until I subscribed to my Buzz feed, but it looks > like GReader's version of Atom feeds don't include a lot of important > information. In the case of Buzz feeds, the most notable absences are > the Atom threading, MediaRSS, and activity stream extensions. Are > these expected to be supported at some point?
Assuming something like this works for you, it should be deployed sometime this week. It will be served under a different path (/reader/atom/hifi/.., most likely), since these responses are quite large and I'd rather have only clients that care about the extra elements get them.
On Mon, Feb 15, 2010 at 11:15 AM, Mihai Parparita <mih...@google.com> wrote: > Hi Nick,
> I'll see if I can add a "pass-through" mode for Reader's Atom output > where we preserve unknown (to Reader) elements that appeared in the > source feed.
> Mihai
> On Thu, Feb 11, 2010 at 1:00 PM, Nick Bradbury <nick.bradb...@gmail.com> wrote: >> I didn't notice this until I subscribed to my Buzz feed, but it looks >> like GReader's version of Atom feeds don't include a lot of important >> information. In the case of Buzz feeds, the most notable absences are >> the Atom threading, MediaRSS, and activity stream extensions. Are >> these expected to be supported at some point?
> Assuming something like this works for you, it should be deployed > sometime this week. It will be served under a different path > (/reader/atom/hifi/.., most likely), since these responses are quite > large and I'd rather have only clients that care about the extra > elements get them.
> Mihai
> On Mon, Feb 15, 2010 at 11:15 AM, Mihai Parparita <mih...@google.com> wrote: >> Hi Nick,
>> I'll see if I can add a "pass-through" mode for Reader's Atom output >> where we preserve unknown (to Reader) elements that appeared in the >> source feed.
>> Mihai
>> On Thu, Feb 11, 2010 at 1:00 PM, Nick Bradbury <nick.bradb...@gmail.com> wrote: >>> I didn't notice this until I subscribed to my Buzz feed, but it looks >>> like GReader's version of Atom feeds don't include a lot of important >>> information. In the case of Buzz feeds, the most notable absences are >>> the Atom threading, MediaRSS, and activity stream extensions. Are >>> these expected to be supported at some point?
Sorry for not seeing this until now - been sidetracked with NG enterprise work this week. Are the missing elements only included when specifically requesting the "hi-fi" version of the feed, or are they also included in the response to calls like "stream/items/ contents" as well?
Forgot that you needed this for the stream/items/contents endpoint. We can add it there too (triggered by an output=atom-hifi param). Do you need it anywhere else?
Mihai
On Fri, Feb 19, 2010 at 7:56 PM, Nick Bradbury <nick.bradb...@gmail.com>wrote:
> Sorry for not seeing this until now - been sidetracked with NG > enterprise work this week. Are the missing elements only included > when specifically requesting the "hi-fi" version of the feed, or are > they also included in the response to calls like "stream/items/ > contents" as well?
> I'm away from my main development machine this week, but I'm pretty > sure that stream/items/contents is the only place I'd need to have > "HiFi" support.
