He's not talking about IP.Board, even though he's put it in the IP.Board category, he's talking about IP.Content
And I'm sorry to say, he has a point. I love IP.Board as much as the next person, but I've just decided to revert from IP.Content to Drupal, running a site with IP.Content for the last year (which I eventually managed to set up properly) has been a royal pain. IP.Content still an incredibly difficult piece of software to get fully conversant with (and yes, Drupal is, but is much more readily extendable as it has a more active developer community).
Putting 'today' in the filter will give me any episode that airs today - could work though and be a slightly different approach for how things work on my site (just because it's worked one way for the last 15 years doesn't really mean it has to keep working in the same way in the future).
I'm going to have a play around this theme and see how it pans out.
It's an interesting idea worth investigating further. But the person would soon find out they're been passively banned - what if they log in as a guest for example and see all their posts missing? (Well, I suppose you could show them to guests still, on the basis that guests wouldn't be able to reply).
In my eyes, it's a bit of a sneaky way to ban people (like making people "miserable" is). If only there were a reliable way to ban someone for ever.
I've just installed IP.Content at the weekend and am getting to grips with it.
One thing that I have on my current website is a huge library of reusable pictures, so if I want to accompany a story about person X, then I can call up any picture of person X and reuse it in that article.
At the moment with IP.Content I have to upload a picture to go with each article I create (or at least that's what I'm assuming based on my limited playing).
I want to use IP.Gallery to store all these pictures (as I let people browse the picture library I have). Would this then let me reuse pictures in IP.Content for articles more easily?