IDEA: "Personal Censor"

[CodeTRUCKER]

I had a thought in regard to the tagging/NSFW debate that seems to recur periodically.  I was wondering if there was a tool that could be a "Personal Censor?"  I'm not real sure how it would work exactly, but if there was a utility that could be programmed for the individual tastes which would censor out what one does not want to read without butchering the author's real message, it could be of some value, I think?

[Deozaan]

I could have sworn that fellow DC member Allen's ReReplace did that, but checking it out now I don't see that feature. You could send him a personal message and invite him to add that feature. I doubt it would be very difficult.

Even though ReReplace isn't what you're looking for now, it is quite a handy online find and replace utility that accepts Regular Expressions and displays highlighted results to boot!

[CodeTRUCKER]

I could have sworn that fellow DC member Allen's ReReplace did that, but checking it out now I don't see that feature. You could send him a personal message and invite him to add that feature. I doubt it would be very difficult.

Even though ReReplace isn't what you're looking for now, it is quite a handy online find and replace utility that accepts Regular Expressions and displays highlighted results to boot!

Sounds promising. 

[skrommel]

Proximotron should do the trick. Download from http://www.proxomitron.info

Skrommel

[CodeTRUCKER]

Ah! Yes, I've used the venerable Proxomitron before.  Worked great too.  I can't recall why I ditched it?

[allen]

Ok, I've implemented such a feature--but keep in mind it's a bit rough in some areas.  You can search a URL and view the results either as source or see the changes/highlights within the page itself.  Excluding html tags from the query would, however, take a great deal of work than I care to do, so don't be surprised with the occasional format breakage on a page.  Also, at present, it won't elegantly integrate an intricately designed website with the find highlighters -- so there's plenty of breakage there.  But there shouldn't be too many complications with the replacement aspect--much simpler than the find/preview functions!

[CodeTRUCKER]

Thanks for the comments and suggestions.