Gummikavalier
Gummikavalier
Sorry! I'm not an actual dev or RC project maintainer. Just reporting. :)
And even when the workaround works, as the regular owner role is builtin and special compared to hand made ones, it means allowing the invite permission to any member of...
I also confirm that this is still an issue on RC 6.0.0 release candidate 0. :(
Confirmed fixed in RC 6.1.2. :hearts:
Hi! I checked that global pruning (90 days and once a day schedule) works for the instances we've been running. The issues with pruning I've noticed are with channel specific...
I asked about the status of reaction name fixes in the community meeting few weeks ago. The issue is complex; Showing real names requires more queries to be made and...
@banderosss As a load change issue the name change is not that big question in closed systems I admit. Namely the biggest load issues would probably come from individuals in...
@henit-chobisa Me humbly bows in front of your reasoning! Thanks! :raised_hands: @debdutdeb Raising awareness of the devs. Would this work on the issue?
I cannot replicate this issue in our test environment with RC 5.2.0. I also tried with native oplog on and off. RHEL8 with tar installation, two nodes setup.
Our RC 5.3.3 seems to limit the max shown amount of members to somewhere between 40 - 80 for regular users and for admins ~300. Disabling rate limiters did not...