visibility checks around reported content #8
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently, admins and moderators might not be able to see reported content properly because the visibility checks are not adjusted to this. For example:
User 1 creates a followers only note. User 2 reports that note. User 3 (a moderator) sees the report but can not see the content of the note because the visibility checks forbey them from doing so.
A solution would be to embed the note in the reports UI and only there enact different visibility checks which allows admins & moderators to see the note.
In many cases it should be possible to determine moderator action based on the note alone. However, in some cases it might be necessary to get more context from notes that have been replied to. Therefore, admins (and only admins, not moderators) should also be able to go to a page of a note and view the content, even if as a normal user they would not be able to see the content. This should be done after informing them about the fact that they are now using administrator privileges to view the content. Such notes should also not normally be shown on timelines, user profiles, in replies to another note etc.; only if the adminstrator explicitly visits a page about the note.
Since this might potentially be revealing DMs, it seems a good idea to only allow administrators to have this privilege, and not moderators.
I think this can be two sub-tasks.
First, embedding the note in the report (the 80+% solution for 20% of the effort).
Then, afterwards, bypassing everything (e.g via button in the report panel that can also be reused?) for admins.