-
Notifications
You must be signed in to change notification settings - Fork 152
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
Provision request is unclear to IRC ops without Matrix knowledge #462
Labels
p1
quick-win
T-Enhancement
New features, changes in functionality, performance boosts, user-facing improvements.
Comments
Agreed. We need to be more scary on the wording here. |
I think a better message would be to let them know what matrix is and where they can get more info.
|
I would also link this wiki page somewhere too |
justinbot
added
T-Enhancement
New features, changes in functionality, performance boosts, user-facing improvements.
and removed
improvement
labels
May 13, 2022
Mikaela
added a commit
to Mikaela/mikaela.github.io
that referenced
this issue
Oct 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
p1
quick-win
T-Enhancement
New features, changes in functionality, performance boosts, user-facing improvements.
is the current message in Provisioner.js of version 0.7.2.
I think this is ambiguous and sounds more innocent than it actually is for people who don't know what Matrix is and I would instead suggest provoking the IRC op:
I am aware that it's not strictly true, but I think it's better than later having IRC ops wondering when did they grand Matrix side power entirely to random Matrix user who now has power to make all logs on the channel public without them knowing and thus breaking common courtesy of letting IRC users know that they are talking in publicly logged room. I think the Matrix user would also be able to confuse Matrix users by banning IRC users and thus possibly resulting a situation where Matrix users don't see some messages from banned virtual user.
The text was updated successfully, but these errors were encountered: