antidoxxing: cog ships with no info.json at all (missing GDPR statement + metadata) #10

New issue

Open

opened 2026-08-10 04:04:58 -04:00 by everestmcarthur · 0 comments

everestmcarthur commented

2026-08-10 04:04:58 -04:00

(Migrated from github.com)

The new antidoxxing cog (added 2026-08-05) has no info.json whatsoever — affiliates, ghostwipe, and imagevault (tracked in #9) at least have an info.json missing just the end_user_data_statement field, but antidoxxing is missing the file entirely (no name, author, min_bot_version, or end_user_data_statement).

This is a real compliance gap, not just a formality: antidoxxing/antidoxxing.py actively scans message content for PII (IPv4/IPv6 addresses, GPS coordinates), stores a sanitized copy of flagged messages in mod-log embeds (_send_logs, line ~423), and can forward those logs to an optional global webhook (config.register_global(webhook_url=...)). That's squarely the kind of processing that needs an end_user_data_statement, on top of the missing cog metadata Downloader/repo tooling expects.

Suggest adding antidoxxing/info.json with the standard fields (matching the other 9 cogs) plus an end_user_data_statement, and doing the same for any other new cogs going forward.

Code refs:

antidoxxing/ — no info.json present
antidoxxing/antidoxxing.py:267 — reads raw message.content
antidoxxing/antidoxxing.py:423-436 — logs sanitized message content to mod channel
antidoxxing/antidoxxing.py:41 — config.register_global(webhook_url=None) — optional global webhook forwarding

The new `antidoxxing` cog (added 2026-08-05) has no `info.json` whatsoever — `affiliates`, `ghostwipe`, and `imagevault` (tracked in #9) at least have an `info.json` missing just the `end_user_data_statement` field, but `antidoxxing` is missing the file entirely (no `name`, `author`, `min_bot_version`, or `end_user_data_statement`). This is a real compliance gap, not just a formality: `antidoxxing/antidoxxing.py` actively scans message content for PII (IPv4/IPv6 addresses, GPS coordinates), stores a sanitized copy of flagged messages in mod-log embeds (`_send_logs`, line ~423), and can forward those logs to an optional global webhook (`config.register_global(webhook_url=...)`). That's squarely the kind of processing that needs an `end_user_data_statement`, on top of the missing cog metadata Downloader/repo tooling expects. Suggest adding `antidoxxing/info.json` with the standard fields (matching the other 9 cogs) plus an `end_user_data_statement`, and doing the same for any other new cogs going forward. Code refs: - `antidoxxing/` — no `info.json` present - `antidoxxing/antidoxxing.py:267` — reads raw `message.content` - `antidoxxing/antidoxxing.py:423-436` — logs sanitized message content to mod channel - `antidoxxing/antidoxxing.py:41` — `config.register_global(webhook_url=None)` — optional global webhook forwarding