On Mon, Sep 7, 2009 at 12:18 PM, Toby Inkster <[email protected]>wrote:
> > Lastly, I think it would be nice for this to be possible just for > architectural reasons: StatusNet is supposed to be about decentralising > microblogging; accounts shouldn't be tied to a single server. Yeah, I agree. It seems to me that using the PubSubHubBub (PuSH) approach would work — and would follow what's emerging in the industry as a reasonable mechanism to achieve this cross-posting situation that you're describing. Metaphorically, we'd end up with something more like this: ln -s [email protected] [email protected] In other words, creating equivalency between two nodes/users in two separate services. I think it's important and useful to use the email-style identifier format in this situation, even though both could be expanded to their URL equivalents (http://status.net/chris and http://twitter.com/chris). I would worry about creating confusion, however — if people discovered one or the other accounts and began replying to either one. Would their comments/replies need to be synced across contexts as well? Chris -- Chris Messina Open Web Advocate Personal: http://factoryjoe.com Follow me on Twitter: http://twitter.com/chrismessina Citizen Agency: http://citizenagency.com Diso Project: http://diso-project.org OpenID Foundation: http://openid.net This email is: [ ] bloggable [X] ask first [ ] private
_______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev
