Filtering is likely to be occasionally inconsistent (more so than usual?) over the next couple of days as I work on it.
I'm making it more simplified and squashing a couple of bugs in the process. Rather than having different "types" of filters (ones that block PM's and ones that hide public messages), setting a filter will accomplish both. You'll still be able to select whether you want to block replies to filtered people, though. Most people don't use that, but I put so much work into it, I'm not ready to throw it out the window yet.
One notable change that will possibly affect 444 people who use public-message filtering is that if you had someone's public message blocked but not their PM's, they won't be blocked anymore until you re-block them when I'm done. Actually, I'm pretty sure I'm far enough along that you can reblock them now (from a PM of theirs or their profile) and the change will survive the changes I'm making.
On the technical side of things, what's going on is that I've been using two separate tables that handle filter-storage completely differently for each type of filter. One of these methods/tables has a bug in that if you put a public filter (from their profile) on, say, user number 6748, it also treated user 8, user 48, and user 748 as being blocked. That bug didn't exist in the "PM Block" table, and since all filters will be based on that table now, the bug will go away.
I'll also be making it so that if you've got someone blocked (regardless of the current status of your Filtering On/Off toggle), they'll still be able to write public messages to you, but those messages won't appear in your MailBox.
And yet one more bug that'll be addressed. When I implemented filter limits (5 for free members, 200 for premium members), I apparently only applied that to PM blocks. Pretty useless since free members can't PM anyway. Those limits will end up applied to the single form of filtering we're going to use.
AI
