-
Notifications
You must be signed in to change notification settings - Fork 338
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
Private instances #523
Private instances #523
Conversation
2cfa18a
to
74a54a5
Compare
You should use another icon for registration applications, at the moment its the same one as editing a post/comment, which is confusing. And it would be nicer if the "deny reason" input field was only shown after clicking the "deny" button. Also it shouldnt be possible to change the deny reason later. It would also be nice if we could add some extra description for the different site configuration options. |
There aren't too many icons to choose from, but I'll see if I can find something else.
This one I think it should, because applications can be approved, then denied, and back and forth by different admins. So a discussion could develop that ends up with a different deny reason than initially.
I'll try to refactor this so it looks prettier.
The descriptions we can add later once ppl have some more clarifying questions about what they do... they all seem self-expalanatory to me at the moment. |
Still not great. Maybe it would be better to have a single link for "administration", which has tabs or something similar for reports, registration applications, instance config etc. I dont think its necessary to access this stuff from every page.
Its a really bad format for discussion, because people can change or delete comments from others (by accident or on purpose). Better not to get into that, and encourage them to use external tools instead.
Now it seems you have to press deny, then enter the deny reason, and press deny again, not intuitive. Also the approve/deny buttons should probably be hidden at least on accepted applications. |
One issue here is that applications are only for admins to see, while reports are for both admins and mods. So I'd rather have them be at different routes. If we have more "only admin" notifs, or "both admin/mod" notifs, then we can think of better ways to combine them later.
I agree, that isn't the place to do discussion. However after discussion is done, it should be possible to reverse the decision on applications. There's no reason to take away the ability to deny, then approve an application. We wouldn't help anyone by making application decisions irreversible.
I liked it the first way initially, but you asked me to change it to this. I can either always show the deny_reason textarea, or have you reveal that text box with another button. I can't do both.
I already did this for the deny button, but can probably do this for the approve button as well, for ones that are already approved. |
True, but its not necessary to change the deny reason in that case (or in any other case that i can think of).
It should be a separate button for the second action. Possibly show the text input + button in a popup window. |
I changed it so you can't deny twice.
I can't do a popup modal, because that'd be the first we'd have. This is actually the first case of hiding a box, all the others show the |
How about the same kind of input thats used to give a ban reason? |
I mean it has one button which opens the text input + ban button. In comparison, your first version iirc you had to press reject which opened the text input, and then had to press the same reject button again. So its a matter of having different buttons for different actions. |
We can always tweak this later. It is working as is. |
No description provided.