discourse/plugins/discourse-presence/config/settings.yml

plugins:
  presence_enabled:
    default: true
    client: true
  presence_max_users_shown:
    default: 5
    client: true
    min: 1
    max: 50
Add discourse-presence as a core plugin (#5137) * Add discourse-presence as a core plugin * Default enabled 2017-09-07 08:40:18 +01:00			`plugins:`
			`presence_enabled:`
Discourse-presence improvements - Added guardian checks to endpoint - Added security to messagebus publishing - Added specs for security measures - Moved all logic into component - Stop sending ‘keepAlive’ messages if the user stops editing for more then 2 minutes - Enable plugin by default 2017-09-08 21:06:27 +01:00			`default: true`
Disable presence for now 2017-09-08 10:36:10 -04:00			`client: true`
fix site setting name 2018-01-29 11:04:56 +01:00			`presence_max_users_shown:`
New 'presence_max_users_shown' site setting (defaults to 5) 2018-01-29 10:48:42 +01:00			`default: 5`
FEATURE: Redesign discourse-presence to track state on the client side. (#9487) Before this commit, the presence state of users were stored on the server side and any updates to the state meant we had to publish the entire state to the clients. Also, the way the state of users were stored on the server side meant we didn't have a way to differentiate between replying users and whispering users. In this redesign, we decided to move the tracking of users state to the client side and have the server publish client events instead. As a result of this change, we're able to remove the number of opened connections needed to track presence and also reduce the payload that is sent for each event. At the same time, we've also improved on the restrictions when publishing message_bus messages. Users that do not have permission to see certain events will not receive messages for those events. 2020-04-29 12:48:55 +08:00			`client: true`
New 'presence_max_users_shown' site setting (defaults to 5) 2018-01-29 10:48:42 +01:00			`min: 1`
			`max: 50`