On Wed, Jul 30, 2008 at 05:46:02PM -0500, Henry H wrote:
> At this point, I'm not sure what problem you're trying to address. Too many
> tangential discussions and not enough definition of key assumptions.
>
> Are you trying to come up with a universal, user-friendly way to provided
> unique identification for micro-blogging platforms that works across a
> federated environment? What protocol? SMS? XMPP? HTML/HTTP? SMTP? All of
> them?
>
> If it's XMPP, it already exists and it works. And it works for SMS if you
> don't care about how long it is. It also works for HTML/HTTP. And it also
> works for SMTP. It's [EMAIL PROTECTED] and the key assumption is name is
> unique within a domain.
There are actually two problems here:
1) How to indicate that an otherwise unformatted message is a "reply"
instead of a standalone pronouncement.
2) How to address that reply.
I think the twitter solution of @replies isn't bad for #1. For #2, it
clearly suffers from the domain problems we've discussed, but also
suffers internally to twitter in that you can't address a reply to a
specific message but only to a specific person. As an outsider to the
conversation, I'm often left wondering what any given reply is in
reference to, and also often finding that I don't care enough to dig
through the entire stream to find out.
--
- Adam
** Expert Technical Project and Business Management
**** System Performance Analysis and Architecture
****** [ http://www.adamfields.com ]
[ http://www.morningside-analytics.com ] .. Latest Venture
[ http://www.confabb.com ] ................ Founder
[ http://www.aquick.org/blog ] ............ Blog
[ http://www.adamfields.com/resume.html ].. Experience
[ http://www.flickr.com/photos/fields ] ... Photos
[ http://www.aquicki.com/wiki ].............Wiki
