Geek Answers Handbook

Facebook Graph API Comments and Obscene Filter

I look to integrate Facebook comments left on our website in a way in which content can be crawled by search engines, as well as for people (although I very much doubt that there will be many) that do not have Javascript enabled in the browser.

Currently, our Facebook comments are displayed using the Facebook comment social plugin (using the <fb:comments href="MY_URL" num_posts="50" width="665"></fb:comments> ). This leads to an iFrame rendering (which is mostly ignored by search engines), so the plan is to display this information and format it using basic HTML. To do this, comments are pulled using the Graph API - this is displayed only for scanners and people with Javascript disabled.

This all works great using the Graph invocation API (https://graph.facebook.com/comments/?ids=MY_URL), analyzing the JSON result and displaying it on the page. The problem is that the <fb:comments> approach filters our results based on the blacklist that we installed in one of our Facebook apps. An AppId with an appropriate blacklist is stored on the page metadata using ( <meta property="fb:app_id" content="APP_ID"/> ), which <fb:comments> control, obviously needs to be used somehow to filter out the comments.

The problem is that the Graph API method does not filter any results, since I assume that the blacklist (or the application identifier containing the blacklist) is not specified. Does anyone know how to specify a Facebook app ID for an API API URL or not otherwise retrieve comments that violate the blacklist?

On the side of the note, I know that the debate about filtering content in the comments is raging on, but this is the decision of the leadership to implement a blacklist, and one that I have no influence on the changes - they just pack who felt the need to explain why filtering is or not is a good idea!

Any thoughts on a solution are greatly appreciated.

+4
source share
3 answers

Unfortunately, there is no way to access the filtered comment list using the API - this may be a reasonable request to have this in the API - you must specify the wishlist item in Facebook Error Tracking

Otherwise, the only solution I can come up with is to implement your own filter on your side when extracting and displaying comments from the API.

According to plugin comments, the documentation filter on the Facebook side is implemented as a simple subscript match, so it should be trivial to implement it. A fairly simple regex match should be able to quickly check each comment against a relatively long list.

(Unfortunately, the trade-off is that implementing the filter is simple, but you also need to write an interface so that anyone updating the list of banned words can maintain the list for both the Facebook plugin and your own filtering.)

Quote from the docs:

 The comment is checked via substring matching. This means if you blacklist the word 'at', if the comment contains the sequence 'a' 't' anywhere it will be marked with limited visibility; eg if the comment contained the words 'bat', 'hat', 'attend', etc it would be caught.
+1
source

It's pretty accurate that there is no way to do this from the graphical API, the only thing I can offer is to take a blacklist and create your own filter.

0
source

You don't seem to need to do this anymore as Google started indexing Facebook comments

http://www.labnol.org/internet/google-indexes-facebook-comments/20295/

0
source

More articles:


All Articles