Hello,
I'm not sure I am totally clear on what exactly your asking. (Sorry)
When I first made this module at the time there was no JSON or JSONP
alternative for Buzz so what I had to do was load the feed via the
Google Feed API which their JSON format does not include much of the
ideal content I would have liked to see.
But since then the Buzz API has now included JSON/JSONP so I have been
planning on making a new module for Buzz using that API instead now
since their JSON structure does include much more content.
You can see more on this here...
http://code.google.com/apis/buzz/v1/getting_started.html#JSONP
And their current JSON format can be seen as follows...
http://www.googleapis.com/buzz/v1/activities/googlebuzz/@public?alt=json&callback=foo&prettyprint=true
(I added &prettyprint=true so you can see the JSON structure better
which this was not available before either and I had to manually
dissect the JSON structure.)
In the JSON data you will now see the "actor":{} object which contains
the thumbnail URL to the profile pic. I am not sure if this is what
your looking for or what, but as you can probably also see in the JSON
data they have actually included a bunch of stuff to almost the point
of being overly bloated.
(There is also "attachments": [] and "enclosure": [] for media
content.)
Unfortunately, some of this makes writing a custom JSON parser for it
a bit more complex and bloated then I ideally would like (in my first
revisions of it) so I have been deciding on what should all be
included in the module to try to keep it as simple and lightweight as
possible. Of course being an open script, developers could easily add
to the callback handler/parser to include extra parsing of data they
need as well. :)
Does this help?
Cheers!
Vision Jinx