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

Provision request is unclear to IRC ops without Matrix knowledge #462

Open
Mikaela opened this issue Jun 26, 2017 · 3 comments
Open

Provision request is unclear to IRC ops without Matrix knowledge #462

Mikaela opened this issue Jun 26, 2017 · 3 comments
Assignees
Labels
p1 quick-win T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements.

Comments

@Mikaela
Copy link
Contributor

Mikaela commented Jun 26, 2017

            `${userId} has requested to bridge ${roomDesc} with ${ircChannel} on this IRC ` +
            `network. Respond with 'yes' or 'y' to allow, or simply ignore this message to ` +
            `disallow. You have ${timeoutSeconds} seconds from when this message was sent.`);

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:

            `${userId} has attempted to claim ownership of ${roomDesc} and ${ircChannel} on this IRC ` +
            `network to bridge them together. Respond with 'yes' or 'y' to confirm, or simply ignore this message to ` +
            `deny. You have ${timeoutSeconds} seconds from when this message was sent.`);

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.

@kegsay
Copy link
Member

kegsay commented Jun 26, 2017

Agreed. We need to be more scary on the wording here.

@Spydar007
Copy link

I think a better message would be to let them know what matrix is and where they can get more info.

            `${userId} has attempted to claim ownership of ${roomDesc} on the matrix.org network` +
            `and ${ircChannel} on this IRC network to bridge them together. Please make sure you are` +
            `aware of the consequences of this. Please visit #matrix-irc on freenode for more information.` +
            `Respond with 'yes' or 'y' to confirm, or simply ignore this message to deny.` +
            `You have ${timeoutSeconds} seconds from when this message was sent.`);

@Spydar007
Copy link

I would also link this wiki page somewhere too

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.
Projects
None yet
Development

No branches or pull requests

5 participants