TypePad has just shipped PubSubHubbub-enabled activity streams feeds for
all TypePad users, which include activity by those users across all
things TypePad.
Here are some examples:
http://profile.typepad.com/apparentlymart/activity/atom.xml
http://profile.typepad.com/markpasc/activity/atom.xml
http://profile.typepad.com/parishilton/activity/atom.xml
http://profile.typepad.com/zacharyquinto/activity/atom.xml
Fortunate timing allowed me to squeeze in at the last moment some of the
changes we discussed at the last meetup, including:
* We're exclusively using link rel="photo" for userpics. rel="avatar"
is not included, since I figured the few generic consumers we have today
aren't doing much with that information anyway.
* We're using atom:author for the actor, though we're also still
publishing activity:actor for the moment for compatibility.
These feeds are linked from user profile pages as normal,
auto-discoverable Atom feeds, and they're compatible with
non-activity-aware feed readers.
--
You received this message because you are subscribed to the Google Groups "Activity Streams" group.
To post to this group, send email to activity...@googlegroups.com.
To unsubscribe from this group, send email to activity-strea...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/activity-streams?hl=en.
BIG CONGRATULATIONS Martin (and the TypePad team) !!!
Congrats Martin. Great to hear.
On Mar 11, 3:55 pm, Darren Bounds <dar...@cliqset.com> wrote:
> Congrats Martin. Great to hear.
>
> On Mar 11, 2010 3:43 PM, "Martin Atkins" <m...@degeneration.co.uk> wrote:
>
> Hi all,
>
> TypePad has just shipped PubSubHubbub-enabled activity streams feeds for all
> TypePad users, which include activity by those users across all things
> TypePad.
>
> Here are some examples:
> http://profile.typepad.com/apparentlymart/activity/atom.xml
> http://profile.typepad.com/markpasc/activity/atom.xml
> http://profile.typepad.com/parishilton/activity/atom.xml
> http://profile.typepad.com/zacharyquinto/activity/atom.xml
>
> Fortunate timing allowed me to squeeze in at the last moment some of the
> changes we discussed at the last meetup, including:
>
> * We're exclusively using link rel="photo" for userpics. rel="avatar" is
> not included, since I figured the few generic consumers we have today aren't
> doing much with that information anyway.
>
> * We're using atom:author for the actor, though we're also still publishing
> activity:actor for the moment for compatibility.
>
> These feeds are linked from user profile pages as normal, auto-discoverable
> Atom feeds, and they're compatible with non-activity-aware feed readers.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Activity Streams" group.
> To post to this group, send email to activity...@googlegroups.com.
> To unsubscribe from this group, send email to
> activity-strea...@googlegroups.com<activity-streams%2Bunsubscrib e...@googlegroups.com>
Awesome!
--
You received this message because you are subscribed to the Google Groups "Activity Streams" group.
To post to this group, send email to activity...@googlegroups.com.
To unsubscribe from this group, send email to activity-strea...@googlegroups.com.
This isn't really considered to be a developer feature... it's just a
feed, after all. It's discoverable by standard feed autodiscovery, so
you don't need to know anything proprietary except the location of the
user's TypePad profile page in order to play.
I consider these feeds on TypePad to be an example of the progressive
enhancement that our spec affords; we just took a standard feed and
bolted some extra elements onto it. Right now users of these feeds just
see standard feed fare... but as soon as a good activity streams
consumer application comes along it'll magically become a better user
experience for users of that application without the user needing to
understand why it's better and without Six Apart needing to partner with
the company that produces the consumer application.
I hope in the coming months we can persuade more services to add these
extra bits to their feeds so that this spec moves from being a protocol
for integration between specific pairs of partners to the decentralized,
ad-hoc syndication system it was always intended to be.
On Thu, Mar 11, 2010 at 3:42 PM, Martin Atkins <ma...@degeneration.co.uk> wrote:
> * We're exclusively using link rel="photo" for userpics. rel="avatar" is
> not included, since I figured the few generic consumers we have today aren't
> doing much with that information anyway.
Quick question - it looks like your <link rel="photo" /> elements are
using "src" for the actual image... that should be 'href' , no? Per
http://atompub.org/rfc4287.html#element.link - href is a MUST and
there's no mention of 'src'.
We'd love for StatusNet subscribers to see your pretty face ;-)
Thanks!
--
James Walker :: http://walkah.net/
James,
Thanks for pointing that out. This was a stupid error but it makes me
wish we had a good validator or even just a viewer to test these things
with.
I'm hoping to take some time next week to just make a simplistic
activity streams visualizer tool where you can provide a URL for a feed
and it will print out a description of the meaning of the feed as far as
an activity streams parser is concerned.
And also, of course, I'll fix this error in the feeds.
--Steve
On Sat, Mar 13, 2010 at 7:02 PM, Martin Atkins <ma...@degeneration.co.uk> wrote:
> This was a stupid error but it makes me
> wish we had a good validator or even just a viewer to test these things
> with.
--
Steve Ivy
http://monkinetic.com // http://diso-project.org
This email is: [ ] bloggable [x] ask first [ ] private
I think this just needs someone to take the time to work on it. I
suspect initially we'd need to host a fork of it ourselves, but the
FeedValidator folks said previously that they'd be interested in running
it if the AtomActivity specification gains non-trivial adoption.