On Wed, Jul 30, 2008 at 3:57 PM, Henry H <[EMAIL PROTECTED]> wrote: > (e.g. let users assign nicknames to people > they follow up to a certain # of characters > - say 5, and limit messages to 135 characters)
But, what would you do if you're using a "tracking" service that does real-time prospective search within the stream of all public messages published in a federated network. With such a service, you can't know in advance which user ids you will see. Thus, you can't rely on learning that the prefix "Alex" is different from "Alexa." On Wed, Jul 30, 2008 at 3:56 PM, anders conbere <[EMAIL PROTECTED]> wrote: > On the rest of the web this kind of aliasing isn't > a problem because we can markup that text with > extra data <a href="http://twitter.com/aconbere"; rel="me, > that-xmpp-spec">@anders</a>, the problem you're bring up is > that we don't have a good way besides raw uri's to > describe resources (in this case people) in plain text. Being able to hide data behind the interface in hyperlinks may solve the machine's problem, but it doesn't solve the human interface problem. Imagine that there are two Susan's who might send you Tweets/Dents or whatever. They are: [EMAIL PROTECTED] and [EMAIL PROTECTED] Now, you get a message that looks like this in your IM client: Susan <http://bad.com/susan>: Shall we have dinner tonight? How do you know what answer to give or to whom your answer will be sent? Will you *always* remember to check? How would a non-technical person solve this problem? bob wyman
