facebook: /me/posts returns objects with ids with colons

[snarfed]

very weird. @aaronpk reported that bridgy sent him duplicate responses this morning, e.g. on http://aaronparecki.com/notes/2014/09/02/4/drhorrible. here are example original and duplicated u-urls:

• https://facebook.com/11500459/posts/10101595978024156?comment_id=10101596203522256
• https://facebook.com/11500459/posts/11500459:10101595978024156:63?comment_id=10101596203522256

note the odd (bad) colon-formatted post id in the dupe. FB evidently returned comment ids like these in a single /me/posts API call, 2014-10-28 16:53:24 UTC. log here. polls for @aaronpk's acccount since then have received normal comment ids, without colons.

[snarfed]

google doesn't find any other reports, at least for queries like facebook graph api ids "colons".

[snarfed]

reopening, we're seeing this again for many/all FB users. example log:

Traceback (most recent call last):
...
File "/base/data/home/apps/s~brid-gy/3.383236630846410047/tasks.py", line 109, in post
  source_updates.update(self.poll(source))
File "/base/data/home/apps/s~brid-gy/3.383236630846410047/tasks.py", line 161, in poll
  cache=cache)
File "/base/data/home/apps/s~brid-gy/3.383236630846410047/facebook.py", line 204, in get_activities_response
  assert ':' not in id[1], 'Cowardly refusing id with colon: %s' % id[1]
AssertionError: Cowardly refusing id with colon: 12802152:10101224399086339:10101869104476441_10101225182401569

@kylewm thinks it might be /1565113317092307/invited, but we don't see colons in those ids right now.

[snarfed]

the id in that example, 12802152:10101224399086339:10101869104476441_10101225182401569, is [USERID]:[POSTID]:[OTHER-USERID]_[UNKNOWN]

[snarfed]

more example ids:

• 100001501388539:866229876770384:10101869104476441_866434786749893
• 10205989425965050:10206207863185844:10101869104476441_10206207866545928
• 510659665:10153194244359666:10101869104476441_10153194358259666

the only part that's the same is the second user id, 10101869104476441.

[snarfed]

i'm seeing that 10101869104476441 user id in every single bad id, so i'm going to go out on a limb and say it's the root cause, or at least the common thread.

[snarfed]

it's the app-scoped user id for https://www.facebook.com/rickosterberg .

[snarfed]

also notable, the colon-separated ids here are of a different form than the original ones in this bug, e.g. 11500459:10101595978024156:63.

[snarfed]

progress: these ids are in comments returned by /me/posts for some users, e.g. 10205049272524056. example post https://www.facebook.com/10205049272524056/posts/10205200565786293 . corresponding object returned by FB API:

{
  "id": "10205049272524056_10205200565786293",
  "comments": {
    "data": [
      {
        "id": "10205049272524056:10205200565786293:10101869104476441_10205207541960693",
        "message": "Did you go to Comicon (spelled correctly?) this year?",
        ...
      },
      {
        "id": "10205049272524056:10205200565786293:10101869104476441_10205216360221144",
        "message": "No. As usual, just lived vicariously through tweets.",
        ...
      },
  ...

the odd part is that the 10101869104476441 user seems unrelated. he didn't write the post or any comments or like anything. i wonder if that id here is something other than the app-scoped user id...but the FB id namespace is pretty unified, so hrmph.

[snarfed]

current status is watchful waiting. it was transient last time, so i'm still kinda hoping this is an FB bug that will eventually get fixed. it's been happening longer for this time, ~16h so far, but hope springs eternal.

[snarfed]

huh. the v2.3 /me/posts docs say it returns Post objects, but the v2.3 Post object docs say they were "removed after Graph API v2.2."

i'm guessing just an unrelated doc bug...but hrm.