For this to be federated it has to *not* guess at the short form, IMO even to assume twitter, because once you have more than one server talking to yours you cannot assume @bear is from system1 or system2 that your server has communicated with.
The only way I can see this working is if each server that talks to yours offers an API endpoint to do roster queries so you can find out what names resolve - but that would mean each @foo entry would require a name lookup to each federated server that you have access to. Not a scalable solution IMO. One way would be to limit the scope of any guessing to the roster of followers each user has but that would require realtime roster updates that are pushed to each server the user has access to. On Fri, Jan 9, 2009 at 4:31 PM, PI. ly <[email protected]> wrote: > The question is whether it will still guess at remote users based on > subscriptions if a short form is used. For instance, if I put in > @evan, will it see that there's no evan on hap.pi.ly and see that I'm > subscribed to identi.ca/evan and go to you? Or do I need to specify > @identi.ca/evan or it won't get to you? > > Btw, I'm in favor of the second solution. > @hap.pi.ly/happily > _______________________________________________ > Laconica-dev mailing list > [email protected] > http://mail.laconi.ca/mailman/listinfo/laconica-dev > -- --- 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
