User status is broken

[Kot-o-pes]

Community workspaces have a cap of 200 concurrent connections, although you can have more connections active, once you hit that limit you won't be able to see users' status. This doesn't affect their ability to send & receive messages.

this is serious degradation of a service if its not working at least let us disable it completely

[superset1]

++

[ktkd]

+

[Siaber]

++

[wieldes]

... what's next? 😬

[MrShadow74]

+++

[Bralva]

+

[McGregor700]

+

[alexkadyrov]

+

[korokunt]

+

[sasha-sup]

+

[lairil]

++

[robinreinhardt]

++

[FR-Solution]

+

[isurganov]

++

[latitov]

Maybe it's time to take the project away from original authors, if they're about to go rogue and choose to be bad for people..

[kbsx32]

I suppose lots of instances have been upgraded without knowing that in version 6 there is a limit for seeing user status and understood it just when 200 connections limit reached (it took some time for me for example to understand that there is a limit exists).

So, lots of people can't roll back to version 5 of Rocket.Chat without loosing data and now they stuck with such behaviour. Maybe Rocket.Chat developers can help with that?

[kertiskz]

the service is gradually starting to limit simple functions in order to sell users a subscription.

[dmitry-krishtal]

+

[geidsonc]

I'm also in the same situation. I was forced to update to version 6, and now I have this problem.

My suggestion is to allow the definition of a limit on simultaneous connections through an environment variable or configuration in the database via the system.

As it stands, they are imposing limits to force Enterprise subscription.

[buliverd53]

Same here... This a basic feature to be a freemium feature :-(