Moderation capabilities based on IPs #23

Open
opened 2022-08-02 09:32:31 +00:00 by hf · 2 comments
Owner

Currently there is no way for an ordinary Moderator to check who placed what pixels where without needing command line access.

Things that would be needed:

  • Show users that placed within a given area within the last x hours/minutes/seconds (sum up amount of pixels per user and show last pixel)
  • Without showing IPs (map IPs to random UUIDs) but with shoing CIDR IP ranges
  • Abiity to ban and unban by this UUID or CIDR range
  • Show pixels an UUID placed within a given area within the last x hours/minutes/seconds
  • Rollback an UUID (maybe, will be very performance intensive)
Currently there is no way for an ordinary Moderator to check who placed what pixels where without needing command line access. Things that would be needed: - Show users that placed within a given area within the last x hours/minutes/seconds (sum up amount of pixels per user and show last pixel) - Without showing IPs (map IPs to random UUIDs) but with shoing CIDR IP ranges - Abiity to ban and unban by this UUID or CIDR range - Show pixels an UUID placed within a given area within the last x hours/minutes/seconds - Rollback an UUID (maybe, will be very performance intensive)
Author
Owner

Rollback an UUID not possible with our current redis lua script, because we don't know the overwritten color now. Also too much possibilities for jannies to abuse, potentially doing actions that can'tbe undone.

Makes CIDR ban only thing that is left.

Rollback an UUID not possible with our current redis lua script, because we don't know the overwritten color now. Also too much possibilities for jannies to abuse, potentially doing actions that can'tbe undone. Makes CIDR ban only thing that is left.
hf self-assigned this 2023-03-14 17:33:18 +00:00
hf added the
enhancement
label 2023-03-14 17:33:24 +00:00
Author
Owner

Only range bans are left and that's more of an SQL issue. The implementation is simple once we got a way of storing it.

Only range bans are left and that's more of an SQL issue. The implementation is simple once we got a way of storing it.
hf added this to the SQLRefactor milestone 2023-03-17 03:26:03 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: ppfun/pixelplanet#23
No description provided.