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
Add notifications of severed relationships #27511
Conversation
0d5c6c1
to
8622abe
Compare
8241ca5
to
0453fd5
Compare
8245688
to
c37fdf2
Compare
This pull request has merge conflicts that must be resolved before it can be merged. |
This pull request has resolved merge conflicts and is ready for review. |
c5fe57a
to
f3ed005
Compare
This pull request has merge conflicts that must be resolved before it can be merged. |
…rmation for affected local accounts
f3ed005
to
89d3c22
Compare
Great to see this get merged! |
this is incredible! great job everyone |
@ClearlyClaire There are 2 similar keys in Crowdin now with the same text, is the second one a typo? Lines 41 and 378 in 44bf7b8 |
Oops. Thanks for pointing this out, #29689 should address it |
Reference: mastodon/mastodon#27511 This is done purely based on the above codebase without real testing.
When a moderation action severs relationship, record those relationships so they can be examined by the affected local users, offering them to export the lost follows, as well as re-issue them if the domain block gets reverted.
Lost followers cannot be recovered this way, but the information should be made available nonetheless.
TODO:
Documentation PR: mastodon/documentation#1385