To protect your privacy, mark your events "Not Attending".
Update (06:00 PDT): So far, some people have reported that their events are exposed, and some have reported that they aren't. I don't have an explanation. I've sent a note to Facebook asking them not to expose events this way.
Update (13:00 PDT):
theharmonyguy commented that event lists were already
(
Read more... )
Comments 81
Our app republished your FB events. Contrary to documentation, FB would not
filter out "secret" events even if asked to. Since we couldn't tell your public events from your non-public events, we had to disable that part of the app.
We filed bugs, but the resolution was that this was a documentation bug. (!!!) I can't find it, but it was a really low numbered bug at the time, like less than 500.
Here's a public announcement I made at the time.
http://www.facebook.com/topic.php?uid=2358064182&topic=3330
They've iterated many times on the basic technology since then, and it seems that there are at least some ways to fix the problem now (there were none back then). But, it seems to me to be part of FB's general failure to think through privacy implications (or, more disturbingly, to think through, and then to shrug off.)
Reply
/Christian
Reply
Reply
Reply
Reply
I miss the 2006 version of Facebook, where the only annoying nags were pokes.
Reply
... and pasting this line into the address bar of a selected profile with an old FB settings:
javascript:(function(){CSS.removeClass(document.body,%20'profile_two_columns');tab_controller.changePage("photos");})()
Reply
But the code has been making the rounds, and lately seems to have been really spreading. Tonight it appears that Facebook has blocked the trick.
By the way, the first version of the trick was also posted back in December.
Reply
Reply
Leave a comment