You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you know, presence updates have a major impact on the overall server performance... but just turning it off is not a real solution in most use-cases. Therefore, I'm suggesting a new option in the presence configuration called limit_to_direct_rooms (or something like that).
The idea is, that when collecting the list of interested parties for presence updates, only room ids with a m.direct membership should be used. As a result, users would retrieve presence updates for their "contacts", but not for everyone who's sharing a group chat room. This could help decreasing the server load and increase privacy at the same time.
What do you think? Could this be a reasonable solution?
The text was updated successfully, but these errors were encountered:
This issue has been migrated from #11977.
As you know, presence updates have a major impact on the overall server performance... but just turning it off is not a real solution in most use-cases. Therefore, I'm suggesting a new option in the presence configuration called
limit_to_direct_rooms
(or something like that).The idea is, that when collecting the list of interested parties for presence updates, only room ids with a
m.direct
membership should be used. As a result, users would retrieve presence updates for their "contacts", but not for everyone who's sharing a group chat room. This could help decreasing the server load and increase privacy at the same time.What do you think? Could this be a reasonable solution?
The text was updated successfully, but these errors were encountered: