-
Notifications
You must be signed in to change notification settings - Fork 53
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
Revise roles page #271
Revise roles page #271
Conversation
PR Summary
|
✅ Deploy Preview for reactiflux ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copy is good, but I think we should keep the links so non-members can contact us (for example if there's a question about promotion policies or an unban request from a friend of a banned member) and so members can reuse sessions and settings (including accessibility settings that the user may rely on) from the native client.
Fair, but I'm still concerned about the latter issue:
In my experience most users are primarily using the native Discord client, and therefore direct links are more difficult to open for users that aren't logged in or don't have their preferred settings on web. This likely affects most users to an extent, as Discord doesn't attempt to sync these with the native client. Alternatively we could also solve these issues using the |
Oh word, it's just a direct swap like |
No description provided.