{"id":3130,"date":"2011-03-03T13:52:05","date_gmt":"2011-03-03T13:52:05","guid":{"rendered":"https:\/\/thesocialelement.agency\/us\/?p=3130"},"modified":"2011-03-03T13:52:05","modified_gmt":"2011-03-03T13:52:05","slug":"testing-facebook-pages-new-profanity-filter-works","status":"publish","type":"post","link":"https:\/\/thesocialelement.agency\/us\/testing-facebook-pages-new-profanity-filter-works","title":{"rendered":"Testing Facebook Pages: The New Profanity Filter – How It Works"},"content":{"rendered":"
When it comes to Facebook, there’s only one to check out their changes: test, test and test. For which you will need access to at least three profiles: Comments<\/p>\n My conclusions?<\/strong><\/p>\n
\n1. Page admin
\n2. User posting comments
\n3. Other user.
\nMy tips? Use three different browsers for each log in, and keep notes as you go. Oh, and screenshots. Then you can fill in any other members of your team who need to manage Facebook pages (and check they have the same results, following the steps you took). Banal doesn’t even begin to describe it. It’s even slightly dull. But that’s how it has to be.
\nFollowing my recent post on Facebook’s new built-in profanity filter, our community management team at eModeration had some questions.\u00a0 Do you have to put any words in the customisable list? How strong is the filter on the two available settings? Does it work on character strings? How quickly does it work? Does a user know their comments has been deleted? Posts as well as comments? etc etc.
\nI’ve just done a little testing, and here is how it went:
\nThe test<\/strong>
\nPosts<\/p>\n\n
\n
\n