Having filters configurable via the mastodon api will be difficult, as not all the options can be mapped to it. The JS codebase just returns an empty collection (when listing filters), and an error advising users to check the web interface instead (when adding filters).

Hmm, maybe we should revamp filters altogether. The current system is split in half and kind of janky.

Mastodon filters:

• Title
• Expiry (optional)
• Context (home/lists/conversations/notifications/profiles/public timelines)
• Action (hide with warning/hide completely)
• Keywords (list, "whole word" toggle)

This is a superset of misskey style filters, with the only thing missing being regex. We can just support that by surrounding the filter with slashes, though.

I definitely think we should drop both previous word mute locations and create a new table for them.

We should also support editing the filters through the mastodon client api, unlike the js codebase, especially since it'll take a while for the frontend & web api to catch up.

Existing filters are now handled properly, though we should ensure that expired ones are cleaned up properly.