Optionally use an external text file instead of/additionally to BadContents wiki page

[izzysoft@…]

It would be nice to use some external text file instead of/additionally to the wiki page, which had several advantages:

• the admin only needs to maintain one list even for multiple trac environments
• spammers could not simply investigate the page to see what terms to avoid
• there could even be a central maintained file provided on the net to be updated regularly by e.g. a cron job (and optionally merged with another file holding local terms)

[ebray]

Note that with fine-grained permissions you can easily prevent spammers from seeing your BadContent. Of course, that's not the default situation. I think that the other points are valid.

Perhaps someone could contribute a script to sync environments with Trac's BadContent.

[Dirk Stöcker]

The bayes filter is much more effective than the BadContents page is and the BadContents page is changed seldom. Is this really required?

[izzysoft@…]

Not "high priority" maybe, but still: I'd vote for "yes". I run a multi-project installation here with 10+ projects - havint those definitions in an external file would make things easier for people like me. True, this page rarely changes - but sometimes it does. Plus, having it not in the wiki the spammers cannot check against it.

[Dirk Stöcker]

In r10119.