3 ms·

There's no need for speculation here. Open Facebook, right click, select "Inspect Element" then the "Network" tab. On a self-censored status update, they send

There's no need for speculation here. Open Facebook, right click, select "Inspect Element" then the "Network" tab. On a self-censored status update, they send a request to /ajax/bz that triggers their censorlogger, but don't pass the content itself. On messages & chat, they send a request to /ajax/messaging/typ.php to show the other person you're typing, but again, they don't pass your message to their servers. On search, they send a request to /ajax/typeahead/search/facebar/query/ which passes everything you type to their server to power their auto-complete functionality.

alexwright 13y ago
Yes you could do that two seconds worth of testing, in basically every browser these days even. But then you couldn't write a link bait article about the possibility that they are doing it.
- B-Con 13y ago
  This is Slate. I expect nothing better.
- tedunangst 13y ago
  "I don't know for certain that this has never happened..."
selmnoo 13y ago
I have done this before, I've done experiments where I meticulously monitored all HTTP requests sent and I could've sworn I saw questionable activity. Doing it now I get results that seem similar to your description. I don't know what to say, other than that experience has taught me to always be on the skeptical side of things when we're talking about Facebook.
elwell 13y ago
I don't think /ajax/bz has anything to do with censorlogging. I'm seeing it hit just for scrolling down the page.
- joshfraser 13y ago
  I think it may be their generic logging system. The JSON passed back to their server contained the phrase trigger:"censorlogging" when I bailed on the status update.
  - elwell 13y ago
    ah ok
iLoch 13y ago
Well if I was really paranoid I might argue that they could save that information locally then upload it later when Facebook loses the browser's focus (ie. switch tab).
- yuliyp 13y ago
  Alright. Go ahead and test that. Have your machine connect through a proxy, leave it open for a day, see what you get

alexwright 13y ago

Yes you could do that two seconds worth of testing, in basically every browser these days even. But then you couldn't write a link bait article about the possibility that they are doing it.

B-Con 13y ago
This is Slate. I expect nothing better.
tedunangst 13y ago
"I don't know for certain that this has never happened..."

selmnoo 13y ago

I have done this before, I've done experiments where I meticulously monitored all HTTP requests sent and I could've sworn I saw questionable activity. Doing it now I get results that seem similar to your description. I don't know what to say, other than that experience has taught me to always be on the skeptical side of things when we're talking about Facebook.

elwell 13y ago

I don't think /ajax/bz has anything to do with censorlogging. I'm seeing it hit just for scrolling down the page.

joshfraser 13y ago
I think it may be their generic logging system. The JSON passed back to their server contained the phrase trigger:"censorlogging" when I bailed on the status update.
- elwell 13y ago
  ah ok

iLoch 13y ago

Well if I was really paranoid I might argue that they could save that information locally then upload it later when Facebook loses the browser's focus (ie. switch tab).

yuliyp 13y ago
Alright. Go ahead and test that. Have your machine connect through a proxy, leave it open for a day, see what you get