I agree, message delivery and ambiguity in the same sentence make me nervous. User tolerance for messages gone astray will be very low. What happens when the wrong John gets the direct message that the other John is a jerk?
I understand the motivation for a smart aliasing system. Fully qualified addresses are not human friendly but unless it can guess right 100% of the time the convenience is not worth it. This is why email clients have address books. The proposed solution assumes that subscription relationships and cohabitation on the same server are a form of an address book, which they are. So why not handle the ambiguity like a regular address book? Ask the user. Reply back with a few choices and ask the user to pick one. Ahoy, Jason ----- "bear" <[email protected]> wrote: | The reason I don't like this and say it cannot guess is the answer | you | gave to PI.ly just now: | | >There's actually an ambiguity here -- if you're subscribed to john on | army.twit.tv | > and john on bleeper.de, it's not specified which john is picked for | your @john | > message. Right now it's up to MySQL to decide, and I bet it picks | the first | > one you subbed to, but I'm not sure. I think it should pick the one | who | > posted most recently. | | without a clear algorithm that everyone agrees on it shouldn't guess | at all | | I guess the problem does boil down to having each processor of a | message having the information needed on the sender and the | destination so proper routing can be done. | | On Sat, Jan 10, 2009 at 3:39 PM, Evan Prodromou | <[email protected]> wrote: | > bear wrote: | > | > For this to be federated it has to *not* guess at the short form, | > | > I don't agree. If I'm on identi.ca and I subscribe to someone | nicknamed | > "john", then if I send a message to "@john", it's 99% percent | certain which | > john I'm talking to. Forcing users to enter the full address for | their | > friends and colleagues, or people on their own servers, is wasteful | of their | > time and effort. | > | > The problem with guessing comes when the message travels to another | server, | > and that server tries to guess who the message is addressed to. Say, | if mary | > on bleeper.de is subscribed to my messages, bleeper.de doesn't have | adequate | > information to determine who I mean by "john". | > | > That's why OMB 0.2 is going to include a) rendered HTML of messages | (so | > remote servers don't have to make links to addressees themselves) | and b) a | > list of addressees. It will make these conversations work a little | better. | > | > -Evan | > | > | | | | -- | --- | 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 | _______________________________________________ | Laconica-dev mailing list | [email protected] | http://mail.laconi.ca/mailman/listinfo/laconica-dev _______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev
