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
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Feature
Current application services allows you to limit the events received by using regular expressions on user_ids, room_ids or room alias. If would also be very useful to also allow events to by filtered on the "type" type field.
Use case
We have several application services that uses user presence to determine the bot message/behavior (eg OfflineAgentBot). In our system this presence information is based on a group. These groups can range from 1 user to 500 users, which makes it impossible to efficiently query this information from the homeserver. Currently we're using MSC2409 feature to have presence events pushed via application service to an endpoint which then aggregates and caches group presence in redis. The problem currently is that there is a very large number of ignored events because we cannot filter on the type of event.
The text was updated successfully, but these errors were encountered:
Feature
Current application services allows you to limit the events received by using regular expressions on user_ids, room_ids or room alias. If would also be very useful to also allow events to by filtered on the "type" type field.
Use case
We have several application services that uses user presence to determine the bot message/behavior (eg OfflineAgentBot). In our system this presence information is based on a group. These groups can range from 1 user to 500 users, which makes it impossible to efficiently query this information from the homeserver. Currently we're using MSC2409 feature to have presence events pushed via application service to an endpoint which then aggregates and caches group presence in redis. The problem currently is that there is a very large number of ignored events because we cannot filter on the type of event.
The text was updated successfully, but these errors were encountered: