Change Details

See comments in Change-Id: Ifeec00fc98c7912b6e16b6f07d1fdc26ab4e4fb5 Currently protection log entries are stored in plain text which is also used as the IRC line, making it hard to be i18n'ed. It could be nice to just store the original restriction array, use the new LogFormatter architecture to format it on display, and have it decoupled from IRC text, so it can be correctly translated without breaking existing bots. -------------------------- **Version**: unspecified **Severity**: enhancement

See comments in Change-Id: Ifeec00fc98c7912b6e16b6f07d1fdc26ab4e4fb5 Currently protection log entries are stored in plain text which is also used as the IRC line, making it hard to be i18n'ed. It could be nice to just store the original restriction array, use the new LogFormatter architecture to format it on display, and have it decoupled from IRC text, so it can be correctly translated without breaking existing bots.

See comments in Change-Id: Ifeec00fc98c7912b6e16b6f07d1fdc26ab4e4fb5 Currently protection log entries are stored in plain text which is also used as the IRC line, making it hard to be i18n'ed. It could be nice to just store the original restriction array, use the new LogFormatter architecture to format it on display, and have it decoupled from IRC text, so it can be correctly translated without breaking existing bots. -------------------------- **Version**: unspecified **Severity**: enhancement