v5.1.0-RC1: new parameter requires_approval default value #4875

New issue

Open

opened 2026-02-22 10:44:09 -05:00 by deekerman · 0 comments

deekerman commented

2026-02-22 10:44:09 -05:00

Owner

Originally created by @JohnXLivingston on GitHub (Mar 1, 2023).

Describe the problem

In the newly published v5.1.0-RC1 version, the new parameter requires_approval is set to true by default (in the default.yml file).

This means that admins who update without checking new parameters will change their instance behaviour without knowing.

We know that for some instances, admins don't respond to notifications. So, it could be possible that new users got stuck forever with such a feature.

I have mixed feelings about it. I don't know if this is a good or bad thing. (if it could prevent spam account creation on instances that are well-know for not moderating comments, why not 😉 )

Have you thought about it? Have you listed pros and cons?

Additional information

No response

Originally created by @JohnXLivingston on GitHub (Mar 1, 2023). ### Describe the problem In the newly published v5.1.0-RC1 version, the new parameter requires_approval is set to true by default (in the default.yml file). This means that admins who update without checking new parameters will change their instance behaviour without knowing. We know that for some instances, admins don't respond to notifications. So, it could be possible that new users got stuck forever with such a feature. I have mixed feelings about it. I don't know if this is a good or bad thing. (if it could prevent spam account creation on instances that are well-know for not moderating comments, why not :wink: ) Have you thought about it? Have you listed pros and cons? ### Additional information _No response_