posting this on behalf of Beehaw, as we’ve started doing denials in meaningful amounts.
we have a little rejection letter telling people to reapply if they are rejected, but we just experimented and it seem users do not receive the rejection reason in any way. if the rejection field is intended exclusively as a moderator backend thing, it’s very ambiguously indicated.
if it isn’t, and users do receive some sort of information on rejection, we are also unclear on what that information is or by what mechanism people receive it. we made a test account to see how our users would receive what we assumed they’d be getting, and so far any rejection is:
- not indicated on the account;
- not indicated through logging in to the account (because you can’t log in, as far as i can tell, if you’ve been rejected);
- and not given to you through email, if you choose to provide one.
clarification would be much appreciated, as the answer to this question would obviously have direct implications on how we move forward with approvals and denials. thanks!
Semi-related: rejections are also displayed as “approved by” in the read applications log.
Looks like if you try to login you get a message telling you the deny reason
Can they then reapply from the same account?
seems to just infinitely load when I tried again
okay this matches our testing
btw, if you accept then deny the account still seems to be accepted
We have also opened a bug report for this issue
You can find it out yourself by registering with a test account.
We did this and this is why we created this post, we did not notice any notification to the test account
to update this, since we’ve had a lot of developments:
- some of this was on our end. approvals were not going through to Gmail users even though Lemmy sends those, and that was an email configuration problem on our part.
- denials are not sent to users by email, which is by design as of now.
- users are supposed to be able to log in and get their denial, but there’s a bug which makes this inconsistent.
we have opened an issue about all of this, which you can find here. hopefully this is helpful to any instance also dealing with one or multiple facets of a problem like this!
