My thought on the other information that could be published is that we may need to create a user profile feed that generates a new event when something in the user's public profile is updated. This would be where the out-of-band information about a user would be found.
The in-band information of their Activity would be their primary stream, hmm, unless profile updates become a Activity Stream type guess I should go do some research ;) On Fri, Mar 20, 2009 at 2:33 PM, Bob Wyman <[email protected]> wrote: > On Fri, Mar 20, 2009 at 2:17 PM, bear <[email protected]> wrote: >> Now to put some friendly pressure on the Laconica >> devs to add a source of Atom over XMPP for their >> streams instead of the Atom over Chat they >> are using now :) > Yeah... Grumble... As I understand it, Laconica is trying to maintain > compatiblity with the now defunct "Atom over Chat" that Twitter *used* to > publish. The reason is that some clients were built to support the Twitter > feed back when it was still being published and those client authors didn't > want to change what they are were doing for a "small" publisher like > Laconica... As Laconica instances proliferate, hopefully, that attitude will > change -- especially since Twitter seems to have left the world of XMPP at > this point. > > In any case, whether or not we've got some legacy cruft in the wild, folk > should understand that the "correct" way to publish microblog entries over > XMPP (especially for "firehose" feeds) is by using the "Atom over XMPP" > specification. See: > http://xmpp.org/internet-drafts/draft-saintandre-atompub-notify-07.html > > At some point, we should try to get agreement on the extra-metadata that > people publish in microblog entries. For instance: Number of followers, > Number followed, location, profile links, etc. > > bob wyman > > On Fri, Mar 20, 2009 at 2:17 PM, bear <[email protected]> wrote: >> >> When I did the streams for Seesmic I took a look at the current Best >> Practice and had picked Atom for the same reasons you list. Glad I >> was ahead of the curve this time :) >> >> I'll be double checking that the media enclosure formats we are using >> are compatible with what Activity Streams is suggesting and tweak as >> needed. >> >> Now to put some friendly pressure on the Laconica devs to add a source >> of Atom over XMPP for their streams instead of the Atom over Chat they >> are using now :) >> >> >> >> On Fri, Mar 20, 2009 at 3:04 AM, Chris Messina <[email protected]> >> wrote: >> > Thanks for sharing this here Bob. I agree that I'd love to see >> > ActivityStreams pushed over XMPP. We're starting with ATOM for that >> > reason — >> > and would be excited to see what kinds of ideas might emerge from >> > hooking up >> > PubSub for Activities! >> > Chris >> > >> > On Thu, Mar 19, 2009 at 1:12 PM, Bob Wyman <[email protected]> wrote: >> >> >> >> Over on the Activity Streams list Martin Atkins has been developing >> >> specs >> >> for representing activity stream data as Atom entries. It makes a great >> >> deal >> >> of sense to me that we should see this data not only provided via >> >> traditional files, but also using Atom Over XMPP so that real-time >> >> clients >> >> can be built. MySpace (represented by Monica Keller) has been >> >> particularly >> >> active in helping to refine these extensions to the Atom entry format >> >> and >> >> recently announced that MySpace and Yahoo are already sharing Atom >> >> Activity >> >> data. >> >> >> >> My hope is that "microblogging" services, that have been the focus of >> >> much >> >> of the discussion here, will also grow to handle the more general set >> >> of >> >> events that ActivityStreams encompasses. It's great that I can generate >> >> short-messages on something like Identi.ca today and access them over >> >> XMPP, >> >> but it would be even better if I could have all my "activity stream" >> >> data >> >> and events handled in the same way. If we can get all the data >> >> published >> >> over XMPP in a consistent format: "Atom entries with extensions" then >> >> it >> >> will be really easy to build some really exciting and innovative >> >> clients, >> >> cross-platform services, etc. >> >> >> >> For info on Atom Activity Streams, see: http://activitystrea.ms/ (links >> >> to >> >> draft specs are provided) >> >> Discussion is on this list: >> >> http://groups.google.com/group/activity-streams?hl=en >> >> Documentation of data published by MySpace is at: >> >> >> >> http://developerwiki.myspace.com/index.php?title=Standards_for_Activity_Streams >> >> >> >> To give you a quick overview of the kinds of "Activities" or events >> >> that >> >> MySpace is supporting, I've included the TOC from their spec below: >> >> >> >> 1 Activities Stream Spec Compliant Activities >> >> >> >> 1.1 Single User's Activities >> >> 1.2 Friend Activities >> >> 1.3 Atom Entry Format for Activities >> >> 1.4 Photos >> >> >> >> 1.4.1 Tagged in Photo >> >> 1.4.2 Posting a Photo >> >> >> >> 1.5 Music >> >> >> >> 1.5.1 Posting a Song >> >> 1.5.2 Sharing a Song >> >> >> >> 1.6 Notes >> >> >> >> 1.6.1 Posting a Blog >> >> 1.6.2 Posting a Forum Topic >> >> >> >> 1.7 Videos >> >> >> >> 1.7.1 Sharing a Video >> >> 1.7.2 Marking a Video as a Favorite >> >> 1.7.3 Posting a Video >> >> >> >> 1.8 People >> >> >> >> 1.8.1 Adding Friends >> >> 1.8.2 Joining a Group >> >> 1.8.3 Creating a Friend Category >> >> >> >> 1.9 Events >> >> >> >> 1.9.1 Band Shows >> >> 1.9.2 Hosting an event >> >> 1.9.3 Attending an event >> >> >> >> bob wyman >> >> >> > >> > >> > >> > -- >> > Chris Messina >> > Citizen-Participant & >> > Open Web Advocate >> > >> > factoryjoe.com // diso-project.org // vidoop.com >> > This email is: [ ] bloggable [X] ask first [ ] private >> > >> >> >> >> -- >> --- >> Bear >> >> [email protected] (work) >> [email protected] (jabber & email) >> http://code-bear.com/bearlog (weblog) >> >> PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29 > > -- --- Bear [email protected] (work) [email protected] (jabber & email) http://code-bear.com/bearlog (weblog) PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29
