Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can not choose the power level of the bridge bot #1582

Open
jaller94 opened this issue Jul 25, 2022 · 6 comments
Open

Can not choose the power level of the bridge bot #1582

jaller94 opened this issue Jul 25, 2022 · 6 comments
Labels
S-Minor Impairs non-critical functionality or suitable workarounds exist T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements.

Comments

@jaller94
Copy link
Contributor

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

@jaller94 jaller94 added S-Minor Impairs non-critical functionality or suitable workarounds exist T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements. labels Jul 25, 2022
@jaller94 jaller94 changed the title Can not choose the permissions of @appservice:libera.chat Can not choose the power level of the bridge bot Jul 25, 2022
@morguldir
Copy link

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.

@Half-Shot
Copy link
Contributor

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).

@DemiMarie
Copy link

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?

@morguldir
Copy link

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.

@DemiMarie
Copy link

Does the IRCd handle large number of connections poorly?

@progval
Copy link
Contributor

progval commented Aug 24, 2022

It's not about performance but to keep user lists and chat logs "clean".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-Minor Impairs non-critical functionality or suitable workarounds exist T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements.
Projects
None yet
Development

No branches or pull requests

5 participants