Do not include the reason for /monitor in the logs #147

New issue

Closed

opened 2025-11-29 06:44:20 -05:00 by sirdog3355 · 1 comment

sirdog3355 commented

2025-11-29 06:44:20 -05:00

(Migrated from github.com)

What it says on the tin. The reason for why someone is being monitored can be very sensitive - upto and including allegations of illegal behavior - and that should not be held flippantly in text. It should only be accessible to systems operators who manually pull the SQLITE database and look inside or when such an individual attempts to join and the bot makes the notification.

Desired functionality is that the reason for /monitor being ran is omitted from inclusion in the logs.

What it says on the tin. The reason for why someone is being monitored can be _very_ sensitive - upto and including allegations of illegal behavior - and that should not be held flippantly in text. It should only be accessible to systems operators who manually pull the SQLITE database and look inside _or_ when such an individual attempts to join and the bot makes the notification. Desired functionality is that the reason for `/monitor` being ran is omitted from inclusion in the logs.

sirdog3355 commented

2025-11-30 22:42:30 -05:00

(Migrated from github.com)

Closed by #157