Open jaller94 opened 2 years ago
Setting the power level to 51 can be better so it doesn't stop the bot from kicking moderators that are idle (and thus activating the privacy filter)
Also note that if people can, they will probably often demote the appservice to 0 as soon as it kicks someone for idling, resulting in the privacy filter activating, and the users the bridge was supposed to kick join flooding the IRC channel.
I think the theory was here that you would use bot commands / integration managers to remove the bot in case you want to be rid of it. People kicking/banning bots is more of an accidental feature that is fraught with problems.
I suspect if we want to support this type of thing, we should actually codify what a kick does to the bridge (remove room mappings, remove ghost users, drop PLs etc).
I think the theory was here that you would use bot commands / integration managers to remove the bot in case you want to be rid of it. People kicking/banning bots is more of an accidental feature that is fraught with problems.
One definite reason for doing this is if the bot is compromised.
Also note that if people can, they will probably often demote the appservice to 0 as soon as it kicks someone for idling, resulting in the privacy filter activating, and the users the bridge was supposed to kick join flooding the IRC channel.
What do you mean by this?
Because libera only gives the bridge so many connections, there are scripts for kicking idle users. Some prefer not kicking idle users, so they will do what they can to prevent the bot from kicking idle people, which the bridge doesn’t really handle that well right now.
Does the IRCd handle large number of connections poorly?
It's not about performance but to keep user lists and chat logs "clean".
As a community manager I want to choose the power level of the IRC bridge. With the default of PL 100 I'm not able to depromote or kick the bridge in case it malfunctions or stops working.
Examples
1578