11 comments.

  1. Michael

    same here

  2. Icaro

    Same here

  3. Michael

    It's very frustrating Meta doesn't state what permission we need to get permalink_url (comment_id) without using PPCA.
    This change has broken Facebook for our customers for days b/c we have to quickly decide on how to move forward with comment ids (including handling replies).
    This should've been pushed as a FB notification to developers, being an important deprecation.

  4. Michael

    hi michael could you provide any tips on handling comment ids & permalink ? we didn't recieve any notification, is this permanent?

  5. Michael

    Hey Michael, whoops I meant to write my reply as a comment but put it in the answers. Leaving it there

  6. Icaro

    As per documentation this is permanent from August 19 forward. https://developers.facebook.com/docs/graph-api/reference/v20.0/comment
    Does anyone have found a solution/workaround?

    1. Icaro

      As per documentation this is permanent from August 19 forward. https://developers.facebook.com/docs/graph-api/reference/v20.0/comment
      Does anyone have found a solution/workaround?

      1. Icaro

        As per documentation this is permanent from August 19 forward. https://developers.facebook.com/docs/graph-api/reference/v20.0/comment
        Does anyone have found a solution/workaround?

    2. Icaro

      As per documentation this is permanent from August 19 forward. https://developers.facebook.com/docs/graph-api/reference/v20.0/comment
      Does anyone have found a solution/workaround?

  7. Michael

    Hey Michael, I had this issue with another platform we use and the way I dealt with it is to concat the post_id (of which the comment belongs), the comment datetime, and the comment text into a string, then do an md5 hash to end up with something that looks more like an ID. Collisions are possible but rare.
    Beware #1: if you are currently tracking which comments you already have, this new system is gonna cause duplicated data due to artificially unique IDs using this new system, so you would want to do a full recollection and invalidate old comments.
    Beware #2: if the user edits their comment, you'll end up with a second different ID for the same comment. So don't use that part if that will cause issues for you. If you exclude text from your ID hash, beware that you'll run into ID collisions if two comments are posted within the same second).
    There are some other details you can figure out to make this system work better according to your ecosystem requirements.

    1. Michael

      Hey Michael, I had this issue with another platform we use and the way I dealt with it is to concat the post_id (of which the comment belongs), the comment datetime, and the comment text into a string, then do an md5 hash to end up with something that looks more like an ID. Collisions are possible but rare.
      Beware #1: if you are currently tracking which comments you already have, this new system is gonna cause duplicated data due to artificially unique IDs using this new system, so you would want to do a full recollection and invalidate old comments.
      Beware #2: if the user edits their comment, you'll end up with a second different ID for the same comment. So don't use that part if that will cause issues for you. If you exclude text from your ID hash, beware that you'll run into ID collisions if two comments are posted within the same second).
      There are some other details you can figure out to make this system work better according to your ecosystem requirements.

      1. Michael

        Hey Michael, I had this issue with another platform we use and the way I dealt with it is to concat the post_id (of which the comment belongs), the comment datetime, and the comment text into a string, then do an md5 hash to end up with something that looks more like an ID. Collisions are possible but rare.
        Beware #1: if you are currently tracking which comments you already have, this new system is gonna cause duplicated data due to artificially unique IDs using this new system, so you would want to do a full recollection and invalidate old comments.
        Beware #2: if the user edits their comment, you'll end up with a second different ID for the same comment. So don't use that part if that will cause issues for you. If you exclude text from your ID hash, beware that you'll run into ID collisions if two comments are posted within the same second).
        There are some other details you can figure out to make this system work better according to your ecosystem requirements.

        1. Michael

          Hey Michael, I had this issue with another platform we use and the way I dealt with it is to concat the post_id (of which the comment belongs), the comment datetime, and the comment text into a string, then do an md5 hash to end up with something that looks more like an ID. Collisions are possible but rare.
          Beware #1: if you are currently tracking which comments you already have, this new system is gonna cause duplicated data due to artificially unique IDs using this new system, so you would want to do a full recollection and invalidate old comments.
          Beware #2: if the user edits their comment, you'll end up with a second different ID for the same comment. So don't use that part if that will cause issues for you. If you exclude text from your ID hash, beware that you'll run into ID collisions if two comments are posted within the same second).
          There are some other details you can figure out to make this system work better according to your ecosystem requirements.

    2. Michael

      Hey Michael, I had this issue with another platform we use and the way I dealt with it is to concat the post_id (of which the comment belongs), the comment datetime, and the comment text into a string, then do an md5 hash to end up with something that looks more like an ID. Collisions are possible but rare.
      Beware #1: if you are currently tracking which comments you already have, this new system is gonna cause duplicated data due to artificially unique IDs using this new system, so you would want to do a full recollection and invalidate old comments.
      Beware #2: if the user edits their comment, you'll end up with a second different ID for the same comment. So don't use that part if that will cause issues for you. If you exclude text from your ID hash, beware that you'll run into ID collisions if two comments are posted within the same second).
      There are some other details you can figure out to make this system work better according to your ecosystem requirements.

      1. Michael

        Hey Michael, I had this issue with another platform we use and the way I dealt with it is to concat the post_id (of which the comment belongs), the comment datetime, and the comment text into a string, then do an md5 hash to end up with something that looks more like an ID. Collisions are possible but rare.
        Beware #1: if you are currently tracking which comments you already have, this new system is gonna cause duplicated data due to artificially unique IDs using this new system, so you would want to do a full recollection and invalidate old comments.
        Beware #2: if the user edits their comment, you'll end up with a second different ID for the same comment. So don't use that part if that will cause issues for you. If you exclude text from your ID hash, beware that you'll run into ID collisions if two comments are posted within the same second).
        There are some other details you can figure out to make this system work better according to your ecosystem requirements.

    3. Michael

      Hey Michael, I had this issue with another platform we use and the way I dealt with it is to concat the post_id (of which the comment belongs), the comment datetime, and the comment text into a string, then do an md5 hash to end up with something that looks more like an ID. Collisions are possible but rare.
      Beware #1: if you are currently tracking which comments you already have, this new system is gonna cause duplicated data due to artificially unique IDs using this new system, so you would want to do a full recollection and invalidate old comments.
      Beware #2: if the user edits their comment, you'll end up with a second different ID for the same comment. So don't use that part if that will cause issues for you. If you exclude text from your ID hash, beware that you'll run into ID collisions if two comments are posted within the same second).
      There are some other details you can figure out to make this system work better according to your ecosystem requirements.

Add a new comment.