While not an actual solution, the work-around for this I use is to set my server up to use a local JUD and also to point at users.jabber.org. I encourage users who wish to have their details made public to register with users.jabber.org. It would, perhaps, be nice if an entry in the JUD could be marked as public and then distributed to any other Jabber server with which the server on which it is registered came into contact. Some kind of TTL would probably be required to prevent a server being flooded with second- or third-hand JUD info, however and it would have to be heavily karma-limited.

Dougal Campbell wrote:

On Tue, 17 Jun 2003, Bart van Bragt wrote:



[....]

There are already some online indicators available. The problem with
these indicators is that most of them work on a site basis. So you need
one bot/agent in your roster for every site where you want to display
your presence.



This reminds me of a discussion I had recently about Jabber. One of the things that came up was that a "weakness" of the decentralized nature of Jabber is that there is no central method for locating other Jabber users.

Let's say that you convince somebody to switch from some other messenger
to Jabber. She sets up a jid "[EMAIL PROTECTED]". Then she says "I wonder if
my old friend Bob is on Jabber?" She does a JUD search, but doesn't find
Bob. Unbeknownst to Alice, Bob *does* have a Jabber account
("[EMAIL PROTECTED]"). But since the JUDs don't talk to each other, she has
no easy way to find it, unless she contacts him by other means and asks
him.

Has anyone thought about creating a centralized user directory? There
could be an optional s2s component for the server implementations, and
perhaps a direct c2s protocol that clients could implement, as well.

If such a project were started, it would be a good idea to fold presence
into it as well.





_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev

Reply via email to