next »

[anna]

Speaking of a "who's who" and since access control has been mentioned (i.e. some groups don't want too many other users overwhelming their servers), I wonder if it's possible to administer some sort of roster.

When I go into the jabber web interface, the list of users look like this example:

1c598e1edb3e75b5ebfcf042f104f2f3a5be5b0a@servername

That's a UUID of an XO, right?  It might be possible, though I haven't tried, to register an XO through the admin interface and only allow preregistered XOs to connect.

So, a user wanting to connect to an access controlled jabber server would first contact the server admin with his/her UUID and request access.  A human readable "who's who" could be part of that process.

It would add another burden to the server admin, but where access control is desired, it might solve that concern.  Though keep in mind a new UUID is generated when the XO is reflashed, so that would be an issue.

Thoughts?

[Dinky]

Noticed a new jabber on the http://wiki.laptop.org/go/Community_Jabber_Servers :     jabber.buddycloud.com   .

Anyone using it yet ?

Looks like buddycloud has been trying to access existing jabbers.