On Thu, 2008-08-07 at 17:04 +0200, - wrote: > Reading the openmicroblogging spec I was wondering if wouldn't be a > better idea to just extend current opensocial APIs (people, > activities, appdata, messaging) with a new API (blogging).
Do you mean, literally, the OpenSocial API? The one put out by Google? Or are you talking about DiSo, RSS + Clouds, XFN, FOAF, or something else? > In my opinion, a lot of work would be reused (profiles, friends, > authentication and authorization....), and both communities (social > networks and microblogging services) would benefit of a unique spec. The spec is based on OAuth and most of the interaction is OAuth with some extra parameters to get profile information across. I'll be honest -- I'm a little sick of "why don't you just use technology XYZ?" questions. There is no existing federated microblogging standard, so ANY standard is going to require application of an existing technology. XMPP PubSub, OAuth, FOAF, whatever. It may be easy, it may be hard, but it's going to take some specification. -Evan
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev
