Return-path: Envelope-to: fb@vin-fm.com Delivery-date: Thu, 04 Apr 2013 08:34:57 +0700 Received: from outcampmail005.snc4.facebook.com ([66.220.144.164]:33710 helo=mx-out.facebook.com) by server01-iix.secureserver.web.id with esmtp (Exim 4.80) (envelope-from ) id 1UNZ4q-0000NR-OC for fb@vin-fm.com; Thu, 04 Apr 2013 08:34:57 +0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=facebookmail.com; s=s1024-2011-q2; t=1365038920; bh=frnTzDtKYOA5sWeVSsMLkTbQI4WwZ/hh+MgO7BGxazY=; h=Date:To:From:Subject:MIME-Version:Content-Type; b=kzMN3FhhEi1R2UO9CgjcgvqA4eOVPDAny0u0z5hZQ/kTeSzsNJSfCfU8mOFw2i6kW Ta7U7OhEqHs199QHKKinY4/+b68WjnWYf52UOxF3Z9GM2G4yrwBG0MMYmIJtezZFaW aAFhBMeqxifdARKNzoIb/VGivqGrMfV4JRqyUhbg= Received: from [10.66.204.49] ([10.66.204.49:48554]) by smout022.snc6.facebook.com (envelope-from ) (ecelerity 3.5.1.37927 r(/root/Momo-dev:tip)) with ECSTREAM id D2/2B-32706-847DC515; Wed, 03 Apr 2013 18:28:40 -0700 X-Facebook: from zuckmail ([MTI3LjAuMC4x]) by async.facebook.com with HTTP (ZuckMail); Date: Wed, 3 Apr 2013 18:28:40 -0700 To: fb@vin-fm.com From: "Facebook" Subject: Developer Blog: New APIs for Comment Replies Message-ID: X-Priority: 3 X-Mailer: ZuckMail [version 1.00] X-Facebook-Notify: ; mailid= X-FACEBOOK-PRIORITY: 0 X-Auto-Response-Suppress: All MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="b1_eb73243120b9db15202f5a94e955d561" --b1_eb73243120b9db15202f5a94e955d561 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Halo Vincent, A new post has been added to the Developer Blog. New APIs for Comment Replies, Besok, 4 April jam 7:38 Published by Alex Madjar Last week, we launched comment replies on Facebook pages and profiles with = more than 10,000 followers. This allows businesses and celebrities to = engage with their fans more directly. Today, we=E2=80=99re updating the = API so developers can build tools that make it easier for brands to = monitor and respond to comment replies. API Updates Our API now supports different "views" of the comments on posts through = our updated comments API and FQL comment table. Top Level Comments The first view of the comments on a post is called "top level". The = comments that are on the post (and are not replies to individual comments) = are called "top level comments." Top level comments may be ranked, = depending on the post and the number of top level comments on that post so = far. The top level view of comments corresponds to what a user would see on = Facebook. To get the top level view of comments in Graph API: GET {object_id}/comments?filter=3Dtoplevel In FQL, you can issue the request: SELECT id, fromid, time, text, likes=20 FROM comment=20 WHERE object_id=3D{object_id} AND parent_id=3D'0' Replies Comments on comments are called "replies." You get replies by querying = for the comments on a comment id. Graph API: GET {comment_id}/comments FQL: SELECT id, fromid, time, text, likes=20 FROM comment=20 WHERE parent_id=3D{comment_id} Comment Stream Another view of the comments on a post is the "stream". The comments = "stream" gives all comments (top level and replies to comments) together. = The "stream" view provides comments in chronological order, so it's easy = for you to just get what's new. Graph API: GET {object_id}/comments?filter=3Dstream FQL: SELECT id, fromid, time, text, likes=20 FROM comment=20 WHERE object_id=3D{object_id}=20 ORDER BY time Getting Started with the APIs To get started today with the new APIs, opt into the "July 2013 Breaking = Changes" migration for your app by visiting the Advanced tab of your app = dashboard. If you're currently using our existing comments APIs, here are a few = changes to keep in mind: 'comments' field from 'stream' FQL table is deprecated. Please use = the'comment_info' column to fetch the 'can_comment' and 'comment_count' = fields. We are removing the fields on the FQL 'comment' table that were used = exclusively for legacy Comments Plugins -- 'xid', 'reply_xid', 'username' = and 'comments'. We are removing the undocumented 'count' field on the 'comments' = connection in the Graph API. Please request = '{id}/comments?summary=3Dtrue' explicitly if you would like the summary = field which contains the count (now called 'total_count') Please read the documentation for details on how to use these new features = and the Roadmap for details on the API changes. We're excited to continue working with you, our community of developers, = to improve the quality of the conversations happening on Facebook and = can't wait to see what you build. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ___________________ This message was intended for fb@vin-fm.com. Anda menerima surel ini = karena anda telah memilih untuk menerima pembaruan pengembang dari = Facebook. Ingin mengendalikan pembaruan pengembang mana saja yang anda = terima? Pergi ke: http://developers.facebook.com/settings Facebook, Inc., Attention: Department 415, PO Box 10005, Palo Alto, CA = 94303 --b1_eb73243120b9db15202f5a94e955d561 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Facebook
facebook
Halo Vincent,
A new post has been added to the Developer = Blog.
 

