Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Update admin/domain_blocks to include conflict response #1417
Update admin/domain_blocks to include conflict response #1417
Changes from all commits
c2153cd
9694154
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Arguably this shouldn't be a 422 but instead a 409 conflict, I'm not sure how easy that would be to change though, since the 422 is existing behaviour.
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.
This is also misleading kind of: The check is just "do we have a domain block for any of the variants of
example.com
", it doesn't actually check that the block that is found is "stricter" than the requested block to create.i.e., if you have a block for
foo.example.com
where you want to suspend, but you already have a block forexample.com
which is asilence
, then you cannot createfoo.example.com
's block with suspend, because the rule forexample.com
prevents you.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.
That does sound like a bug, we may want to let people block subdomains of domains they have merely limited, and that is something the admin interface allows afaict
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.
Yeah, the logic is definitely different: https://github.com/mastodon/mastodon/blob/main/app/controllers/admin/domain_blocks_controller.rb#L31
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.
In IFTAS FediCheck we basically had to reimplement the domain block redundancy code, and comparing severity.
i've also an issue to add webhooks to federation management (would certainly be also good to know when a new domain is noticed, but this is much harder to implement )