Skip to content
This repository has been archived by the owner on Jun 6, 2021. It is now read-only.

Registration: add instructions for finding staff #498

Closed
wants to merge 2 commits into from
Closed

Registration: add instructions for finding staff #498

wants to merge 2 commits into from

Conversation

fndax
Copy link
Contributor

@fndax fndax commented Apr 7, 2021

Normally I'd mention /stats p instead of /join #freenode for obvious reasons, but the channel is actually fairly helpful for registration issues so I made an exception.

Fixes #492

Normally I'd mention `/stats p` instead of `/join #freenode` for obvious reasons, but the channel is actually fairly helpful for registration issues so I made an exception.

Fixes #492
@glguy
Copy link
Contributor

glguy commented Apr 7, 2021

Pointing people to #freenode sounds right to me. I've already heard people ask how they'd find a staff member in the first place. Most registration issues won't need a staff member specifically, so I think that's another win for joining the channel instead of recommending stats p. Of course stats p already confuses new users as it the destination of the output can be a surprise.

An additional comment I'd make is that we might want to tell people how to identify who is staff on #freenode. It might not be obvious to check for @ or a freenode/staff/. Being explicit will help them know who they can trust as authoritative.

@fndax
Copy link
Contributor Author

fndax commented Apr 7, 2021

@glguy Would adding the following sentence to the end address your second paragraph?

If your problem involves sensitive information, be aware that people with ops in #freenode (designated with @ and a freenode/staff/ cloak in /whois) are network staff and can be messaged in private as needed.

(Bit more technical than I was hoping, but I'm having trouble thinking of better wording)

@swantzter
Copy link
Contributor

For a nitpick I'd say "commonly designated by @" because not all clients does that

@freenode freenode deleted a comment from down4some1x Apr 17, 2021
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

registration help doesn't say *how* to contact staff
3 participants