-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
feat: ユーザー登録を承認制にできるように #12852
base: develop
Are you sure you want to change the base?
feat: ユーザー登録を承認制にできるように #12852
Conversation
Fixes an issue where if approval and invite were enabled the code would stay as unused
Removes approvals tab in favor of the new approvals page
これ既存ユーザーはどうなるんだろう |
misskey/packages/backend/test/e2e/users.ts Line 181 in 7948018
signupReason: user.signupReason, 追加すれば良さそう
|
テ ス ト 通 過 |
This comment was marked as resolved.
This comment was marked as resolved.
この変更が適用されてないプレーンなMisskeyでの動作確認が必要 |
これログイン処理では承認済みかどうかのチェック入ってるけどその他の認証処理には入ってないので、何らかの方法でAPIトークンを取得できれば承認をバイパスできるな |
通常のAPI呼び出し時にも承認状態を確認するようにした |
テストあると有難いわね |
@Mar0xy Have you coded (or do you plan to write) a test for this? |
We don't have a test for it nor is one being written/planned currently. |
あんまり意味ないとは思うけど、同一IPからの複数申請は弾く(一つ承認されないと申請できない)ようにしても良いかも |
承認制と招待コード両方が有効になってるときの処理が入ってなかった |
基本的に招待コード持ってたら審査バイパスでいいと思っている |
Thank you for sending us a great Pull Request! 👍 example: pnpm run build-misskey-js-with-types |
Is the development of this feature stalled? I believe it would be more practical to implement a registration reason feature rather than switching to an invite-only system after a period of administrator inactivity. |
|
What
Cherry-picked from https://activitypub.software/TransFem-org/Sharkey
Why
モデレーション強化
Fix #5957 / Fix #10334
Additional info (optional)
Sharkeyからの改良点
Checklist