Ticket #5311 (assigned defect)

Opened 7 years ago

Last modified 6 years ago

make shared roster not include everybody

Reported by: daf Owned by: robot101
Priority: normal Milestone: 8.2.0 (was Update.2)
Component: telepathy-other Version:
Keywords: Cc: jg, kimquirk, eben, Collabora
Action Needed: never set Verified: no
Deployments affected: Blocked By:


The XMPP server on jabber.laptop.org is configured so that every user is subscribed to the presence of every other user, using a feature known as "shared roster". This does not scale well to large numbers of users. In the long term, we're planning to move away from using the shared roster entirely (see #5309); in the short term, for Update.1, we need to try and make the shared roster smaller, by restricting it to one or another subset of all the people an the server.

Change History

Changed 7 years ago by robot101

  • cc jg, kimquirk, eben added
  • status changed from new to assigned

My plans for this (in Update.1 timeframe) was to modify the server, as detailed in my e-mail at http://lists.laptop.org/pipermail/devel/2007-November/007926.html, so that the server would provide some groups like "Nearby" for people who were on the same network block (IPv6 /96 or IPv4 /24 for example), and "Random" for a group of N (30, or 50, whatever, tweakable...) instead of the current "Everybody" group. This depends on the fix #4965 being merged, otherwise friends are not guaranteed to be visible.

Note that this is a trade-off of search functionality for scalability. If the laptop is only made aware of Friends + Nearby + Random, the number of buddies and activities that it will be looking through when it does its client side search is somewhat reduced. That said, if the "Nearby" thing works, and gives you the people you would've seen via Salut anyway, then this should only result in an increase in available results compared to XMPP being disabled. It's something we should be aware of when proceeding with this plan however.

The true fix for Update.2+ is a protocol where the searching and selection of relevant activities and buddies can be done on the server, this is tracked by #5309.

Changed 7 years ago by robot101

So in the process of fixing #5313, I'm working on a patch for ejabberd now which gives us an "Online" group. I intend to continue with "Nearby" and "Random" if possible.

We've got a fix for EJAB-71, but EJAB-407 could bite us in the ass.

Changed 7 years ago by gdesmott

  • cc gdesmott added

Changed 6 years ago by gdesmott

  • next_action set to never set

XS's ejabberd now configure @online@ shared roster instead of @all@. Is that enough to close this ticket?

Changed 6 years ago by gdesmott

  • cc Collabora added; gdesmott removed
Note: See TracTickets for help on using tickets.