3D"Alex
Besok, 4 April jam 7:38
Published by Alex = Madjar

Last week, we launched comment replies on Facebook pages = and profiles with more than 10,000 followers. This allows businesses and = celebrities to engage with their fans more directly. Today, we=E2=80=99re = updating the API so developers can build tools that make it easier = for brands to monitor and respond to comment replies.

API Updates

Our API now supports different "views" of the comments on posts through = our updated comments API and FQL = comment table.

Top Level Comments

The first view of the comments on a post is called "top level". The = comments that are on the post (and are not replies to individual comments) = are called "top level comments." Top level comments may be ranked, = depending on the post and the number of top level comments on that post so = far.

The top level view of comments corresponds to what a user would see on = Facebook. To get the top level view of comments in Graph API:

GET {object_id}/comments?filter=3Dtoplevel

In FQL, you can issue the request:

SELECT id, fromid, time, text, likes=20
FROM comment=20
WHERE object_id=3D{object_id} AND parent_id=3D'0'

Replies

Comments on comments are called "replies." You get replies by querying = for the comments on a comment id.

Graph API:

GET {comment_id}/comments

FQL:

SELECT id, fromid, time, text, likes=20
FROM comment=20
WHERE parent_id=3D{comment_id}

Comment Stream

Another view of the comments on a post is the "stream". The comments = "stream" gives all comments (top level and replies to comments) together. = The "stream" view provides comments in chronological order, so it's easy = for you to just get what's new.

Graph API:

GET {object_id}/comments?filter=3Dstream

FQL:

SELECT id, fromid, time, text, likes=20
FROM comment=20
WHERE object_id=3D{object_id}=20
ORDER BY time

Getting Started with the APIs

To get started today with the new APIs, opt into the "July 2013 = Breaking Changes" migration for your app by visiting the Advanced tab of = your app dashboard.

If you're currently using our existing comments APIs, here are a few = changes to keep in mind:

  • 'comments' field from 'stream' FQL table is deprecated. Please use = the'comment_info' column to fetch the 'can_comment' and 'comment_count' = fields.

  • We are removing the fields on the FQL 'comment' table that were = used exclusively for legacy Comments Plugins -- 'xid', 'reply_xid', 'username' and = 'comments'.

  • We are removing the undocumented 'count' field on the 'comments' = connection in the Graph API. Please request = '{id}/comments?summary=3Dtrue' explicitly if you would like the summary = field which contains the count (now called 'total_count')

Please read the documentation for details on how to use these new features = and the Roadmap for details = on the API changes.

We're excited to continue working with you, our community of = developers, to improve the quality of the conversations happening on = Facebook and can't wait to see what you build.


This = message was intended for fb@vin-fm.com. Anda menerima surel ini = karena anda telah memilih untuk menerima pembaruan pengembang dari = Facebook. Ingin mengendalikan pembaruan pengembang mana saja yang anda = terima? Pergi ke:
= http://developers.facebook.com/settings
Facebook, Inc., Attention: = Department 415, PO Box 10005, Palo Alto, CA = 94303
--b1_eb73243120b9db15202f5a94e955d561--